Login screen freezes the computer when I log in

This forum is dedicated to testing early releases and cauldron : Howtos, tips, tricks and user global feedback and thoughts...

Helpful tip :
For bugs tracking we use : https://bugs.mageia.org = The Mageia Bug Tracker
In this bug tracker you'll find already reported bugs and you'll be able to report those you have found....

Login screen freezes the computer when I log in

Postby banjo » Mar 18th, '21, 17:23

I am running Cauldron. Sometimes, when I attempt to log in to Plasma, the screen freezes completely. The symptoms are:

It works fine through the input of the password.
When I click the Login button, everything freezes except the mouse cursor.
The clock display freezes.
None of the buttons or menus is responsive.
I cannot bring up a console using any of the Ctr-Alt-F<n> sequences.
The disk drive access light is on steady, but eventually goes out. (probably the file system indexing task)

I have to shut the computer down by holding in the power button.

When I reboot, everything works fine.

After the successful boot I dumped out the logs for the good boot and the failed boot, which are attached.

I noticed in the failed boot, an error around line 1567, "Failed to start KDE Session Management Server.". That error is not found in the bootlog for the successful boot.

Code: Select all
Mar 18 09:33:25 BSKMageia9 systemd[1]: systemd-hostnamed.service: Succeeded.
Mar 18 09:33:31 BSKMageia9 kcminit_startup[8329]: QProcess: Destroyed while process ("xrdb") is still running.
Mar 18 09:34:28 BSKMageia9 systemd[8206]: plasma-kcminit.service: start operation timed out. Terminating.
Mar 18 09:34:28 BSKMageia9 systemd[8206]: plasma-ksmserver.service: start operation timed out. Terminating.
Mar 18 09:34:28 BSKMageia9 systemd[8206]: plasma-kwin_x11.service: start operation timed out. Terminating.
Mar 18 09:34:28 BSKMageia9 systemd[8206]: plasma-ksmserver.service: Failed with result 'timeout'.
Mar 18 09:34:28 BSKMageia9 systemd[8206]: Failed to start KDE Session Management Server.
Mar 18 09:34:28 BSKMageia9 systemd[8206]: Dependency failed for KDE Plasma Workspace Core.
Mar 18 09:34:28 BSKMageia9 systemd[8206]: Dependency failed for KDE Plasma Workspace.
Mar 18 09:34:28 BSKMageia9 systemd[8206]: plasma-workspace@x11.target: Job plasma-workspace@x11.target/start failed with result 'dependency'.
Mar 18 09:34:28 BSKMageia9 systemd[8206]: plasma-core.target: Job plasma-core.target/start failed with result 'dependency'.
Mar 18 09:34:28 BSKMageia9 systemd[8206]: plasma-kwin_x11.service: Failed with result 'timeout'.
Mar 18 09:34:28 BSKMageia9 systemd[8206]: Failed to start KDE Window Manager.
Mar 18 09:34:28 BSKMageia9 systemd[8206]: Reached target Current graphical user session.


This is an intermittent problem. I cannot reproduce it on demand. I thought that it might be related to this problem:

https://forums.mageia.org/en/viewtopic.php?f=7&t=13964

but that seems to have been resolved by removing extra .Xauthority files. My system does not appear to have that problem.

Code: Select all
[poobah@BSKMageia9 ~]$ ll -a | grep authority
-rw-------  1 poobah poobah        0 Dec 31 10:09 .ICEauthority
-rw-------  1 poobah poobah      299 Mar 18 09:41 .Xauthority


Here is my inxi info

Code: Select all
$ inxi -b
System:    Host: BSKMageia9 Kernel: 5.11.6-desktop-4.mga9 x86_64 bits: 64 Desktop: KDE Plasma 5.21.2 Distro: Mageia 9 mga9
Machine:   Type: Desktop Mobo: ASUSTeK model: P5G41T-M LX PLUS v: Rev X.0x serial: <superuser required>
           BIOS: American Megatrends v: 0502 date: 10/21/2011
CPU:       Info: Dual Core Intel Core2 Duo E7300 [MCP] speed: 2667 MHz
Graphics:  Device-1: NVIDIA G94 [GeForce 9600 GT] driver: nouveau v: kernel
           Display: x11 server: Mageia X.org 1.20.10 driver: loaded: nouveau,v4l resolution: 1920x1080~60Hz
           OpenGL: renderer: NV94 v: 3.3 Mesa 21.0.0
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
           Device-2: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter driver: 8139too
           Device-3: Qualcomm Atheros AR9271 802.11n type: USB driver: ath9k_htc
Drives:    Local Storage: total: 465.76 GiB used: 34.13 GiB (7.3%)
Info:      Processes: 183 Uptime: 24m Memory: 3.84 GiB used: 1.34 GiB (34.9%) Shell: Bash inxi: 3.3.01


Banjo
(_)=='=~
Attachments
LoginGoodBootLog.txt
Boot log from successful login session
(206.69 KiB) Downloaded 8 times
LoginFailureBootLog.txt
Boot log from login failure session
(225.67 KiB) Downloaded 5 times
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 318
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Login screen freezes the computer when I log in

Postby papoteur » Mar 19th, '21, 16:49

Hello,
What I see in the failing boot:
Mar 18 09:33:31 BSKMageia9 kcminit_startup[8329]: QProcess: Destroyed while process ("xrdb") is still running.

I don't know if it was killed because not responding or because the startup sequence decided to stop the start sequence.
Perhaps it's this process which is killed:
https://phabricator.kde.org/source/plas ... ma.cpp$297
xrdb -quiet -merge -nocpp
To get information about the screen.
Did you change screen or connected a second one?
papoteur
 
Posts: 52
Joined: Oct 27th, '11, 22:28

Re: Login screen freezes the computer when I log in

Postby banjo » Mar 19th, '21, 18:19

Did you change screen or connected a second one?


Nope. The same monitor has been connected for many months and working fine.

What is really odd is that it freezes the entire computer. I can't even get a console to run with Ctrl-Alt-F<n>.

The heavy disk drive access finally settles down and stops, and the computer is still frozen. So it isn't trapped in a disk IRQ or something weird like that. I can't tell if the CPU is locked in a loop. But then, it has two cores, so you would think one of them might have cycles left anyway. The computer does track the mouse cursor, so the graphics are working.

I don't know how to test it since I cannot replicate the problem on demand. I just happens sometimes. I can't test to see if it works with ICE since it works with Plasma most of the time anyway, so running ICE won't tell me anything.

I am using a wireless mouse of dubious source that I bought on ebay. I might swap in a wired mouse to see what happens. But that won't help much since I cannot reproduce the problem, and if it works with a wired mouse, so what?

I think that each time I saw this, I had booted the computer and walked away, and then I tried to log in later. But I may be misremembering that. I will give that go and see if I can force this to happen.

I am grasping at straws.

Thanks for the pointer.
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 318
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Login screen freezes the computer when I log in

Postby banjo » Apr 10th, '21, 20:05

I still cannot reproduce this problem on demand, but it has reoccurred a couple of times since my previous post. It appears to be completely random.

The symptoms remain the same. The entire system locks up on the SDDM login page except for the mouse cursor. I cannot open a console with Ctrl-Alt-F(n). I cannot reboot with Ctrl-Alt-Delete. Nothing works. It is not hammering the disk or anything else that I can see. It simply shows no response to any keyboard or mouse button inputs.

After shutting down the system with the power button it will reboot and run normally. It will boot and fun for days with no problems and then randomly freeze again.

I have attached boot logs from the previous two failures. At the end of the file LoginFailureBootlog-20210410.txt it appears to be stuck in a loop trying to start Powerdevil, KDE Plasma Workspace, and KDE PolicyKit Authentication Agent. See partial extract below from the end of the file.

Code: Select all
Apr 10 09:52:10 BSKMageia9 systemd[8545]: Starting Powerdevil...
Apr 10 09:52:16 BSKMageia9 systemd[8545]: plasma-polkit-agent.service: start operation timed out. Terminating.
Apr 10 09:52:16 BSKMageia9 systemd[8545]: plasma-powerdevil.service: start operation timed out. Terminating.
Apr 10 09:52:16 BSKMageia9 systemd[8545]: plasma-polkit-agent.service: Failed with result 'timeout'.
Apr 10 09:52:16 BSKMageia9 systemd[8545]: Failed to start KDE PolicyKit Authentication Agent.
Apr 10 09:52:16 BSKMageia9 systemd[8545]: plasma-powerdevil.service: Failed with result 'timeout'.
Apr 10 09:52:16 BSKMageia9 systemd[8545]: Failed to start Powerdevil.
Apr 10 09:52:16 BSKMageia9 systemd[8545]: plasma-polkit-agent.service: Scheduled restart job, restart counter is at 105.
Apr 10 09:52:16 BSKMageia9 systemd[8545]: plasma-powerdevil.service: Scheduled restart job, restart counter is at 105.
Apr 10 09:52:16 BSKMageia9 systemd[8545]: Stopped KDE PolicyKit Authentication Agent.
Apr 10 09:52:16 BSKMageia9 systemd[8545]: Starting KDE PolicyKit Authentication Agent...
Apr 10 09:52:16 BSKMageia9 systemd[8545]: Stopped Powerdevil.
Apr 10 09:52:16 BSKMageia9 systemd[8545]: Starting Powerdevil...
Apr 10 09:52:20 BSKMageia9 systemd[8545]: plasma-plasmashell.service: start operation timed out. Terminating.
Apr 10 09:52:20 BSKMageia9 systemd[8545]: plasma-plasmashell.service: Failed with result 'timeout'.
Apr 10 09:52:20 BSKMageia9 systemd[8545]: Failed to start KDE Plasma Workspace.
Apr 10 09:52:21 BSKMageia9 systemd[8545]: plasma-plasmashell.service: Scheduled restart job, restart counter is at 5.
Apr 10 09:52:21 BSKMageia9 systemd[8545]: Stopped KDE Plasma Workspace.
Apr 10 09:52:21 BSKMageia9 systemd[8545]: plasma-polkit-agent.service: start operation timed out. Terminating.
Apr 10 09:52:21 BSKMageia9 systemd[8545]: plasma-powerdevil.service: start operation timed out. Terminating.
Apr 10 09:52:21 BSKMageia9 systemd[8545]: plasma-polkit-agent.service: Failed with result 'timeout'.
Apr 10 09:52:21 BSKMageia9 systemd[8545]: Failed to start KDE PolicyKit Authentication Agent.
Apr 10 09:52:21 BSKMageia9 systemd[8545]: plasma-powerdevil.service: Failed with result 'timeout'.
Apr 10 09:52:21 BSKMageia9 systemd[8545]: Failed to start Powerdevil.
Apr 10 09:52:21 BSKMageia9 systemd[8545]: plasma-polkit-agent.service: Scheduled restart job, restart counter is at 106.
Apr 10 09:52:21 BSKMageia9 systemd[8545]: plasma-powerdevil.service: Scheduled restart job, restart counter is at 106.
Apr 10 09:52:21 BSKMageia9 systemd[8545]: Stopped KDE PolicyKit Authentication Agent.
Apr 10 09:52:21 BSKMageia9 systemd[8545]: Starting KDE PolicyKit Authentication Agent...
Apr 10 09:52:21 BSKMageia9 systemd[8545]: Stopped Powerdevil.
Apr 10 09:52:21 BSKMageia9 systemd[8545]: Starting Powerdevil...
Apr 10 09:52:27 BSKMageia9 systemd[8545]: plasma-polkit-agent.service: start operation timed out. Terminating.
Apr 10 09:52:27 BSKMageia9 systemd[8545]: plasma-powerdevil.service: start operation timed out. Terminating.
Apr 10 09:52:27 BSKMageia9 systemd[8545]: plasma-polkit-agent.service: Failed with result 'timeout'.
Apr 10 09:52:27 BSKMageia9 systemd[8545]: Failed to start KDE PolicyKit Authentication Agent.
Apr 10 09:52:27 BSKMageia9 systemd[8545]: plasma-powerdevil.service: Failed with result 'timeout'.
Apr 10 09:52:27 BSKMageia9 systemd[8545]: Failed to start Powerdevil.
Apr 10 09:52:27 BSKMageia9 systemd[8545]: plasma-polkit-agent.service: Scheduled restart job, restart counter is at 107.
Apr 10 09:52:27 BSKMageia9 systemd[8545]: plasma-powerdevil.service: Scheduled restart job, restart counter is at 107.
Apr 10 09:52:27 BSKMageia9 systemd[8545]: Stopped KDE PolicyKit Authentication Agent.
Apr 10 09:52:27 BSKMageia9 systemd[8545]: Starting KDE PolicyKit Authentication Agent...
Apr 10 09:52:27 BSKMageia9 systemd[8545]: Stopped Powerdevil.
Apr 10 09:52:27 BSKMageia9 systemd[8545]: Starting Powerdevil...
Apr 10 09:52:30 BSKMageia9 systemd-logind[3069]: Power key pressed.
Apr 10 09:52:30 BSKMageia9 systemd-logind[3069]: Powering Off...
Apr 10 09:52:30 BSKMageia9 systemd-logind[3069]: System is powering down.


I am suspicious that the timeouts are due to a missing resource that has failed somewhere during the boot, but that is just a guess. I do not know what resource they are timing out on.
Attachments
LoginFailureBootlog-20210410.txt
Bootlog after login freeze on April 10.
(285.72 KiB) Downloaded 2 times
LoginFailureBootlog-20210329.txt
Bootlog after login freeze on March 29
(216.94 KiB) Downloaded 2 times
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 318
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Login screen freezes the computer when I log in

Postby benmc » Apr 11th, '21, 07:42

have you considered running a second Desktop Environment and / or Display Manager.

install say Xfce (as root)
Code: Select all
urpmi task-xfce

this will bring in the Xfce desktop and LightDM display manager.
logout and choose Xfce DE and see if the problem persists.
and or run (as root)
Code: Select all
drakdm
and select lightDM (also do-able via MCC => boot tab).

give it a few days, and see if the problem is the Mageia base system (kernel race condition), Plasma DE, Display Manager or your hardware?
benmc
 
Posts: 956
Joined: Sep 2nd, '11, 12:45
Location: Pirongia, New Zealand

Re: Login screen freezes the computer when I log in

Postby doktor5000 » Apr 11th, '21, 14:34

Sometimes that the boot freezes, does that happen after kernel/nvidia updates? You may want to check again what you have installed:

Code: Select all
Mar 29 15:46:13 BSKMageia9 dkms-autorebuild.sh[674]: nvidia340 (340.108-15.mga8.nonfree): Installing module.
Mar 29 15:46:13 BSKMageia9 dkms-autorebuild.sh[674]: dkms build -m nvidia340 -v 340.108-15.mga8.nonfree -k 5.11.10-desktop-1.mga9 -a x86_64 -q --no-clean-kernel
Mar 29 15:47:02 BSKMageia9 dkms-autorebuild.sh[674]: (bad exit status: 10)
Mar 29 15:47:02 BSKMageia9 dkms-autorebuild.sh[674]:   Build failed.  Installation skipped.


The nvidia340 driver has been dropped, even for mga8 - you may want to remove those packages.

You should also check if this same issue during startup occurs with a freshly created user, maybe you have some conflicting settings laying aroung?

Mar 29 15:48:39 BSKMageia9 kcminit_startup[8414]: QProcess: Destroyed while process ("xrdb") is still running.
Mar 29 15:49:36 BSKMageia9 systemd[8291]: plasma-kwin_x11.service: start operation timed out. Terminating.
Mar 29 15:49:36 BSKMageia9 systemd[8291]: plasma-kcminit.service: start operation timed out. Terminating.
Mar 29 15:49:36 BSKMageia9 systemd[8291]: plasma-ksmserver.service: start operation timed out. Terminating.
Mar 29 15:49:36 BSKMageia9 systemd[8291]: plasma-ksmserver.service: Failed with result 'timeout'.
Mar 29 15:49:36 BSKMageia9 systemd[8291]: Failed to start KDE Session Management Server.
Mar 29 15:49:36 BSKMageia9 systemd[8291]: Dependency failed for KDE Plasma Workspace Core.
Mar 29 15:49:36 BSKMageia9 systemd[8291]: Dependency failed for KDE Plasma Workspace.
Mar 29 15:49:36 BSKMageia9 systemd[8291]: plasma-workspace@x11.target: Job plasma-workspace@x11.target/start failed with result 'dependency'.
Mar 29 15:49:36 BSKMageia9 systemd[8291]: plasma-core.target: Job plasma-core.target/start failed with result 'dependency'.
Mar 29 15:49:36 BSKMageia9 systemd[8291]: plasma-kwin_x11.service: Failed with result 'timeout'.
Mar 29 15:49:36 BSKMageia9 systemd[8291]: Failed to start KDE Window Manager.
Mar 29 15:49:36 BSKMageia9 systemd[8291]: Reached target Current graphical user session.


This is where the main KDE/plasma components fail to start up afterwards.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 16463
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Login screen freezes the computer when I log in

Postby banjo » Apr 11th, '21, 15:23

Thanks for the ideas. I will try some of those. Since I don't know how to force this to happen, it will take a while to convince myself that it is fixed by any of the changes.

I have not seen a pattern with the kernel and/or nvidia updates, but that doesn't mean that it isn't there. I think that uninstalling the unused Nvidia drivers would be a good place to start, although they are not being used anymore. Whatever is in deadlock or crashed must be at a fairly low level since it freezes just about everything associated with keyboard and mouse IO.

I have tried logging in using ICE, but it doesn't mean much if that DM works since the problem shows up randomly. It also works most of the time with Plasma.

It could be my hardware as well. It is pretty old. I put it together in 2008, and I mothballed it in 2015 because some of the hardware just didn't work anymore (e.g. optical drive, Intel graphics, etc.). If nobody else is seeing this, it could be my hardware is out of whack with modern software.

I will try to narrow this down some more.
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 318
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts


Return to Testing : Alpha, Beta, RC and Cauldron

Who is online

Users browsing this forum: No registered users and 1 guest

cron