Hi, I’ve encountered this issue yesterday, when I tried to connect my monitor.
I am running Fedora 40 (kernel 6.9.7) on wayland session with proprietary nvidia drivers (555.58.02).
What happens is the following, I login to my laptop, hookup my external HDMI display, and my laptop screen goes black, and after I’m sent to the login screen, I login, my screen goes black again and I get sent again to the login screen, repeating this never ending cycle until I disconnect the external monitor and I can login normally again.
I had this issue also with the proprietary 550 drivers, so I upgraded them to the 555 drivers to see if it would solve it but it didn’t.
I couldn’t find any similar issues on forums.
Please let me know if I should upload any extra info.
I am having the exact same issue. KDE recovers from the crash, but crashes every time I disconnect my external HDMI display. I am also on Fedora 40, I have an integrated graphics card and an NVIDIA discrete card, I have installed the drivers from rpmfusion.
thank you
I’ve just found the solution to this problem. If you had secure boot disabled on your BIOS, try enabling it. I re-enabled it and the issue disappeared!
Hello,
I have no way of testing this now, I decided to switch back to Gnome, mainly because of this bug. I am pretty sure I have had Secure Boot enabled all of this time though, I doubt that can be related to my symptoms.
thanks,
There was a crash in PowerDevil, Plasma’s power management and display brightness service, in 6.1.2 and 6.1.3. One way this would get triggered is when connecting or disconnecting the only external monitor, and it would crash soon afterwards.
I’m not sure if this would really have anything to do with your particular issue (it shouldn’t crash the entire session, just restart the service) but it might be worth retrying with the recently released Plasma 6.1.4 release that has a fix for this.
Also Nvidia released a new version of their EGL-Wayland library yesterday, which talks about fixing crashes and race conditions in KDE.
Generally, getting sent to the login screen means that KWin crashed and could not recover. If that happens, you could find the relevant backtraces in coredumpctl and logs in journalctl -S today, which is what KWin developers can use to analyze such issues. If you want to contribute to a fix, please gather this info and open a bug report on bugs.kde.org.