SUMMARY This issue relates to the two weeks I spent on Fedora 38 KDE. Every time I rebooted my computer, I couldn’t login to KDE, even after waiting 2 hours. Usually, it’s just a black screen for 2-3 minutes, but the last time, I couldn’t login at all. I can’t show you the full logs as I couldn't get to a desktop on this machine, but journalctl -r spams: kwin_core: Applying Kscreen config failed! I also saw: kwin_wayland_drm: Failed to create gamma blob! Invalid argument I have a NVIDIA RTX 2060S card and I was attempting to log in to KDE Wayland. I just updated via Discover before rebooting, which performed an offline update. STEPS TO REPRODUCE 1. Reboot the computer. 2. Ty to login. OBSERVED RESULT I see a black screen for over 2 hours with nothing happening, and the KDE session never starts. EXPECTED RESULT I can login and the session starts. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 38 (Oct 15th) (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.111.0 Qt Version: 5.15 ADDITIONAL INFORMATION Sorry for not being able to provide specific versions. I uninstalled Fedora because of this recurrent issue, but I thought I should report it as it is quite a severe error. As such, I'm not available to troubleshoot it because this doesn't occur on Arch Linux. I ran into several other bugs related to KDE/KDE programs that aren't present on Arch and documented them but unsure whether I should report them because I'm no longer using the system...
Would you be willing to test this again (if it even still happens on Fedora 40)? "Applying Kscreen config failed" means the driver rejected KWin's display configuration but without more details it's hard to know more or do anything about it
Hi, If I get around to testing this particular machine again, it's not going to be for quite a long time. What I can say is that I've been running the last versions of the KDE 5.x series and now the 6.x series since October on Arch Linux with the same hardware, and I have never experienced this issue. Several years ago, I used to get this same issue on Arch Linux when I used KDE, but not when I went back to KDE the past few months. Sorry, I guess it would be better to close this issue, and if I use Fedora and face it again, I'll re-open it.
> I guess it would be better to close this issue, and if I use Fedora and face it again, I'll re-open it. Sounds good