https://bugs.kde.org/show_bug.cgi?id=478090
--- Comment #10 from Jonathan Isom <jei...@gmail.com> --- While I am not the original reporter(Should I duplicate it?) here are my experiences. (In reply to Nate Graham from comment #7) > Some questions *for the original reporter of the bug*: > - Does it happen when the system locks the screen? I don't think so, but after is has been put to sleep. > - Does it happen when the system puts the display to sleep? see above > - Does it happen when the system suspends? Yes, but only when the screenlocker is enabled. If the screenlocker is disabled the system will wake normally. > - Are there more than one screen? Not in my case. > - Are there more than one GPU? No, just one in my case. > - Is it a PRIME system with muxing? If so, which GPU was driving the display? No, just a single discrete gpu. > - Is the cursor visible? Yes and it is movable. > - Are there any GUI elements visible? No. Just a black screen and the cursor. > - Is the broken lock screen function (e.g. blindly typing your password and > hitting Enter unlocks)? Not in my experience. > - Is there a method that brings you back to a working desktop (e.g. killing > kscreenlocker_greet). I have only had it work once where killing kscreenlocker_greet that worked. I am currently using the 550.xx beta driver and that be why I was able to. Can't say without further testing. Prior times it would just restart it with a black screen. > - Is the desktop session using X11 or Wayland? This is on wayland. X11 works as expected. -- You are receiving this mail because: You are watching all bug changes.
