Screen saver starts but monitor does not turn off

English Hardware
,
1

Running Tumbleweed KDE Plasma just recently in the past week my monitor is not turned off as it should be, the screen saver starts and after 5 minutes the monitor should turn off but this is not happening. I have a KVM to switch to a Leap 15.6 install and when switched to that the screen does get turned off. The main difference in hardware is the TW system runs an AMD processor with integrated graphics and the Leap system runs Intel processor with integrated graphics. I think this started with a recent big update to Plasma but cannot be absolutely sure.

Is anyone else seeing this? Can anyone suggest what I can do to debug this please?

Stuart

2

https://bugzilla.opensuse.org/show_bug.cgi?id=1261248

1 Like
3

Thanks I did search bugzilla but obviously picked the wrong search agument :disappointed_relieved: now tracking this.

Stuart

4

You can fix it by downloading and installing these:

kf6-kidletime-plugins-6.24.0-kf.52.6.x86_64.rpm
libkscreen6-plugin-6.6.3-kf.90.6.x86_64.rpm

Get them here:

kf6-kidletime-plugins-6.24.0-kf.52.6.x86_64.rpm

And here:

libkscreen6-plugin-6.6.3-kf.90.6.x86_64.rpm

5

Please do not advise such stuff. These are the KDE developement repos. It is not advised to handpick only single packages from it. It will lead to serious issues in the short and long run.

Unfortunately, ppl which give such advice do not really help fix broken system from other users here in the forum…

The fix will land in the official TW repos with the next KDE frameworks update.

6

Yes, on a machine here it is happening. I am glad to see this thread.

:~> kinfo
Operating System: openSUSE Tumbleweed 20260331
KDE Plasma Version: 6.6.3
KDE Frameworks Version: 6.24.0
Qt Version: 6.11.0
Kernel Version: 6.19.10-5.g1efcf12-default (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6600K CPU @ 3.50GHz
Memory: 16 GiB of RAM (15.6 GiB usable)
Graphics Processor: AMD Radeon RX 640
7

There is a script in the bug report which says it fixed the issue for the writer and then it turned out to have been developed using AI which I was unaware of at the time. I tried it and it did not fix the issue for me. If I’d known that I’d never have tried it, my experience of AI writing code is that it rarely works

Stuart

8

The large update I installed yesterday fixed this issue.

Stuart