| Summary: | [NVIDIA] locking 2nd time in a Wayland session results in black screen with cursor | ||
|---|---|---|---|
| Product: | [Plasma] kscreenlocker | Reporter: | kodatarule |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | REPORTED --- | ||
| Severity: | major | CC: | alesar032, fanzhuyifan, gcala, jeisom, miranda, nate, postix, stefan.hoffmeister |
| Priority: | NOR | Keywords: | qt6 |
| Version: | 5.90.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
kodatarule
2023-12-05 04:28:44 UTC
I remember seeing a bug just like this -- also with lock screen, not sleep/suspend to RAM. But I can't seem to find it. This seems to be affecting the Plasma 6 alpha, now beta only, I didn't experience it prior to the update. I experienced this as well. I am currently running the latest nvidia vulkan driver. I haven't done a lot of testing, but have not reproduced it since disabling the kscreenlocker. I tried loginctl to unlock the session and killing kscreenlocker and it would just restart. I am curious if others can reproduce this if they disable it. Not the best workaround if it is the case though. Using a 4080 and 6.0 Beta 1 I see the same behaviour on vmwgfx - i.e. a virtual machine running on top of VMware Workstation. The only way I have found to recover from this is to resize the virtual machine's window. This works well for a virtual machine, but still is annoying. FWIW, I am not sure about the "second time" - it's hit and miss for me, much more often hit the problem than missing it. This is on Fedora Rawhide 40 with (I suspect) my self-built plasma-desktop in place from git master. I just had this happen again. It may correlate with timeouts, where "something" turns off? My VM is running in the background - KDE will simply (eventually) turn off the virtual screen. Curious: the mouse cursor was a pointing finger, not an arrow. Literally the only way for me to recover was the magic "change screen size in virtual machine" work-around. No amount of clicking, hacking away at the keyboard, sending keystrokes into virtual machine did anything. At the same time, I was enjoying exactly no warnings in the SSH session. I confirm the bug. I usually use hibernate and after resume I got a black screen with a mouse pointer that follows mouse movements. Operating System: Arch Linux KDE Plasma Version: 5.91.0 KDE Frameworks Version: 5.247.0 Qt Version: 6.7.0 Kernel Version: 6.6.8-arch1-1 (64-bit) Graphics Platform: X11 Processors: 4 × AMD A8-6500 APU with Radeon(tm) HD Graphics Memory: 7.7 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 Some questions *for the original reporter of the bug*: - Does it happen when the system locks the screen? - Does it happen when the system puts the display to sleep? - Does it happen when the system suspends? - Are there more than one screen? - Are there more than one GPU? - Is it a PRIME system with muxing? If so, which GPU was driving the display? - Is the cursor visible? - Are there any GUI elements visible? - Is the broken lock screen function (e.g. blindly typing your password and hitting Enter unlocks)? - Is there a method that brings you back to a working desktop (e.g. killing kscreenlocker_greet). - Is the desktop session using X11 or Wayland? Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! *** Bug 480669 has been marked as a duplicate of this bug. *** 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. (In reply to Jonathan Isom from comment #10) > > - 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. I am testing with the NVidia vulkan beta now, 535.43.25 and I am able to kill it and it reloads and then I can log in. I thought maybe a driver update changed something, but that may not be the case. This is on Plasma 6RC2 on arch. On beta 1 it would just reload as a new black screen. *** This bug has been marked as a duplicate of bug 475605 *** Not a duplicate of that issue, my mistake. That's X11-only and this is on Wayland. (In reply to Jonathan Isom from comment #11) > (In reply to Jonathan Isom from comment #10) > > > - 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. > > I am testing with the NVidia vulkan beta now, 535.43.25 and I am able to > kill it and it reloads and then I can log in. I thought maybe a driver > update changed something, but that may not be the case. This is on Plasma > 6RC2 on arch. On beta 1 it would just reload as a new black screen. Additional note: I can kill it by "killall -9 kscreenlocker_greet" and login, but only if I am on the TTY for plasma, ie I ssh in. If I switch to another TTY to kill it I end up with another blackscreen. |