Bug 516704 - Monitor wakes up immediately after turning off
Summary: Monitor wakes up immediately after turning off
Status: RESOLVED DUPLICATE of bug 516454
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (other bugs)
Version First Reported In: 6.6.0
Platform: Arch Linux Linux
: HI major
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: multiscreen, regression
: 516693 (view as bug list)
Depends on:
Blocks:
 
Reported: 2026-02-25 09:06 UTC by Nikola M.
Modified: 2026-02-26 19:01 UTC (History)
3 users (show)

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

Attachments
journalctl for 6.5.5 (13.55 KB, text/plain)
2026-02-25 19:37 UTC, Nikola M. 		Details
journalctl for 6.6.1 (6.71 KB, text/plain)
2026-02-25 19:38 UTC, Nikola M. 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Nikola M. 2026-02-25 09:06:48 UTC 
SUMMARY
After upgrading to Plasma 6.6.0, my monitor is not being able to go to sleep and wakes up immediately after turning off. This issue still persist in 6.6.1. Reverting KWin alone to 6.5.5 resolves the issue and allows the monitor to turn off properly.

STEPS TO REPRODUCE
Unknown (Tried fresh Arch install and the issue persist)

OBSERVED RESULT
Monitor wakes up immediately after turning off.

EXPECTED RESULT
Monitor should properly turn off and be on standby until input is registered.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.6.1
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2
Kernel Version: 6.19.3-2-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 1600 Six-Core Processor
Memory: 16 GiB of RAM (15.6 GiB usable)
Graphics Processor: AMD Radeon RX 580 Series
ddcutil 2.2.5

ADDITIONAL INFORMATION

Monitor is connected to GPU through HDMI and system is using amdgpu.
Comment 1 Nate Graham 2026-02-25 14:58:38 UTC 
*** Bug 516693 has been marked as a duplicate of this bug. ***
Comment 2 Nate Graham 2026-02-25 14:59:09 UTC 
Can you upgrade to 6.6.1 and see if it's fixed now?
Comment 3 Nikola M. 2026-02-25 19:37:41 UTC 
Created attachment 190106 [details]
journalctl for 6.5.5
Comment 4 Nikola M. 2026-02-25 19:38:10 UTC 
Created attachment 190107 [details]
journalctl for 6.6.1
Comment 5 Nikola M. 2026-02-25 19:38:53 UTC 
Like I stated in my original post, I tried upgrading to 6.6.1 and issue persist in both 6.6.0 and 6.6.1. I've uploaded two log files from journalctl that might help you identify the bug.
Comment 6 Zamundaaa 2026-02-26 19:01:02 UTC 

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