Bugzilla – Bug 1202078
Plasma wayland cannot be set as default with autologin (kernel bug)
Last modified: 2024-06-07 11:42:07 UTC
Leap 15.4 with Plasma KDE 5.24.4 and all updates installed with autologin enabled. It works fine on X11. I tried to set Plasma Wayland as default via "System Settings-->Startup and Shutdown-->Login Screen (SDDM)-->Behavior-->choose Plasma Wayland", but then I will end in console instead in Plasma. Plasma Wayland itself works, if I keep old settings with autologin into X11 and then I just unlog to SDDM, change session and log with Wayland, it is ok. Just autologin will not boot. I can reproduce it both on my freshly installed Laptop with i5-11400H cpu with integrated graphics and in VirtualBox. I tested behavior in Fedora 36 without updates (similar components, Plasma 5.24.3, etc) and there autologin settings works fine.
Retested and still valid even for updated Leap 15.5 Is it possible, that is not KDE issue, but some other component? Eg. systemd, or?
I tried to debug it, what is different between Leap and Tumbleweed and I found the culprit: Bug is in the kernel. With Leap 15.4 and 15.5 kernels it does not work, with kernel from https://download.opensuse.org/repositories/Kernel:stable:Backport/standard/Kernel:stable:Backport.repo it works. I guess it has something with this issue https://github.com/sddm/sddm/issues/1443 In clean Leap 15.5 I cannot find anything usefull in logs, but in my "frankenstein" Leap with half of components from Tumbleweed from previous testing I see this error in log: Mar 31 21:50:56 localhost.localdomain sddm-helper[1087]: Couldn't finalize jump to VT 1: Přerušené volání systému So I guess it is some bug in virtual terminal code in kernel?
It looks much more dificult then I thought... Yesterdays update does not work anymore today on VirtualBox. On real PC with AMD graphics it works with original Leap's kernel. On real PC with Intel graphics it does not work. And I read somewhere on reddit, it does not work sometimes even on Tumbleweed... So I will just use it without autologin. Should I close the bug as too much broken to fix?
Almost two years later, experiencing something similiar still today as of 2024.06.06 boo 1226053
bug 1221507 has the most info *** This bug has been marked as a duplicate of bug 1221507 ***