Freeze after entering password

[petsam]

@Marvin

Or just this case different?

Standard instructions are… standard, not for every case. Since you worry about it, I would expect you had gone and read manuals to check what the different options do. It’s still not late to do it . For example, we need info for the previous booted and failed session, not the current and successful one.

---

On Topic:

Unfortunately, there is no much difference that I can notice, but I have questions.

What is your configured display resolution, and how do you set it?
Is the LightDM resolution different from the user session’s (XFCE)?

@Marvin

There was a mouse pointer, it was slightly larger than my usual one,

[     4.732] (II) Loading sub module "dri2"
[     4.732] (II) LoadModule: "dri2"
[     4.732] (II) Module "dri2" already built-in


[     4.735] (==) intel(0): Display hotplug detection enabled
[     4.736] (II) intel(0): [DRI2] Setup complete
[     4.736] (II) intel(0): [DRI2]   DRI driver: i965
[     4.736] (II) intel(0): [DRI2]   VDPAU driver: va_gl
[     4.736] (II) intel(0): direct rendering: DRI2 DRI3 enabled
[     4.736] (II) intel(0): hardware support for Present enabled

[     4.932] (II) Initializing extension DRI2
[     4.938] (II) intel(0): switch to mode 1920x1080@60.0 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none
[     4.944] (II) intel(0): Setting screen physical size to 508 x 285
...

[    15.897] (II) intel(0): resizing framebuffer to 1024x768
[    15.897] (II) intel(0): switch to mode 1024x768@75.0 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none

Please, post :

pacman -Q xf86-video-intel

If that package is installed, you can try uninstalling it and testing for improvement.

@Marvin

why is it working sometimes, e.g. yesterday 3 or 4 reboots were fine and only one was not, whereas on the previous day it had been 5 or 6 fails and only one success.

When such behavior happens on a not-modified system configuration, it is a clear sign of one of two things AFAIK.

1. Some hardware component is failing slowly (hardware)
2. A race condition is affecting behavior (software)

So, my next question is "What have you changed on system or desktop (XFCE) configuration before this started happening? Think! Think!..

In case it is a user account issue, create a new user account and login to that, to test behavior.

[Marvin]

@petsam

… had gone and read manuals to check what the different options do. It’s still not late to do it .

For example, we need info for the previous booted and failed session, not the current and successful one.

Sure, but i had already allowed for the boot session number, obv! It was the ‘x’ changing to a ‘z’ on the inxi command that got me. TBH the ‘x’ being there at in the initial command i thought confusing as ‘man inxi’ implied, to me, that the ‘x’ needs to be accompanied by another ‘qualifier’.

@petsam

What is your configured display resolution, and how do you set it?

I guess i must have set it during the install of EOS.
When i boot the live eos it gives me 1920x1080 (shown default on running system) which i then manually change to 1024x768

@petsam

Is the LightDM resolution different from the user session’s (XFCE)?

Sorry, not a clue??
Every line in the lightdm.conf file is commented out (#) except for the headings ().
Including for display-setup-script
so i guess, the same as display.

I have only done, and when running on live eos only do, one resetting of the resolution and that is through “display”

@petsam

Please, post :

pacman -Q xf86-video-intel

If that package is installed, you can try uninstalling it and testing for improvement.

$ pacman -Q xf86-video-intel == xf86-video-intel

I will remove after posting this reply … 'ish

Although, how many roads must a man walk down? Or in our case, how many reboots would prove that this issue has really done a Lord Lucan?

I am seriously considering doing a fresh install and moving to lxqt, i.e. clean things up; hopefully help with your [2] below; make me feel like i’ve done something & see the new install + try an online install for once.

@petsam

When such behavior happens on a not-modified system configuration, it is a clear sign of one of two things AFAIK.

1. Some hardware component is failing slowly (hardware)
2. A race condition is affecting behavior (software)

Gotcha, fingers crossed then

[petsam]

@Marvin

Lord Lucan

I guess you know this is an international site/forum. I have no idea what this is. Are you cursing?..

@Marvin

make me feel like i’ve done something

Well, you haven’t answered one question.

@petsam

What have you changed on system or desktop (XFCE) configuration before this started happening?

Also, have tried the suggestion?

@petsam

create a new user account and login to that, to test behavior

[Marvin]

@petsam

@Marvin

Lord Lucan

I guess you know this is an international site/forum. I have no idea what this is. Are you cursing?..

Cursing, nah.
I have long since stopped believing in those gods of IT, well, at least since i left Windoze behind me Πέτρος

Lord Lucan was a posh guy who disappeared and who the police suspected of killing his kids nanny.
Forget it. It’s an age thing.
Replace with:

disappeared

@petsam

@Marvin

make me feel like i’ve done something

Well, you haven’t answered one question.

Sorry, i haven’t changed anything.
Not added anything. Not taken anything away. Not changed anything.
I’ve not changed the display, background, theme, not even moved an icon (i do only have one).
I have not even altered any settings in an application for some time & long before all this started.

I do update my system every day, immediately after i switch on, with:
yay -Syu
and if that says i should reboot i do. After the reboot i then do:
pacman -Syyu
which i accept is probably completely unnecessary.

@petsam

@petsam

What have you changed on system or desktop (XFCE) configuration before this started happening?

Also, have tried the suggestion?

Nothing has changed - see above for complete list.
BTW, i haven’t done any desktop changes since my last install
_ except create one desktop link ( for EiskaltDC++ ) which i did soon after the EOS install had finished.

N.B. It is the Qt version of EiskaltDC++ though.

And yes, i have removed it using:
sudo yay -Rns xf86-video-intel
and then i rebooted as recommended.

I then did a system update (as stated above) and it recommended another reboot, which i did.

@petsam

@petsam

create a new user account and login to that, to test behavior

No, I have not done this as taking the above actions would seem to have resolved the issue … well, i have done six reboots, plus the ones mentioned above, and all of them have gone like a dream
& a bit quicker too!

Do you still think that creating a new user now and trying that it would move this issue forward now?

Although i have lost my lovely EOS background and instead got a CCTV image of some mouse that’s stuck in a maze.

[anon11595408]

@Marvin

sudo yay -Rns xf86-video-intel

sudo yay -Rns <package> now has removed the package, along with it’s dependencies. In case there were any important dependencies to this package, they were also removed, although they might be very needed by your system (not sure in this case), as I cannot reproduce it here on my system. But in case this package relies on Xorg, oh well, then your system cannot boot again without fixing it via chrooting into the system from a live ISO or from another Linux system installed on your machine.

To remove a single package in the future, you should always do yay -Rc <package>, instead. This will remove the single package without removing it’s dependencies that might be needed by your system.

To list the dependencies of a package, simply type sudo pacman -Qi <package>

Sudo and yay also don’t go well together, this might cause more errors. - To update your system, you should simply use yay without any additional arguments.

[Marvin]

@anon11595408

sudo pacman

@anon11595408

@Marvin

sudo yay -Rns xf86-video-intel

sudo yay -Rns <package> now has removed the package, along with it’s dependencies. In case there were any important dependencies to this package, they were also removed, although they might be very needed by your system (not sure in this case), as I cannot reproduce it here on my system. But in case this package relies on Xorg, oh well, then your system cannot boot again without fixing it via chrooting into the system from a live ISO or from another Linux system installed on your machine.

To remove a single package in the future, you should always do yay -Rc <package>, instead. This will remove the single package without removing it’s dependencies that might be needed by your system.

To list the dependencies of a package, simply type sudo pacman -Qi <package>

Thanks for the correction, i thought, well, assumed, that it would only removed dependencies that nothing else needed.
Seems very dangerous to do what it does imo.

Still, it seems i was lucky as my system still works.
But i’ve made a note for next time, thanks.

@anon11595408

Sudo and yay also don’t go well together, this might cause more errors. - To update your system, you should simply use yay without any additional arguments.

Yeah, sorry.
I don’t actually type sudo yay
i enter yay options
then enter my password when it is requested.
I was just implying that it wasn’t being done as a user without sudo abilities.

Thanks for the points you made.

[anon11595408]

Thank God in your case, and next time, please think of others reading your commands and reproducing them on their systems. Thank you.

[Marvin]

@anon11595408

Thank God in your case, and next time, please think of others reading your commands and reproducing them on their systems. Thank you.

I will, thank you again Sir Knight

[petsam]

@Marvin

Do you still think that creating a new user now and trying that it would move this issue forward now?

Do you have a better idea?
Does it cost more than you can afford?

Maybe yes, maybe no.

[Marvin]

What i meant was if it would certainly seem to not be faulty now, how would we gauge the results of comparing the current situation with those when we created a new user?
i.e.
both would just be working …

Unless there are other checks that you want me to run as a new user?

[petsam]

@Marvin

if it would certainly seem to not be faulty now, how would we gauge the results of comparing the current situation with those when we created a new user?
i.e.
both would just be working …

IIUC, this issue is of the randomly happening type. These issues are solved when the user decides so. When you decide there is no issue, mark a post as the solution.
The waiting time is yours to decide.

A simple perspective is:

Keep it as it is now, and if it happens again, try a new user.

Have a good day!

[Marvin]

@petsam

Please, post : 

pacman -Q xf86-video-intel

If that package is installed, you can try uninstalling it and testing for improvement.

At the risk of sounding like an Oscar speech …

As this problem was transient in the first place and i am thinking of doing a re-install to move to the LXQt version plus the fault has not reoccurred since removing the driver suggested by petsam in post 21, above. It would seem sensible to mark this issue as solved and post 21 by petsam as the solution. Thank you petsam.

However, there were a number of other extremely helpful contributions in other posts and i would like to thank everyone else who posted those ideas too.

Thank you also to everyone who even read this post.
Marvin, 2023-02-15