Bug 432259

Summary: Screen does not seem to turn off when locked
Product: [Plasma] kscreenlocker Reporter: Claudius Ellsel <claudius.ellsel>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: bhush94, butirsky, herzenschein
Priority: NOR Keywords: regression
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:

Description Claudius Ellsel 2021-01-28 19:01:05 UTC
SUMMARY
On the current Plasma Beta (5.20.90) I noticed that the screen doesn't seem to turn off when I lock it (shortcut Meta + L). Currently only tested on Wayland.

STEPS TO REPRODUCE
1. Start a session
2. Lock the screen
3. Wait a short amount of time for the displays to turn off

OBSERVED RESULT
The displays stay on

EXPECTED RESULT
The displays are turned off

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20210127
KDE Plasma Version: 5.20.90
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.10.9-1-default
OS Type: 64-bit
Processors: 4 × Intel® Xeon® CPU E3-1225 v3 @ 3.20GHz
Memory: 11.6 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics P4600/P4700
Comment 1 Claudius Ellsel 2021-01-28 19:02:16 UTC
I am rather sure this is a regression (although I haven't used Tumbleweed Wayland that often). Setting the keyword.
Comment 2 Claudius Ellsel 2021-01-28 19:14:27 UTC
Just tested on X11 and I have a similar experience there. Waited about a minute but nothing changed. However, I am not entirely sure anymore how long it used to take the screens to turn off after locking the screen.
Comment 3 Thiago Sueto 2021-01-28 20:30:16 UTC
Hello, my screen seems to have turned off after ten minutes.
I'll text this further later on, but can you check if waiting for more than a few minutes works on your machine?
Comment 4 Claudius Ellsel 2021-01-29 12:15:33 UTC
Alright. I am marking this as waitingforinfo, as everything might be working completely fine. The instance where the screen was still on after I was afk for about 30 Minutes might have been caused by my mouse slightly moving and thus turning the screen on again. I'll have to try again properly, and probably it will also work for me, so false alarm.
Comment 5 Claudius Ellsel 2021-01-30 19:04:20 UTC
On a second test it worked for me, so most likely a false alarm.