Bug 405344 - display does not stay in power save on lock screen
Summary: display does not stay in power save on lock screen
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Power management & brightness (other bugs)
Version First Reported In: 6.2.4
Platform: Debian unstable Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-11 10:03 UTC by arne anka
Modified: 2025-07-31 03:46 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description arne anka 2019-03-11 10:03:16 UTC
SUMMARY
- desktop machine
- NVIDIA GF119 [NVS 315]
- two displays via DP

when locking screens, power save kicks in after defined interval, but screen immediately power on again.

while logged in issuing

xset dpms force suspend

blanks the screens AND the screens stay blank

having the command run after lock, screens still wake up again.

seems to be an issue with the lock screen since power save works when not locked.

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2019-03-17 14:07:33 UTC

*** This bug has been marked as a duplicate of bug 348529 ***
Comment 2 arne anka 2019-03-17 18:44:46 UTC
this is no duplicate of 348529!
this bug is about the proposed workaround not working as well!

while I am bitten by both bugs, those are two separate issues.
this one is about the screens not _staying_ blank when in lock screen, NOT the screen not _blanking_.
Comment 3 Lukas Ba. 2019-03-17 22:59:40 UTC
Steps to reproduce?
Also give the precise command you entered in the workaround.
Could also be something simple, like the mouse registering movement.
Comment 4 arne anka 2019-03-18 09:26:23 UTC
(In reply to Lukas Ba. from comment #3)
> Steps to reproduce?
> Also give the precise command you entered in the workaround.
> Could also be something simple, like the mouse registering movement.

see initial report.
and it doesn't matter whether I use xset or plasma's Energy saving -> switch off after X min -- screen always wakes up again.
Comment 5 minson 2020-01-15 14:17:19 UTC
I too have this issue after switching to mb ASUS PRME B450M-A

Problem exists on Kubuntu as well as Fedora30,31/KDE spin .

Problem does not exists on Ubuntu or Fedore 30,31 Desktop 

Note: If I leave the computer at login prompt the screen does go into powersave mode ad stay there
Comment 6 Alexander Potashev 2020-01-19 10:04:05 UTC
Same problem here with Plasma 5.14.5 (on an in-house developed variant of Debian). The screen is still on after more than 24 hours of inactivity.
Comment 7 minson 2020-08-21 12:24:28 UTC
Problem exists on 

KDE NEON 5.19

Plasma 5.19.4
KDE Frameworks 5.73.0
Qt 5.14.2
Comment 8 minson 2020-09-16 13:29:46 UTC
On Neon 5.19.5 disabling kscreen2 'fixes' this issue (for me anyway) .
Comment 9 TraceyC 2025-07-01 22:24:05 UTC
Thanks for the bug report. I'm sorry we weren't able to get to this yet. There have been many fixes and improvements since this was reported, and this issue may have been fixed.

Can you please re-test on your system with Plasma 6.4.1 or later and let us know if you can still reproduce the problem? If you can, please set this report back to REPORTED. Thanks!
Comment 10 Bug Janitor Service 2025-07-16 03:47:22 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 11 Bug Janitor Service 2025-07-31 03:46:25 UTC
๐Ÿ›๐Ÿงน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.