Screen Energy Saving doesn't work - kwin plasmashell error

Help
1

For a long time now I’ve had Screen Energy Saving turned on to switch off my screens automatically. And it has never worked: the instant the screens turn off they pop themselves back on again. Finally went and looked in the logs, I think I’ve found the relevant lines, but there are SEVERAL lines of logs before and after this posted by plasmashell and kscreen_backend_launcher that can provide more context if needed.

2024-09-08T22:55:42.087062-04:00 solinux kwin_x11[1896]: kwin_core: Parse error in tiles configuration for monitor "5b7a5ba4-43cc-5910-8e98-f358f9d54b43" : "illegal value" Creating default setup
2024-09-08T22:55:42.087367-04:00 solinux plasmashell[1961]: Checking screens: available: (QScreen(0x624c99376a00, name="DisplayPort-0")) redundant: QHash() fake: QSet() all: (QScreen(0x624c99376a00, name="DisplayPort-0"))
2024-09-08T22:55:42.087448-04:00 solinux plasmashell[1961]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:20: TypeError: Cannot read property 'pluginName' of null
2024-09-08T22:55:42.087487-04:00 solinux plasmashell[1961]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:75: TypeError: Cannot read property 'configuration' of null
2024-09-08T22:55:42.087539-04:00 solinux plasmashell[1961]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:78: TypeError: Cannot read property 'pluginName' of null
2024-09-08T22:55:42.087571-04:00 solinux plasmashell[1961]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:80: TypeError: Cannot read property 'configuration' of null
2024-09-08T22:55:42.087602-04:00 solinux plasmashell[1961]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:81: TypeError: Cannot read property 'configuration' of null
2024-09-08T22:55:42.087640-04:00 solinux plasmashell[1961]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:82: TypeError: Cannot read property 'configuration' of null
2024-09-08T22:55:42.087744-04:00 solinux plasmashell[1961]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:83: TypeError: Cannot read property 'configuration' of null
2024-09-08T22:55:42.087782-04:00 solinux plasmashell[1961]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:84: TypeError: Cannot read property 'configuration' of null
2024-09-08T22:55:42.087813-04:00 solinux plasmashell[1961]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:16: TypeError: Cannot read property 'configuration' of null
2024-09-08T22:55:42.087844-04:00 solinux plasmashell[1961]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:17: TypeError: Cannot read property 'configuration' of null
2024-09-08T22:55:42.087875-04:00 solinux plasmashell[1961]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:18: TypeError: Cannot read property 'configuration' of null
2024-09-08T22:55:42.559478-04:00 solinux kscreen_backend_launcher[2186]: kscreen.xrandr: Emitting configChanged()

So is there an issue with a config file somewhere? How can I find what this file is and how do I fix it? Or if it’s something else, what?
In the meantime I’ve disabled the feature and my computer will finally be able to automatically suspend. Cause this little glitch was resetting all the timers for that. I only just figured out that the automatic suspend will work if I disable the screen energy saving. Oops.
Thanks in advance for your help.

2

I don’t have an answer but I have a different problem with Screen Energy Saving on Debian 12.5 with Plasma version 5.27.5, KDE Frameworks version 5.103.0 and QT version 5.15.8. On several machines it works just fine. On one machine it behaves like “Suspend session,” even though that’s not checked on the “Energy Saving” settings page. I’d like to look in “the logs” but I don’t know where they are. The only one containing “plasma” is /var/log/dpkg.log, and that’s about installing plasma-discover-backend-fwupd.

3

You are far more likely to get help with this by making your own post instead of commenting on a months old thread that has no responses.