SDDM hangs on login with KDE Plasma (X11)

hacki · 2023-05-03 09:16:54

Hello everyone,

first issue I actually need help with. Please bear with me as I am not a pro at all. If you need any additional info/logs I will gladly post them.

Situation:
A few days ago I noticed that whenever I try to log into my Plasma X11 Session with SDDM that the whole screen freezes. I can put in my password, press enter and then the whole screen will freeze for about 2 minutes. I can still move my mouse around. And I can also switch to a terminal with "Ctrl" + "Alt" + "F3" log in, and also switch back to F2 where the login session resides. When switching back the screen will be black but I can still move my mouse around. After about 2 minutes the splashscreen will pop up and my desktop is finally loaded.

If I use wayland the login works instantly so my best guess is that its a Xorg problem.

What I tried:
- Reinstalling SDDM
- Reading the SDDM wiki and trying out the troubleshooting steps like removing ~/.Xauthority and checking if I have enough space.
- Trying to find anything in the Xorg logs

I am kinda clueless what the problem is. My guess is, that it might have to do something with my Monitor Setup and my Nvidia graphics card. But everything worked smoothly for about a week, until after one reboot it didnt.

My Xorg log: https://pastebin.com/qMbe5WuA

Software versions:
sddm-git (0.19.0.218.g58a3517-1)
nvidia-dkms (530.41.03-1)
plasma-desktop (5.27.4-1)

Thanks in advance!

Last edited by hacki (2023-05-03 14:24:36)

V1del · 2023-05-03 10:38:59

Remove the /etc/X11/xorg.conf nvidia-xconfig generated stuff is usually not necessary, thait said there's nothing out of the ordinary there, so something else must be off. After such a delayed login post

sudo journalctl -b

hacki · 2023-05-03 10:48:17

V1del wrote:

Remove the /etc/X11/xorg.conf nvidia-xconfig generated stuff is usually not necessary, thait said there's nothing out of the ordinary there, so something else must be off. After such a delayed login post
sudo journalctl -b

I removed the xorg.conf and rebooted. Login still took a while.

Here is the full journalctl log: https://pastebin.com/qV0ghJ1w

seth · 2023-05-03 14:03:29

May 03 12:41:53 archPC sddm[829]: Session "/usr/share/xsessions/plasma.desktop" selected, command: "/usr/bin/startplasma-x11" for VT 2
May 03 12:41:53 archPC sddm-helper[896]: [PAM] Starting...
May 03 12:41:53 archPC sddm-helper[896]: [PAM] Authenticating...
May 03 12:41:53 archPC dbus-daemon[784]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.18' (uid=0 pid=896 comm="/usr/lib/sddm/sddm-helper --socket /tmp/sddm-auth-")
May 03 12:41:53 archPC dbus-daemon[784]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
May 03 12:41:53 archPC sddm-helper[896]: pam_systemd_home(sddm:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
May 03 12:41:53 archPC sddm-helper[896]: [PAM] Preparing to converse...
May 03 12:41:53 archPC sddm-helper[896]: [PAM] Conversation with 1 messages
May 03 12:41:53 archPC sddm-helper[896]: [PAM] returning.
May 03 12:41:53 archPC sddm[829]: Authentication for user  "hacki"  successful
May 03 12:41:53 archPC sddm-greeter[848]: Message received from daemon: LoginSucceeded
May 03 12:41:53 archPC sddm-helper[896]: pam_unix(sddm:session): session opened for user hacki(uid=1000) by (uid=0)
May 03 12:41:53 archPC systemd-logind[787]: New session 2 of user hacki.

The login is instant.

May 03 12:41:41 archPC sddm[829]: Greeter starting...

The greeter started 3s into the boot.

May 03 12:41:54 archPC kernel: ata4.00: limiting speed to PIO4
May 03 12:41:55 archPC kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
May 03 12:41:55 archPC kernel: ata4.00: configured for PIO4
May 03 12:41:59 archPC kernel: ata4.00: limiting speed to PIO3
May 03 12:42:00 archPC kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
May 03 12:42:00 archPC kernel: ata4.00: configured for PIO3

The issue seems to then be w/ the ata4 drive which is

May 03 12:41:38 archPC kernel: ata4.00: ATAPI: HL-DT-ST BDDVDRW GGC-H20N, 1.01, max UDMA/133

some Bluray, is there a disc inside?

hacki · 2023-05-03 14:23:34

seth wrote:

The issue seems to then be w/ the ata4 drive which is
May 03 12:41:38 archPC kernel: ata4.00: ATAPI: HL-DT-ST BDDVDRW GGC-H20N, 1.01, max UDMA/133
some Bluray, is there a disc inside?

There indeed was a disc in there. I took it out and rebooted, didn't help.

Opened the PC and disconnected the bluray drive, sadly also didn't help.

Also apologies I think I mixed two terms. I didn't mean the greeter doesn't show up but the splashscreen which then goes to the desktop! I will edit my original post.

seth · 2023-05-03 14:26:05

Updated journal?

hacki · 2023-05-03 14:36:53

seth wrote:

Updated journal?

https://pastebin.com/maa03rpd

V1del · 2023-05-03 14:43:43

NTPD and timesyncd having a fight over who gets to update the timestamp, fucking over crypto libs in the process? Can you try disabling ntpd and/or systemd-timesyncd? FWIW the splash screen by definition does add a bit of a delay but if I'm reading you corrrectly you have the delay before the splash even shows up? (in any case if you wanted to test that you could disable the splash screen in KDE's settings)

Last edited by V1del (2023-05-03 14:51:40)

hacki · 2023-05-03 14:59:07

V1del wrote:

NTPD and timesyncd having a fight over who gets to update the timestamp, fucking over crypto libs in the process? Can you try disabling ntpd and/or systemd-timesyncd? FWIW the splash screen by definition does add a bit of a delay but if I'm reading you corrrectly you have the delay before the splash even shows up? (in any case if you wanted to test that you could disable the splash screen in KDE's settings)

I thought the same when checking the new logs so I was already testing it after I saw your message. Sadly it didnt fix the issue.

What I did:
systemctl disable systemd-timesyncd
timedatectl set-ntp false
systemctl disable ntpd

(I checked with status and they are disabled after the reboot)

New log: https://pastebin.com/QNbtCDwY

I just want to say again, when I use switch to Plasma Wayland on the login page it starts instantly, so I still think it probably has to do something with Xorg. Are there any other configs I should try to reset maybe?

Last edited by hacki (2023-05-03 14:59:48)

seth · 2023-05-03 15:14:38

Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

seth · 2023-05-03 15:15:53

May 03 16:51:36 archPC systemd[905]: Reloading requested from client PID 914 ('startplasma-x11')...

Does that show up when you log into a wayland session?

hacki · 2023-05-03 15:23:51

seth wrote:

Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

https://pastebin.com/scKaj80k

I have 2 monitors.

1) 144hz 2560 x 1440 Freesync monitor which I run at 120HZ because else wayland misbehaves (another problem for another day).
2) 60hz 1920 x 1080 typical office monitor

On first view the maximum pixel clocks sound weird to me. I will try to disconnect one of the monitors and see if that changes anything.

Last edited by hacki (2023-05-03 15:31:29)

hacki · 2023-05-03 15:31:14

seth wrote:

May 03 16:51:36 archPC systemd[905]: Reloading requested from client PID 914 ('startplasma-x11')...
Does that show up when you log into a wayland session?

It does yes, but instead of x11 its way:

May 03 17:26:38 archPC systemd[903]: Reloading requested from client PID 912 ('startplasma-way')...

Full wayland log: https://pastebin.com/TpJTY5WQ

Sadly can't use wayland as my daily driver yet, too many glitches on nvidia for me.

seth · 2023-05-03 19:24:41

Log into a failsafe session (just an xterm, you can also use startx) and run "startplasma-x11" thre and see whether it hints at what causes about a 130 second stall. There's really nothing in the journal to explain that delay. It would be about 5 consecutive dbus timeouts or one systemd timeout and a dbus timeout and then still some more.

Arch Linux

#1 2023-05-03 09:16:54

SDDM hangs on login with KDE Plasma (X11)

#2 2023-05-03 10:38:59

Re: SDDM hangs on login with KDE Plasma (X11)

#3 2023-05-03 10:48:17

Re: SDDM hangs on login with KDE Plasma (X11)

#4 2023-05-03 14:03:29

Re: SDDM hangs on login with KDE Plasma (X11)

#5 2023-05-03 14:23:34

Re: SDDM hangs on login with KDE Plasma (X11)

#6 2023-05-03 14:26:05

Re: SDDM hangs on login with KDE Plasma (X11)

#7 2023-05-03 14:36:53

Re: SDDM hangs on login with KDE Plasma (X11)

#8 2023-05-03 14:43:43

Re: SDDM hangs on login with KDE Plasma (X11)

#9 2023-05-03 14:59:07

Re: SDDM hangs on login with KDE Plasma (X11)

#10 2023-05-03 15:14:38

Re: SDDM hangs on login with KDE Plasma (X11)

#11 2023-05-03 15:15:53

Re: SDDM hangs on login with KDE Plasma (X11)

#12 2023-05-03 15:23:51

Re: SDDM hangs on login with KDE Plasma (X11)

#13 2023-05-03 15:31:14

Re: SDDM hangs on login with KDE Plasma (X11)

#14 2023-05-03 19:24:41

Re: SDDM hangs on login with KDE Plasma (X11)

Board footer