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 40 times
LoginFailureBootLog.txt
Boot log from login failure session
(225.67 KiB) Downloaded 28 times
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 338
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: 338
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 27 times
LoginFailureBootlog-20210329.txt
Bootlog after login freeze on March 29
(216.94 KiB) Downloaded 30 times
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 338
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: 972
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: 16726
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: 338
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Login screen freezes the computer when I log in

Postby banjo » May 7th, '21, 18:15

It has been a while since I posted an update. I am still looking into this because it is still happening.This is taking a while because the hangup is intermittent and I do not know how to force it to happen.

I had uninstalled the Nvidia 340 driver a while ago to see if that would help with the problem, but it has not.

SDDM stalled twice in a row this morning. The keyboard and the mouse buttons do nothing. I cannot Ctrl-Alt<fn> to get up a console, and I have to use the power button to shut down the computer.

On the third try I could log in successfully. I have captured the boot logs from the failed attempts to see if I can figure out what is going on.

Some interesting things going on around line 1420 in the file LoginFailureBooting-20210507-2.txt. D-Bus gets stopped, and then plasma-kglobalaccel.service goes into a loop timing out. Is it waiting on something from D-Bus? I don't know much about the startup sequence.

Code: Select all
May 07 10:33:01 BSKMageia9 systemd[5116]: Starting KDE Global Shortcuts Server...
May 07 10:33:02 BSKMageia9 dbus-daemon[5209]: [session uid=1000 pid=5209] Activating via systemd: service name='ca.desrt.dconf' unit='dconf.service' requested by ':1.6' (uid=1000 pid=5235 comm="/usr/bin/kded5")
May 07 10:33:02 BSKMageia9 systemd[5116]: Starting User preferences database...
May 07 10:33:02 BSKMageia9 dbus-daemon[5209]: [session uid=1000 pid=5209] Successfully activated service 'ca.desrt.dconf'
May 07 10:33:02 BSKMageia9 systemd[5116]: Started User preferences database.
May 07 10:33:06 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: start operation timed out. Terminating.
May 07 10:33:06 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: Failed with result 'timeout'.
May 07 10:33:06 BSKMageia9 systemd[5116]: Failed to start KDE Global Shortcuts Server.
May 07 10:33:06 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 1.
May 07 10:33:06 BSKMageia9 systemd[5116]: Stopped KDE Global Shortcuts Server.
May 07 10:33:06 BSKMageia9 systemd[5116]: Starting KDE Global Shortcuts Server...
May 07 10:33:08 BSKMageia9 systemd[1]: Stopping User Manager for UID 981...
May 07 10:33:08 BSKMageia9 systemd[3560]: Stopped target Main User Target.
May 07 10:33:08 BSKMageia9 systemd[3560]: Stopping D-Bus User Message Bus...
May 07 10:33:08 BSKMageia9 systemd[3560]: Stopping GnuPG cryptographic agent and passphrase cache...
May 07 10:33:08 BSKMageia9 gpg-agent[3571]: SIGTERM received - shutting down ...
May 07 10:33:08 BSKMageia9 systemd[3560]: dbus.service: Deactivated successfully.
May 07 10:33:08 BSKMageia9 systemd[3560]: Stopped D-Bus User Message Bus.
May 07 10:33:08 BSKMageia9 gpg-agent[3571]: gpg-agent (GnuPG) 2.3.1 stopped
May 07 10:33:08 BSKMageia9 systemd[3560]: gpg-agent.service: Deactivated successfully.
May 07 10:33:08 BSKMageia9 systemd[3560]: Stopped GnuPG cryptographic agent and passphrase cache.
May 07 10:33:08 BSKMageia9 systemd[3560]: Stopped target Basic System.
May 07 10:33:08 BSKMageia9 systemd[3560]: Stopped target Paths.
May 07 10:33:08 BSKMageia9 systemd[3560]: Stopped target Sockets.
May 07 10:33:08 BSKMageia9 systemd[3560]: Stopped target Timers.
May 07 10:33:08 BSKMageia9 systemd[3560]: dbus.socket: Deactivated successfully.
May 07 10:33:08 BSKMageia9 systemd[3560]: Closed D-Bus User Message Bus Socket.
May 07 10:33:08 BSKMageia9 systemd[3560]: gpg-agent.socket: Deactivated successfully.
May 07 10:33:08 BSKMageia9 systemd[3560]: Closed GnuPG cryptographic agent and passphrase cache.
May 07 10:33:08 BSKMageia9 systemd[3560]: pulseaudio.socket: Deactivated successfully.
May 07 10:33:08 BSKMageia9 systemd[3560]: Closed Sound System.
May 07 10:33:08 BSKMageia9 systemd[3560]: Removed slice User Application Slice.
May 07 10:33:08 BSKMageia9 systemd[3560]: Reached target Shutdown.
May 07 10:33:08 BSKMageia9 systemd[3560]: systemd-exit.service: Deactivated successfully.
May 07 10:33:08 BSKMageia9 systemd[3560]: Finished Exit the Session.
May 07 10:33:08 BSKMageia9 systemd[3560]: Reached target Exit the Session.
May 07 10:33:08 BSKMageia9 systemd[1]: user@981.service: Deactivated successfully.
May 07 10:33:08 BSKMageia9 systemd[1]: Stopped User Manager for UID 981.
May 07 10:33:08 BSKMageia9 systemd[1]: Stopping User Runtime Directory /run/user/981...
May 07 10:33:08 BSKMageia9 systemd[1]: user-runtime-dir@981.service: Deactivated successfully.
May 07 10:33:08 BSKMageia9 systemd[5116]: run-user-981.mount: Deactivated successfully.
May 07 10:33:08 BSKMageia9 systemd[1]: Stopped User Runtime Directory /run/user/981.
May 07 10:33:08 BSKMageia9 systemd[1]: Removed slice User Slice of UID 981.
May 07 10:33:08 BSKMageia9 systemd[1]: user-981.slice: Consumed 1.180s CPU time.
May 07 10:33:12 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: start operation timed out. Terminating.
May 07 10:33:12 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: Failed with result 'timeout'.
May 07 10:33:12 BSKMageia9 systemd[5116]: Failed to start KDE Global Shortcuts Server.
May 07 10:33:12 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 2.
May 07 10:33:12 BSKMageia9 systemd[5116]: Stopped KDE Global Shortcuts Server.
May 07 10:33:12 BSKMageia9 systemd[5116]: Starting KDE Global Shortcuts Server...
May 07 10:33:17 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: start operation timed out. Terminating.
May 07 10:33:17 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: Failed with result 'timeout'.
May 07 10:33:17 BSKMageia9 systemd[5116]: Failed to start KDE Global Shortcuts Server.
May 07 10:33:17 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 3.
May 07 10:33:17 BSKMageia9 systemd[5116]: Stopped KDE Global Shortcuts Server.
May 07 10:33:17 BSKMageia9 systemd[5116]: Starting KDE Global Shortcuts Server...
May 07 10:33:23 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: start operation timed out. Terminating.
May 07 10:33:23 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: Failed with result 'timeout'.
May 07 10:33:23 BSKMageia9 systemd[5116]: Failed to start KDE Global Shortcuts Server.
May 07 10:33:23 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 4.
May 07 10:33:23 BSKMageia9 systemd[5116]: Stopped KDE Global Shortcuts Server.
May 07 10:33:23 BSKMageia9 systemd[5116]: Starting KDE Global Shortcuts Server...
May 07 10:33:25 BSKMageia9 ksmserver[5236]: Couldn't start kglobalaccel from org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.")
May 07 10:33:28 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: start operation timed out. Terminating.
May 07 10:33:28 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: Failed with result 'timeout'.
May 07 10:33:28 BSKMageia9 systemd[5116]: Failed to start KDE Global Shortcuts Server.
May 07 10:33:28 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 5.
May 07 10:33:28 BSKMageia9 systemd[5116]: Stopped KDE Global Shortcuts Server.
May 07 10:33:28 BSKMageia9 systemd[5116]: Starting KDE Global Shortcuts Server...
May 07 10:33:29 BSKMageia9 systemd[1]: systemd-hostnamed.service: Deactivated successfully.
May 07 10:33:34 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: start operation timed out. Terminating.
May 07 10:33:34 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: Failed with result 'timeout'.
May 07 10:33:34 BSKMageia9 systemd[5116]: Failed to start KDE Global Shortcuts Server.
May 07 10:33:34 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 6.
May 07 10:33:34 BSKMageia9 systemd[5116]: Stopped KDE Global Shortcuts Server.
May 07 10:33:34 BSKMageia9 systemd[5116]: Starting KDE Global Shortcuts Server...
May 07 10:33:39 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: start operation timed out. Terminating.
May 07 10:33:39 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: Failed with result 'timeout'.
May 07 10:33:39 BSKMageia9 systemd[5116]: Failed to start KDE Global Shortcuts Server.
May 07 10:33:39 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 7.
May 07 10:33:39 BSKMageia9 systemd[5116]: Stopped KDE Global Shortcuts Server.
May 07 10:33:39 BSKMageia9 systemd[5116]: Starting KDE Global Shortcuts Server...
May 07 10:33:45 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: start operation timed out. Terminating.
May 07 10:33:45 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: Failed with result 'timeout'.
May 07 10:33:45 BSKMageia9 systemd[5116]: Failed to start KDE Global Shortcuts Server.
May 07 10:33:45 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 8.
May 07 10:33:45 BSKMageia9 systemd[5116]: Stopped KDE Global Shortcuts Server.
May 07 10:33:45 BSKMageia9 systemd[5116]: Starting KDE Global Shortcuts Server...
May 07 10:33:50 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: start operation timed out. Terminating.
May 07 10:33:50 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: Failed with result 'timeout'.
May 07 10:33:50 BSKMageia9 systemd[5116]: Failed to start KDE Global Shortcuts Server.
May 07 10:33:50 BSKMageia9 systemd[5116]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 9.
May 07 10:33:50 BSKMageia9 systemd[5116]: Stopped KDE Global Shortcuts Server.
May 07 10:33:50 BSKMageia9 systemd[5116]: Starting KDE Global Shortcuts Server...
May 07 10:33:54 BSKMageia9 chronyd[920]: Selected source 163.237.218.19 (pool.ntp.org)
May 07 10:33:54 BSKMageia9 systemd-logind[780]: Power key pressed.
May 07 10:33:54 BSKMageia9 systemd-logind[780]: Powering Off...
May 07 10:33:54 BSKMageia9 systemd-logind[780]: System is powering down.
May 07 10:33:54 BSKMageia9 sddm[3281]: Authentication error: "Process crashed"
May 07 10:33:54 BSKMageia9 sddm[3281]: Auth: sddm-helper crashed (exit code 15)
May 07 10:33:54 BSKMageia9 sddm[3281]: Authentication error: "Process crashed"
May 07 10:33:54 BSKMageia9 sddm[3281]: Auth: sddm-helper exited with 15
May 07 10:33:54 BSKMageia9 systemd[1]: Stopping Session c2 of user poobah.
May 07 10:33:54 BSKMageia9 systemd[1]: Removed slice system-getty.slice.
May 07 10:33:54 BSKMageia9 systemd[1]: Removed slice system-modprobe.slice.


I might try creating a new user to see if that helps, but the problem shows up intermittently so I won't know much if a new user works OK for a while.
Attachments
LoginGoodBootlog-20210507.txt
Successful boot (third try)
(184.67 KiB) Downloaded 19 times
LoginFailureBootlog-20210507-2.txt
Second boot failure
(156.73 KiB) Downloaded 17 times
LoginFailureBootlog-20210507-1.txt
First boot failure
(195.41 KiB) Downloaded 19 times
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 338
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Login screen freezes the computer when I log in

Postby banjo » May 8th, '21, 03:26

Quick update.

I have switched over to LightDM from SDDM to see if that helps with this problem. If it works OK with LightDM then maybe it is being caused by SDDM.

This will take a while because it will require many boots and logins to convince myself that the problem is gone.
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 338
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Login screen freezes the computer when I log in

Postby banjo » May 19th, '21, 16:21

I have been running LightDM now for a couple of weeks, using it to log into Plasma. I have seen no lockups at all, so I am assuming that the problem has something to do with SDDM.

One thing that I have noticed is that updatedb is hammering the disk when I try to log in. It is not taking a lot of CPU cycles, but it is hitting the disk pretty hard. I don't know if that could be related to this problem, but it slows down the boot and the login. So I have moved the running of mlocate-updatedb from boot time to 30 minutes after boot in order to avoid a conflict with my attempt to log in. I have also started using SDDM again to see if that change will have any effect on the freezes.

Given that there are no "me too" responses to this post from the community, I am assuming that there is something unique in my setup that is conflicting with SDDM or crashing something that SDDM uses. I still cannot reproduce this problem on demand, so I will have to run a while to see if I get any freezes.
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 338
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Login screen freezes the computer when I log in

Postby janpihlgren » May 20th, '21, 05:47

Hi
I can tell you that I have the same problem with 2 different user. I have no resolution.
I don't know if this is the same problem but your description likes mine.
Just for your information.
User avatar
janpihlgren
 
Posts: 292
Joined: Mar 30th, '11, 12:23
Location: Marsta, Sweden

Re: Login screen freezes the computer when I log in

Postby morgano » May 20th, '21, 07:35

Jan, are you running Mageia 8 or Cauldron?
Mandriva since 2006, then Mageia since 2011 at home & work. Thinkpad T43 & T400, Dell M4400, Acer Aspire 7. Workstation using LVM, LUKS, VirtualBox, BOINC
morgano
 
Posts: 793
Joined: Jun 15th, '11, 17:51
Location: Kivik, Sweden

Re: Login screen freezes the computer when I log in

Postby janpihlgren » May 20th, '21, 08:06

Mageia 8
User avatar
janpihlgren
 
Posts: 292
Joined: Mar 30th, '11, 12:23
Location: Marsta, Sweden

Re: Login screen freezes the computer when I log in

Postby banjo » May 20th, '21, 14:14

I am not running the released Mag 8 yet, so I cannot confirm whether the problem exists on that version. I will keep an eye out for it after I upgrade.

So far, the workaround that I have is to use LightDM.
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 338
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Login screen freezes the computer when I log in

Postby banjo » May 31st, '21, 17:17

A couple of weeks ago I moved the execution time of mlocate-updatedb so that it runs a half hour after bootup instead of at bootup. I thought that it might be causing a deadlock situation with SDDM resulting in the hanging system.

The change has not helped. Yesterday, I saw another freeze of SDDM. The execution of mlocate-updatedb is off the hook for causing this problem.

The boot log is attached.

After the freeze there is always a sequence of timeouts with plasma-polkit-agent.service and plasma-powerdevil.service. The timeouts are shown in the following snippet from the boot log.

Code: Select all
May 30 13:58:32 BSKMageia9 systemd[5090]: plasma-polkit-agent.service: start operation timed out. Terminating.
May 30 13:58:32 BSKMageia9 systemd[5090]: plasma-powerdevil.service: start operation timed out. Terminating.
May 30 13:58:32 BSKMageia9 systemd[5090]: plasma-polkit-agent.service: Failed with result 'timeout'.
May 30 13:58:32 BSKMageia9 systemd[5090]: Failed to start KDE PolicyKit Authentication Agent.
May 30 13:58:32 BSKMageia9 systemd[5090]: plasma-powerdevil.service: Failed with result 'timeout'.
May 30 13:58:32 BSKMageia9 systemd[5090]: Failed to start Powerdevil.
May 30 13:58:32 BSKMageia9 systemd[5090]: plasma-polkit-agent.service: Scheduled restart job, restart counter is at 1.
May 30 13:58:32 BSKMageia9 systemd[5090]: plasma-powerdevil.service: Scheduled restart job, restart counter is at 1.
May 30 13:58:32 BSKMageia9 systemd[5090]: Stopped KDE PolicyKit Authentication Agent.
May 30 13:58:32 BSKMageia9 systemd[5090]: Starting KDE PolicyKit Authentication Agent...
May 30 13:58:32 BSKMageia9 systemd[5090]: Stopped Powerdevil.
May 30 13:58:32 BSKMageia9 systemd[5090]: Starting Powerdevil...
May 30 13:58:38 BSKMageia9 systemd[5090]: plasma-polkit-agent.service: start operation timed out. Terminating.
May 30 13:58:38 BSKMageia9 systemd[5090]: plasma-powerdevil.service: start operation timed out. Terminating.
May 30 13:58:38 BSKMageia9 systemd[5090]: plasma-polkit-agent.service: Failed with result 'timeout'.
May 30 13:58:38 BSKMageia9 systemd[5090]: Failed to start KDE PolicyKit Authentication Agent.
May 30 13:58:38 BSKMageia9 systemd[5090]: plasma-powerdevil.service: Failed with result 'timeout'.
May 30 13:58:38 BSKMageia9 systemd[5090]: Failed to start Powerdevil.
May 30 13:58:38 BSKMageia9 systemd[5090]: plasma-polkit-agent.service: Scheduled restart job, restart counter is at 2.
May 30 13:58:38 BSKMageia9 systemd[5090]: plasma-powerdevil.service: Scheduled restart job, restart counter is at 2.
May 30 13:58:38 BSKMageia9 systemd[5090]: Stopped KDE PolicyKit Authentication Agent.
May 30 13:58:38 BSKMageia9 systemd[5090]: Starting KDE PolicyKit Authentication Agent...
May 30 13:58:38 BSKMageia9 systemd[5090]: Stopped Powerdevil.

    etc   



Because of the intermittent nature of the problem, this really looks like a deadlock situation. It is not clear to me what those services are waiting for.

Here are the timeout values for the services.

Code: Select all
# systemctl show plasma-polkit-agent | grep Timeout
TimeoutStartUSec=1min 30s
TimeoutStopUSec=1min 30s
TimeoutAbortUSec=1min 30s
TimeoutStartFailureMode=terminate
TimeoutStopFailureMode=terminate
TimeoutCleanUSec=infinity
JobTimeoutUSec=infinity
JobRunningTimeoutUSec=infinity
JobTimeoutAction=none
#
# systemctl show plasma-powerdevil | grep Timeout
TimeoutStartUSec=1min 30s
TimeoutStopUSec=1min 30s
TimeoutAbortUSec=1min 30s
TimeoutStartFailureMode=terminate
TimeoutStopFailureMode=terminate
TimeoutCleanUSec=infinity
JobTimeoutUSec=infinity
JobRunningTimeoutUSec=infinity
JobTimeoutAction=none



The timeouts that I am seeing appear to occur every 5 seconds. I don't see that value in any of the agent timeouts.

The timeouts of the two services may be just a symptom of the freeze, not a cause.

I will keep looking.
Attachments
LoginFailureBootlog-20210530.txt
Boot log of system freeze at login.
(181.39 KiB) Downloaded 15 times
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 338
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Login screen freezes the computer when I log in

Postby doktor5000 » May 31st, '21, 17:56

banjo wrote:The timeouts that I am seeing appear to occur every 5 seconds. I don't see that value in any of the agent timeouts.

No, the startup timeouts occur exactly after those 1:30 min timeouts:


Code: Select all
May 30 13:56:57 BSKMageia9 systemd[5090]: Reached target Session services which should run early before the graphical session is brought up.
May 30 13:56:57 BSKMageia9 systemd[5090]: Starting KDE Config Module Initialization...
May 30 13:56:57 BSKMageia9 systemd[5090]: Starting KDE Daemon...
May 30 13:56:57 BSKMageia9 systemd[5090]: Starting KDE Session Management Server...
May 30 13:56:57 BSKMageia9 systemd[5090]: Starting KDE Window Manager...

[...]

May 30 13:58:27 BSKMageia9 systemd[5090]: plasma-kwin_x11.service: start operation timed out. Terminating.
May 30 13:58:27 BSKMageia9 systemd[5090]: plasma-kcminit.service: start operation timed out. Terminating.
May 30 13:58:27 BSKMageia9 systemd[5090]: plasma-ksmserver.service: start operation timed out. Terminating.
May 30 13:58:27 BSKMageia9 systemd[5090]: plasma-kcminit.service: Failed with result 'timeout'.
May 30 13:58:27 BSKMageia9 systemd[5090]: Failed to start KDE Config Module Initialization.
May 30 13:58:27 BSKMageia9 systemd[5090]: Dependency failed for KDE Configuration Module Initialization (Phase 1).
May 30 13:58:27 BSKMageia9 systemd[5090]: plasma-kcminit-phase1.service: Job plasma-kcminit-phase1.service/start failed with result 'dependency'.
May 30 13:58:27 BSKMageia9 systemd[5090]: plasma-ksmserver.service: Failed with result 'timeout'.
May 30 13:58:27 BSKMageia9 systemd[5090]: Failed to start KDE Session Management Server.
May 30 13:58:27 BSKMageia9 systemd[5090]: Dependency failed for KDE Plasma Workspace Core.
May 30 13:58:27 BSKMageia9 systemd[5090]: Dependency failed for KDE Plasma Workspace.
May 30 13:58:27 BSKMageia9 systemd[5090]: plasma-workspace@x11.target: Job plasma-workspace@x11.target/start failed with result 'dependency'.
May 30 13:58:27 BSKMageia9 systemd[5090]: plasma-core.target: Job plasma-core.target/start failed with result 'dependency'.
May 30 13:58:27 BSKMageia9 systemd[5090]: plasma-kwin_x11.service: Failed with result 'timeout'.
May 30 13:58:27 BSKMageia9 systemd[5090]: Failed to start KDE Window Manager.


On a related note, as one of the last services that runs before the issue occurs is systemd-hostnamed - are you sure that you have set a proper hostname in /etc/hostname and also don't get another one e.g. via DHCP from one of your network connections ?

Apart from that, you didn't answer the question yet if this also occurs for a freshly created user.
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: 16726
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Login screen freezes the computer when I log in

Postby banjo » May 31st, '21, 20:10

Thanks for the response.

The hostname is set in /etc/hostname.

Code: Select all
$ cat /etc/hostname
BSKMageia9


I am not sure how to tell if I got another one from DHCP. Is that in a log somewhere? So I logged into the router, and the DHCP lease for this IP has the host name "new-host-3". I have no idea where the router got that name. Is that an issue? I can rename this computer to "new-host-3" if that will fix it. Or maybe I can change it in the router. I have no special attachment to its current name.

I remember seeing this issue mentioned before when the name "localhost" is left unchanged, which is why I changed the name to BSKMageia9. I don't remember what the connection is between the hostname and the inability to log in.

Apart from that, you didn't answer the question yet if this also occurs for a freshly created user.


I have not done that yet. This is a very intermittent problem. It takes two weeks of logging in and out to see this happen. I cannot reproduce the problem on demand.
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 338
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Login screen freezes the computer when I log in

Postby doktor5000 » May 31st, '21, 21:25

banjo wrote:I remember seeing this issue mentioned before when the name "localhost" is left unchanged, which is why I changed the name to BSKMageia9. I don't remember what the connection is between the hostname and the inability to log in.

Well, that is only one part of the puzzle. The authentication for the X server, so called magic cookie, is tied to the hostname. See also https://www.x.org/wiki/Development/Docu ... /Security/
If the hostname changes during the runtime, that is usually when things can go wrong.
That's why you should ensure that A) a proper static hostname is configured locally and B) that your box does not pull a new hostname via DHCP so that your router does not set a new hostname.

Seems you already did A) but you also need to check for B). It depends how you configured your network connections, whether you used net_applet or networkmanager - or maybe even something different.
But looking through your logs there do seem to be at least two different wifi connections you should probably check and maybe re-do them.
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: 16726
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Login screen freezes the computer when I log in

Postby banjo » May 31st, '21, 22:32

Doktor,

Thanks for the input.

I also found this bug report about SDDM showing only a black screen.

https://bugs.mageia.org/show_bug.cgi?id=27601

In comment 13, a recommendation was to change the hostname using hostnamectl. I originally changed it by editing the /etc/hostname file directly

So I have changed the name to BSKMageia9.local as recommended in the bug report, using hostnamectl.

Code: Select all
[root@BSKMageia9 ~]# hostnamectl set-hostname BSKMageia9.local
[root@BSKMageia9 ~]# hostnamectl status
 Static hostname: BSKMageia9.local
       Icon name: computer-desktop
         Chassis: desktop
      Machine ID: 1b6838b526e0410f9b9bec5a321415be
         Boot ID: 967432590cd6410e942fabf4055008f4
Operating System: Mageia 9                       
          Kernel: Linux 5.12.8-desktop-1.mga9
    Architecture: x86-64
 Hardware Vendor: System manufacturer
  Hardware Model: System Product Name
[root@BSKMageia9 ~]# cat /etc/hostname
BSKMageia9.local
[root@BSKMageia9 ~]#


The original Static Hostname was just "BSKMageia9", and now it is "BSKMageia9.local" as reported by hostnamectl.

According to the hostnamctl man page, the command sets more than just the hostname file.

Set the system hostname to NAME. By default, this will alter the pretty, the static, and the transient hostname alike;


and if the static hostname is set, a transient hostname is not used.

If a static hostname is set to a valid value, then the transient hostname is not used.


I wish I could force this issue, but I cannot so I can only try it for a few days and see if it hangs.

I set up the WiFi connection using the network manager. I will go check that out and see about reconfiguring it.
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 338
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Login screen freezes the computer when I log in

Postby doktor5000 » Jun 1st, '21, 16:59

banjo wrote:According to the hostnamctl man page, the command sets more than just the hostname file.

Yes and no - check the man-page for systemd-hostnamed.service. It will also update /etc/machine-id with the transient and pretty hostname, but as those are set to the same value as the hostname, and as those are not used once a valid static hostname has been set they don't matter.
So for a proper hostname it doesn't matter if you only directly put it in /etc/hostname or set it via hostnamectl, if you reboot afterwards once.

It also doesn't matter if you add .local or not - once you set a valid static hostname and ensure you don't get a different one via DHCP, then it will not change.
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: 16726
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Login screen freezes the computer when I log in

Postby banjo » Jun 1st, '21, 20:26

Thanks for the additional information. I set the host name back in Feb or March, so it has been there for a few months. That seems to rule out a transient hostname causing this issue.
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 338
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Login screen freezes the computer when I log in

Postby doktor5000 » Jun 1st, '21, 21:51

Not really, no - if you still get a hostname via DHCP then it would still change during boot / login. From what I remember DHCP defaults to automatic for networkmanager.
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: 16726
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Login screen freezes the computer when I log in

Postby banjo » Jun 2nd, '21, 00:31

It is set to Automatic. I thought that was to allow the router to modify the IP address when it needs to. I didn't know that it had anything to do with the hostname. The computer does not have a static IP address, but the IP has not changed since I first connected it.

I will do some more research on how all that hangs together.
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 338
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Login screen freezes the computer when I log in

Postby doktor5000 » Jun 2nd, '21, 00:58

DHCP is used to assign an IP adress and also other information, like a hostname, DNS servers, a DNS suffix search list among others. Usually routers will assign the same IP adress to a device, if it requests an IP adress via DHCP as long as the lease time (the timespan for which your DHCP information is valid) has not expired. You can set your router to always assign the same IP adress to a device, which is usually referred to as "static" DHCP. And on your client, you should check networkmanager settings so that it does not change the hostname when getting an adress via DHCP.

If you want to disable this globally and not per connection, you could try to add
Code: Select all
hostname-mode=none
to the [main] section of /etc/MetworkManager/NetworkManager.conf
Also check the man-page for NetworkManager.conf for more details on the hostname-mode option. But I'd suggest to only edit your existing connections, and not the default.
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: 16726
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Login screen freezes the computer when I log in

Postby banjo » Jun 2nd, '21, 02:17

Thanks. I will check it out.
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 338
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Next

Return to Testing : Alpha, Beta, RC and Cauldron

Who is online

Users browsing this forum: No registered users and 1 guest

cron