Bug 506263

Summary: When the screen is locked, after less than a second the screen will wake and remain on, even if the settings are to turn off the screen immediately after locking.
Product: [Plasma] plasmashell Reporter: aoaorecipt
Component: Power management & brightnessAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kdedev
Priority: NOR    
Version First Reported In: 6.4.1   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description aoaorecipt 2025-06-27 12:03:44 UTC
SUMMARY
When the screen is locked, after less than a second the screen will wake and remain on, even if the settings are to turn off the screen immediately after locking.

STEPS TO REPRODUCE
1. In Power Management settings, set the screen to turn off at any time, and when locked: immediately.
2. Lock the system with Meta+L or wait for the system to lock based on the set time.
3. 

OBSERVED RESULT

Screen will lock, screen will go dark, after a few seconds the locking chime will sound, and the screen will instantly wake and remain on, not turning off after any set time. 

EXPECTED RESULT

Screen will lock, screen will go dark, locking chime will sound, screen will remain off. 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 6.4.1
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1

ADDITIONAL INFORMATION
Kernel Version: 6.15.3-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor: AMD Radeon RX 6600
Product Name: B550M-ITX/ac
Comment 1 TraceyC 2025-07-01 18:19:08 UTC
I'm not able to reproduce this in git-master.

Can you let us know if you have multiple displays or just one? This seems related to bug 493879, which is also on Arch, but the user has multiple displays. Thanks.
Comment 2 TraceyC 2025-07-01 21:06:02 UTC
This looks nearly identical to bug 493879 so I'm going to merge this into that one. Please follow that report for updates.

*** This bug has been marked as a duplicate of bug 493879 ***