SUMMARY After a period of inactivity on the lock screen, the monitor is automatically turned off. If I shake the mouse to wake it up again as soon as it happens (or right after that), the monitor's backlight is re-enabled, but there is no image — just a black rectangle. So far, I have not found a way to continue using my computer when this happens. I am able to enter a TTY and issue "systemctl reboot". STEPS TO REPRODUCE 1. System Settings > Energy Saving > When locked, turn off screen: 200 sec 2. System Settings > Screen Locking > Lock screen automatically: after 1 minute 3. Wait :) 4. As the screen is turned off, shake the mouse. OBSERVED RESULT The screen is re-enabled, but the signal is just darkness. EXPECTED RESULT I can see the lockscreen. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240329 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Kernel Version: 6.8.1-1-default (64-bit) Graphics Platform: Wayland Processors: 32 × Intel® Core™ i9-14900K Graphics Processor: NVIDIA GeForce RTX 4070/PCIe/SSE2 (driver version: 550.67) ADDITIONAL INFORMATION
I've tried doing the following commands once in the TTY: $ loginctl unlock-session 3 $ systemctl --user restart plasma-kwin_wayland.service This returns me to TTY3 where KWin should be, but the screen is still black. After a few seconds, I get kicked out to SDDM. From SDDM, I am unable to start a new Plasma Wayland session, as I always get kicked back out after a few seconds of black screen. SDDM itself is displayed normally, and rebooting from SDDM works.
Created attachment 170953 [details] laptop__plasma-kwin_wayland.log Just happened on my machine. Moved the mouse at about 13:22 and the screen went black. Recovered about 30 seconds later this time, but often it never does. Attaching logs from `journalctl --user-unit plasma-kwin_wayland`
> Jun 25 13:22:51 laptop kscreenlocker_greet[112584]: pam_unix(kde:auth): authentication failure; logname=kiril uid=1000 euid=1000 tty= ruser= rhost= user=kiril Just to clarify here. I have the option "Delay before password required" set to 5 seconds. If I set it to "Require password immediately" the issue is not reproducible for me. Always thought that it just turns the screen off earlier than actually locking the session. Looks like it just tries to authenticate with PAM which fails and the potential failure is not handled internally?
*** This bug has been marked as a duplicate of bug 476567 ***