Bug 457726 - kscreen_backend_launcher block entering Screen Energy saving
Summary: kscreen_backend_launcher block entering Screen Energy saving
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 5.27.10
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
Depends on:
Reported: 2022-08-10 17:31 UTC by Erik
Modified: 2024-02-25 21:09 UTC (History)
17 users (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Erik 2022-08-10 17:31:09 UTC
When the system enter the Screen Energy Saving mode, both the connected monitors powers off but after a couple of seconds they wake up again.

1. Into "settings > power managment > energy saving" enable "Screen Energy Saving" and set a timer

After the timer expires, screens go black but after a couple of seconds, both of my monitors turn on again without any interaction from me.

While debugging the issue I found out that killing the "kscreen_backend_launcher" process solves the issue and let the monitor sleep successfully.

After the timer expires, screens go black and stays powered off until it detect an user interaction

Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.5

System is up do date.
I have 2 monitors connected, the primary one with DP and the other one with HDMI.
The gpu is a radeon rx6600xt.
Comment 1 Erik 2022-09-04 14:07:15 UTC
Update and more info: 
OBSERVED RESULT: When the screen forcefully wake up from the very short sleep, all the open windows are moved into the primary display.

EXPECTED RESULT: With "kscreen_backend_launcher" process killed, the windows are not rearranged and the windows stays as before the sleep.
Comment 2 nbgyan 2022-10-21 08:51:07 UTC
On my Lenovo X1 Carbon I confirm that this is true. I kill the kscreen_backend background process and laptop sleeps as it should.
Comment 3 Erik 2022-10-22 12:08:35 UTC
UPDATE: Still happening in 5.26.1
Comment 4 Josh 2023-02-26 05:39:43 UTC Comment hidden (spam)
Comment 5 Josh 2023-02-27 01:13:42 UTC Comment hidden (spam)
Comment 6 Nate Graham 2023-02-27 17:06:11 UTC
Can you confirm whether it's still happening in Plasma 5.27.1, Erik?
Comment 7 Michel Sup 2023-03-02 11:40:51 UTC
> Can you confirm whether it's still happening in Plasma 5.27.1, Erik?

Yes, indeed, it's still happening in Plasma 5.27.1.
Comment 8 Nate Graham 2023-03-02 15:33:56 UTC Comment hidden (spam)
Comment 9 ddreamer 2023-06-30 14:52:30 UTC Comment hidden (spam)
Comment 10 Carl Kittelberger 2023-08-06 23:35:17 UTC Comment hidden (spam)
Comment 11 Ventoux84 2023-08-15 14:02:59 UTC Comment hidden (spam)
Comment 12 Fahim Shahriar 2023-08-26 08:29:36 UTC Comment hidden (spam)
Comment 13 daxdowney 2023-10-14 23:16:43 UTC Comment hidden (spam)
Comment 14 张文超 2023-10-22 02:15:33 UTC Comment hidden (spam)
Comment 15 张文超 2023-10-22 02:17:08 UTC Comment hidden (spam)
Comment 16 xpusostomos 2023-12-10 09:48:09 UTC Comment hidden (spam)
Comment 17 Michael Damian 2024-02-25 21:08:22 UTC
Hello, I am experiencing the same issue on Archlinux.  My Monitors are connected via, HDMI and Displayport.  When the Timeout is reached, the monitors begin to turn off, then the 1st one enters Power Saving Mode and is effectively off.  The 2nd monitor however does not reach this state and then a few seconds later, both monitors turn back on.  It happens even if Dim screen is enabled or not.

Operating System: EndeavourOS 
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12
Kernel Version: 6.7.6-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 20 × 12th Gen Intel® Core™ i7-12700K
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 770
Manufacturer: ASUS