Wayland KDE screens wake from sleep

Linux@lemmy.ml – 30 points – 1 years ago

Hey everyone

Not sure if this is the right place to ask. I have been experiencing this issue for a while now. I'm convinced it's something to do with my monitor setup. When I use a Wayland session my monitors refuse to sleep! On X11 they sleep as expected when the screen is locked. On Wayland they go to sleep, flash the "entering power save" message and then turn back on. Here is my current and previous setups that both experienced the exact same issue.

Current:

OS: Arch Linux x86_64 
Host: B550M Steel Legend 
Kernel: 6.4.10-arch1-1 
DE: Plasma 5.27.7 
WM: kwin 
CPU: AMD Ryzen 5 5600X (12) @ 3.700GHz 
GPU: AMD ATI Radeon RX 7900 XT/7900 XTX 
Memory: 4705MiB / 32018MiB

Previous 2 configurations:

DE: GNOME 43-44
WM: Mutter
GPU: RTX 3080
(everything else is the same except kernel)

DE: GNOME 41-43
WM: Mutter
GPU: GTX 1080ti
(everything else is the same except kernel)

I've tried running this command I found on stack overflow:

/bin/sleep 1 && /bin/dbus-send --session --dest=org.kde.kglobalaccel /component/org_kde_powerdevil org.kde.kglobalaccel.Component.invokeShortcut string:'Turn Off Screen'

Note: && should be && but lemmy is sanitizing it and won't let me put ampersands in code blocks

but no luck. Any ideas on how to fix this?

Dont sleep 1&. Instead sleep 1;

Ah sorry lemmy code sanitation is changing it. I added a note below it.

Have you tried putting the display to sleep from the CLI and see if there's any meaningful output?

I'm not at my desk but something like: https://askubuntu.com/questions/62858/turn-off-monitor-using-command-line

OK, I just realised you've already done something similar. Scratch what I wrote.

Just out of curiosity, since I've had a similar problem, can you try to disable KScreen 2 in your Background Services settings near the startup applications/autostart menu, then try to let your monitors go to sleep?

My monitors always wake from sleep repeatedly on their own on both X11 and Wayland, but disabling it fixes it for me (but also resets my monitor settings on every boot/log in). I'm still working on finding a permanent solution for mine, but if this also acts as a workaround for your issue it might help narrow down the cause a bit.