Thanks for linking this other thread. It list more links and my conclusion from that is that if you get autologin with Wayland working you can run into a black screen with no cursor although @karlmistelberger reports succes.
Anyhow I tried and follow the instructions and things work for me, nice.
During the boot the screen flashes one time, some thing I did not see before but that is likely because SDDM is still running on X11:
> sudo journalctl -b -u display-manager.service -p6
May 29 21:51:22 systemd[1]: Starting X Display ManagerâŚ
May 29 21:51:22 display-manager[1451]: /etc/vconsole.conf available
May 29 21:51:22 display-manager[1451]: XKBLAYOUT: us
May 29 21:51:22 display-manager[1451]: XKBLAYOUT is already set. Better donât touch X11 keyboard configuration.
May 29 21:51:23 systemd[1]: Started X Display Manager.
May 29 21:51:23 sddm-helper[1666]: pam_unix(sddm-autologin:session): session opened for user marel(uid=1000) by marel(uid=0)
May 29 21:51:23 sddm-helper[1666]: pam_kwallet5(sddm-autologin:session): pam_kwallet5: open_session called without kwallet5_key
May 29 21:51:23 sddm[1460]: Authentication information: âLast login: Mon May 29 21:46:46 CEST 2023 from :0 on tty7â
May 29 21:51:23 sddm-helper[1666]: Starting: â/usr/share/sddm/scripts/wayland-session /usr/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-waylandâ
Not a big problem, so let me wait for that until a ssdm update with better wayland support and try to fix that afterwards.
What is not working yet nicely is shutting down the machine, X11 is the culprit but nothing in the journal likely because the journal is stopped before X11 is terminated. During the shut down I see it hang two times on X11, the first time it seems to time out and continue after 30 seconds and then at the end and that seems to take about 2 minutes.
I was also having the shutdown/reboot issue a couple of weeks ago. The problem only lasted a few days and fixed itself, but it was quite annoying.
In the mean time, I edited /etc/systemd/user.conf
Change the following
#DefaultTimeoutStopSec=90s
to
DefaultTimeoutStopSec=15s
and you wonât have to wait so long when it does hang. Fedora just changed this as a default, because they said it was useless to have to wait so long. If a service has not shutdown in 15 seconds, it is not going to shutdown and should just be killed.
Thanks for the hint to reduce the default timeout. Makes good sense, but for now I leave the 90 seconds default so I notice. I might try to play with an updated sddm to see if I can get sddm also to run on Wayland so X11 is not started at all.
No, it is not that KDE does not support Wayland completely (as you can see the compositor is reported as kwin_wayland), but SDDM is still starting via an X11 session.
I have now encountered too many annoyances in Wayland that I want to go back to X11 but switching now only throws me to tty. Incredibly frustrating, but adding to my +1 of anti-wayland.
Well this isnât the category to do that. No value tacking on to a help thread with such a statement. If you need technical assistance, please start a new thread. If you want simply want to recount your Wayland experience you could add to the existing Open Chat thread (or start your own)âŚ