SUMMARY If you put a laptop running KDE Plasma to sleep for a few hours (in my case it was about 5), and then wake the device, it may only show the cursor and a black screen, requiring a reboot to continue using the device. STEPS TO REPRODUCE 1. Put the computer to sleep 2. Wake it up 3. Try to use it (you can't, unfortunately) OBSERVED RESULT The laptop wakes to a black screen with nothing responsive save for the cursor EXPECTED RESULT The laptop wakes to the KDE Plasma screen locker, from which you can unlock the system SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240607 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.3-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i5-1240P Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Framework Product Name: Laptop (12th Gen Intel Core) System Version: A4 ADDITIONAL INFORMATION I found a similar bug https://bugs.kde.org/show_bug.cgi?id=485805 from a few months ago, but there are some differences here: 1. The cursor is visible on the Wayland session 2. A reboot does fix the issue
*** Bug 486799 has been marked as a duplicate of this bug. ***
Does the black screen happen in place of the lock screen? Or after you unlock the screen? Or is screen locking not involved here because you disabled screenlocking and the black background is what you see instead of Plasma and your apps?
(In reply to Nate Graham from comment #2) > Does the black screen happen in place of the lock screen? Or after you > unlock the screen? Or is screen locking not involved here because you > disabled screenlocking and the black background is what you see instead of > Plasma and your apps? The black screen happens in place of the Lock Screen, not after unlocking it. I did not disable the Lock Screen.
Please compare to https://bugs.kde.org/show_bug.cgi?id=487495.
(In reply to Reinier from comment #4) > Please compare to https://bugs.kde.org/show_bug.cgi?id=487495. the difference between this bug and the one you linked is: a. Occurs on Wayland instead of X11 b. Switching to a tty and back does not bring back the lock screen
There's also Bug 477738, which is about the same issue happening Wayland, but so far only with AMD and NVIDIA GPUs.
This sounds like bug 476567. Does this still happen if you disable the lock screen? Do you have a fingerprints sensor? If so, can you still trigger this if you remove the configured fingerprints? Also, please attach the output of > journalctl --user-unit plasma-kwin_wayland --boot 0 (or boot -1 if you reboot in between) after reproducing the issue
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!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone!