https://bugs.kde.org/show_bug.cgi?id=475605
--- Comment #22 from kde-bugzi...@hexology.xyz --- I have made some progress by accidentally reproducing the bug under conditions I didn't expect. I suspect now that SDDM specifically is involved, moreso than KWin or Plasmashell. KWin and/or Plasmashell does seem to suffer some progressive graphics corruption after waking from sleep. That is, if the system goes to sleep several times, eventually there will be graphics glitches that are not solved by toggling compositing or restarting Plasmashell, e.g. solid color blocks, panel buttons not responding, windows flickering when being moved, etc. That is not the problem I am reporting here, but it might be related. Specifically, I reproduced the bug just now under the following circumstances: 1. Wake from sleep and log in to the currently-running session through SDDM; observe lots of graphics glitches, rendering the desktop borderline unusable. Can't even open the KDE applications menu to log out. 2. Log in on TTY 3 as a different user, and use `loginctl terminate-user` to end the graphical session. 3. Switch back to TTY 2 where the graphical session was. At step 3, I was expecting the normal SDDM user selection screen. Instead, I was surprised to find the same black screen with cursor that I had been seeing previously upon wake from sleep. Therefore while there does seem to be some issue with KWin and Plasmashell becoming corrupted after several sleep cycles, the actual error was triggered only when the user was logged out and SDDM was supposed to appear on TTY 2. There is an error in the SDDM log, I have added it as an attachment: https://bugs.kde.org/attachment.cgi?id=164796 I'm not sure if the bug is in SDDM, X.org, Plasmashell, KWin, the Nvidia driver or elsewhere. But I hope that being able to reproduce it under different circumstances, and having a new error message, might act as additional evidence. I am not familiar with the Nvidia config file in modprobe.d, and I do not have that file on my system. I will do some research, try that suggestion, and see if it helps. Thanks again for not closing this ticket. -- You are receiving this mail because: You are watching all bug changes.
