[SOLVED] SDDM freezes when trying to start a Wayland session

zombieagain · 2024-04-19 11:13:27

Hello! I've been using Arch for maybe 10 years, but I'm not that good...
A couple of months ago, after an update, Wayland sessions stopped working (if I autologin I get a black screen with the cursor, a normal login would just freeze at the SDDM screen). X11 sessions work fine.
I waited a few weeks while keeping Arch updated and tried many things searching the forum and Reddit, but I could not solve the issue on my own. Any help would be immensely appreciated.

systemd journal
https://0x0.st/XojO.txt
(login attempt starts at Apr 19 12:54:24)

Xorg.0.log
https://0x0.st/Xojt.txt

I'm accessing the machine through RealVNC. Nothing has changed in the past few months.

Thanks!

Last edited by zombieagain (2024-04-23 08:55:23)

seth · 2024-04-19 12:37:31

The only thing tha looks like trouble is

Apr 19 12:54:26 joy-server udisksd[894]: udisks daemon version 2.10.1 starting
Apr 19 12:54:26 joy-server udisksd[894]: Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdg': Unexpected sense data returned:
                                         0000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................
                                         0010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................

which is

Apr 19 12:51:06 joy-server smartd[446]: Device: /dev/sdg [SAT], HGST HDN726060ALE610, S/N:NCGZSBAS, WWN:5-000cca-24dcdfad8, FW:APGNT517, 6.00 TB
Apr 19 12:51:06 joy-server smartd[446]: Device: /dev/sdg [SAT], found in smartd database 7.3/5528: HGST Deskstar NAS

Try to remove that and see whether it's the cause.

Edit: the immediate session failure is because of

Apr 19 12:54:26 joy-server plasmashell[881]: kde.plasmashell: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
Apr 19 12:54:26 joy-server plasmashell[881]: kde.plasmashell: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable.
Apr 19 12:54:26 joy-server kactivitymanagerd[918]: kf.windowsystem: virtual void KX11Extras::connectNotify(const QMetaMethod&) may only be used on X11
Apr 19 12:54:26 joy-server kactivitymanagerd[918]: kf.windowsystem: virtual void KX11Extras::connectNotify(const QMetaMethod&) may only be used on X11
Apr 19 12:54:26 joy-server systemd[650]: Started KActivityManager Activity manager Service.
Apr 19 12:54:26 joy-server plasmashell[881]: kde.plasmashell: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
Apr 19 12:54:26 joy-server plasmashell[881]: kde.plasmashell: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable.

Edit #2: fits https://bbs.archlinux.org/viewtopic.php … 2#p2164032
I'm not sure where the other users there ran into the same issue.

Last edited by seth (2024-04-19 12:43:50)

zombieagain · 2024-04-19 13:26:03

seth wrote:

The only thing tha looks like trouble is

Apr 19 12:54:26 joy-server udisksd[894]: udisks daemon version 2.10.1 starting
Apr 19 12:54:26 joy-server udisksd[894]: Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdg': Unexpected sense data returned:
                                         0000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................
                                         0010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................

which is

Apr 19 12:51:06 joy-server smartd[446]: Device: /dev/sdg [SAT], HGST HDN726060ALE610, S/N:NCGZSBAS, WWN:5-000cca-24dcdfad8, FW:APGNT517, 6.00 TB
Apr 19 12:51:06 joy-server smartd[446]: Device: /dev/sdg [SAT], found in smartd database 7.3/5528: HGST Deskstar NAS

Try to remove that and see whether it's the cause.

I removed the external hard drives enclosure, but the issue remains. Updated systemd journal:
https://0x0.st/XoeV.txt

seth · 2024-04-19 13:53:58

Apr 19 15:16:55 joy-server plasmashell[824]: QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0

https://wiki.archlinux.org/title/KDE#Un … lution_set ?
Does the problem exists w/ a fresh user account?

zombieagain · 2024-04-19 14:01:54

seth wrote:

Apr 19 15:16:55 joy-server plasmashell[824]: QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
https://wiki.archlinux.org/title/KDE#Un … lution_set ?
Does the problem exists w/ a fresh user account?

thanks for helping. I created a new user to test this and the problem is identical (X11 session works, Wayland does not). I also tried with LightDM and the result is the same.

seth · 2024-04-19 15:48:06

More interestingly than lightdm would be to test eg. a sway session (the problem isn't SDDM but KDE)
When the system "freezes", can you still switch the VT? (ctrl+alt+F1,F2,F3,…)

zombieagain · 2024-04-19 16:33:27

seth wrote:

More interestingly than lightdm would be to test eg. a sway session (the problem isn't SDDM but KDE)
When the system "freezes", can you still switch the VT? (ctrl+alt+F1,F2,F3,…)

Switching the VT never worked for me, I think it is a limitation of RealVNC. I guess I could connect a monitor to the machine since it sits in my pantry and then I should be able to use the ctrl+alt+F...

The system doesn't really freeze, all the applications are working and I can login through SSH just fine.

I'll read up on sway.

Thanks!

zombieagain · 2024-04-19 16:59:14

I installed sway (I'm not sure I did everything I needed to. I just installed the package and then copied /etc/sway/config to ~/.config/sway/config .
The login is unsuccessful and the desktop stays frozen at SDDM, but the systems journal is different.

https://0x0.st/Xo_D.txt

zombieagain · 2024-04-19 20:30:24

Another update. I installed nomachine and disabled realvnc, but the issue remains the same.

seth · 2024-04-19 21:36:18

NX is rather X11 specific and if you cannot switch the VT on VNC, wayland rather isn't going to work either
As a matter of fact: https://help.realvnc.com/hc/en-us/artic … NC-Connect

https://wiki.archlinux.org/title/Wayland#Remote_display
=> krfb?

zombieagain · 2024-04-20 04:23:24

seth wrote:

=> krfb?

Thank you Seth. I had no idea krfb existed. Unfortunately, I can't find a way to enable desktop sharing unless I'm already logged in (and so I need to be in a X11 session). When I log out to try the Wayland session the remote connection stops.
I will connect a monitor to the machine some time today, so to remove the remote desktop connection variable.
BTW, I read the article about Wayland not working with RealVNC, but the interesting bit is that it always worked for me until one month ago when plasma went through the big update.
Anyway, thanks for your help.

seth · 2024-04-20 08:18:44

Do you have older system journals?
Plasma used to default to X11 and only moved to wayland by default w/ v6 - it might also just have implicitly resorted to X11 because of wayland failing?

zombieagain · 2024-04-20 15:11:13

seth wrote:

Do you have older system journals?

Unfortunately no.

seth wrote:

Plasma used to default to X11 and only moved to wayland by default w/ v6 - it might also just have implicitly resorted to X11 because of wayland failing?

It might very well be and maybe I'm just confusing myself. I thought I remember having switched to Wayland but maybe I never did.

The real problem, I should say, is that I've been having very annoying issues since that infamous update and somehow I connected them to having to switch to X11, but maybe they're just plasma 6 issues.

Basically, the apps pinned to the taskbar don't stick. Every time I log in the task bar is empty.
Also, after working for a bit, I have this irritating issue that if I click on a window, another window that was in the background will come to the foreground and the only solution is to minimize all the other windows one by one before I can interact with the window I want.

I always have many projects open in PyCharm and, after a few minutes, I click on a window only to have another project suddenly on the screen and it can get really confusing...

seth · 2024-04-20 16:06:25

https://bugs.kde.org/show_bug.cgi?id=482090

zombieagain · 2024-04-22 17:31:40

Hello! Sorry for having gone quiet for a couple of days. I connected a physical display to the machine and disabled VNC, temporarily. The symptoms while logging into Wayland have changed, but there are still a lot of problems.
After I enter the password, the screen goes black with a cursor. After 3 minutes the wallpaper shows up and after an additional 30 seconds, I'm finally into a working desktop.
Systemd Journal:

https://0x0.st/XonI.txt

The login starts at 19:15:46
I'm looking right now at all the errors and timeouts. Thanks!

seth · 2024-04-22 20:52:46

Apr 22 19:18:47 joy-server plasmashell[954]: libEGL warning: failed to open /dev/dri/renderD128: Permission denied
Apr 22 19:18:47 joy-server plasmashell[954]: libEGL warning: failed to open /dev/dri/renderD128: Permission denied
Apr 22 19:18:47 joy-server plasmashell[954]: libEGL warning: wayland-egl: could not open /dev/dri/renderD128 (Permission denied)
Apr 22 19:18:47 joy-server plasmashell[954]: MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER)
Apr 22 19:18:47 joy-server plasmashell[954]: libEGL warning: egl: failed to create dri2 screen

printenv

Edit: https://wiki.archlinux.org/title/OpenGL

Last edited by seth (2024-04-22 20:53:07)

zombieagain · 2024-04-23 08:54:52

Thanks, Seth for all the help. The delay is gone. I'm not 100% sure why, but I suspect it was related to my misguided attempt to install Nomachine. Now Wayland's session starts immediately.

My problem was due to VNC and not having connected a display in years to the physical machine. Now I can see that, if I try to start a Wayland session through VNC, the VNC client shows a frozen SDDM, while the display connected to the machine is logged in. I'm not sure why the problem started and after an updated I got the infamous black screen with a cursor. Maybe as you said, it was the change of default that happened last month. I'm now back to X11.

It seems like wayvnc and sway are an option to VNC into a Wayland session and I might give this a try.

Marking as solved.

Arch Linux

#1 2024-04-19 11:13:27

[SOLVED] SDDM freezes when trying to start a Wayland session

#2 2024-04-19 12:37:31

Re: [SOLVED] SDDM freezes when trying to start a Wayland session

#3 2024-04-19 13:26:03

Re: [SOLVED] SDDM freezes when trying to start a Wayland session

#4 2024-04-19 13:53:58

Re: [SOLVED] SDDM freezes when trying to start a Wayland session

#5 2024-04-19 14:01:54

Re: [SOLVED] SDDM freezes when trying to start a Wayland session

#6 2024-04-19 15:48:06

Re: [SOLVED] SDDM freezes when trying to start a Wayland session

#7 2024-04-19 16:33:27

Re: [SOLVED] SDDM freezes when trying to start a Wayland session

#8 2024-04-19 16:59:14

Re: [SOLVED] SDDM freezes when trying to start a Wayland session

#9 2024-04-19 20:30:24

Re: [SOLVED] SDDM freezes when trying to start a Wayland session

#10 2024-04-19 21:36:18

Re: [SOLVED] SDDM freezes when trying to start a Wayland session

#11 2024-04-20 04:23:24

Re: [SOLVED] SDDM freezes when trying to start a Wayland session

#12 2024-04-20 08:18:44

Re: [SOLVED] SDDM freezes when trying to start a Wayland session

#13 2024-04-20 15:11:13

Re: [SOLVED] SDDM freezes when trying to start a Wayland session

#14 2024-04-20 16:06:25

Re: [SOLVED] SDDM freezes when trying to start a Wayland session

#15 2024-04-22 17:31:40

Re: [SOLVED] SDDM freezes when trying to start a Wayland session

#16 2024-04-22 20:52:46

Re: [SOLVED] SDDM freezes when trying to start a Wayland session

#17 2024-04-23 08:54:52

Re: [SOLVED] SDDM freezes when trying to start a Wayland session

Board footer