https://bugs.kde.org/show_bug.cgi?id=348529
--- Comment #40 from Chris <inkbottle...@gmail.com> --- (In reply to Kai Uwe Broulik from comment #4) > That script isn't particularly efficient. > I like the idea of reducing the timeout for turning off the screen when it's > locked (and/or making that a separate option since you might not want it to > turn off at all while not locked), though. I added it to my todo list. > Thanks. What do you think of the script there https://bugs.kde.org/show_bug.cgi?id=348529#c33? It does not, on the face of it, rely on an infinite loop, and it works both with x11 and wayland. dbus-monitor --session "type='signal',interface='org.freedesktop.ScreenSaver'" | while read x; do case "$x" in *"boolean true"*) echo SCREEN_LOCKED; kwriteconfig5 --file powermanagementprofilesrc --group AC --group DPMSControl --key idleTime 60; qdbus org.kde.Solid.PowerManagement /org/kde/Solid/PowerManagement org.kde.Solid.PowerManagement.refreshStatus ;; *"boolean false"*) echo SCREEN_UNLOCKED; kwriteconfig5 --file powermanagementprofilesrc --group AC --group DPMSControl --key idleTime 600; qdbus org.kde.Solid.PowerManagement /org/kde/Solid/PowerManagement org.kde.Solid.PowerManagement.refreshStatus ;; esac done It is quick and dirty cut and paste but I think it works, and I don't see why not? As they say in https://bugs.kde.org/show_bug.cgi?id=348529#c39, it could help having something like that integrated in System-Settings, instead on relying on users hacks. It is annoying having 30W plus, of monitor LED, glowing unnecessarily. (https://www.thehomehacksdiy.com/how-much-power-watts-does-a-monitor-use/) Keep in mind that for most users, monitor power button is not an option because it scrambles up all the settings. -- You are receiving this mail because: You are watching all bug changes.
