4 ms·

> The minimum screen brightness is now always 1, and the minimum keyboard brightness is now always 0, ensuring that the screen backlight never turns off complet

> The minimum screen brightness is now always 1, and the minimum keyboard brightness is now always 0, ensuring that the screen backlight never turns off completely at minimum brightness, while the keyboard backlight always does (me: Nate Graham and Natalie Clarius, link 1 and link 2) Finally! I thought there was something wrong on my end. I also love how open KDE is and how almost any functionality in it can be automated.

geokon 3y ago
I liked that your could turn off the brightness entirely :( (Though in Kubuntu it doesn't) Not clear how you can even do that now. You can "sleep" the display but it'll turn back on when you hit any key
- FirmwareBurner 3y ago
  You can always set brightness to zero via the command line using any monitor ddc control tool you can find.
  - geokon 3y ago
    ... but then I don't have a shortcut to turn it back on.. lol the convenience is that most laptops have dedicated brightness keys
    - tux3 3y ago
      I think it'd still turn back on if you press brightness up, as before :) And you can make a custom shortcut that runs a brightness to zero script as well, that should work!
- circuit10 3y ago
  Yes, being able to turn it off might be confusing for some people but it’s useful if you’re aware of it so there should be a setting
- mmh0000 3y ago
  Make a little script, bind it to a hotkey. For me, I use Windows+S $ cat ~/bin/monitor-off.sh #!/bin/bash sleep .5 xset dpms force off Same little trick for when I lock the screen, (Settings -> Notifications -> Screen Saver -> Configure Events): cat ~/bin/LOCKSCREEN-ACTIONS.sh #!/bin/bash ## Anything that is "slow" should be run in the background otherwise lock/unlock is slowed down #Mute audio on screen lock, only if not already muted: ( if [[ "$(amixer get Master | awk '/Front Left:/ {print $NF}')" = "[on]" ]]; then amixer -q set Master mute touch "${HOME}/.audiomutedbylockscreen" fi ) & #Pause foobar2000 only if playing, and make a note. ( "${HOME}/bin/foobar2000-pauseonly.sh" && touch "${HOME}/.foopausedbylockscreen" ) & #Disable all mouses (to prevent movement waking monitor.) "${HOME}/bin/set-mice-status" disable #Force monitor to sleep. "${HOME}/bin/monitor-off.sh" And finally, I have the inverse of that, which is called on screen unlock, called automatically on screen unlock (Settings -> Notifications -> Screen Saver -> Configure Events): cat ~/bin/UNLOCKSCREEN-ACTIONS.sh #!/bin/bash #Unmute audio only if muted by lockscreen: ( if [ -f "${HOME}/.audiomutedbylockscreen" ]; then amixer -q set Master unmute rm -f "${HOME}/.audiomutedbylockscreen" fi ) & #Enable all mouses. "${HOME}/bin/set-mice-status" enable & #Unpause foobar2000 only if paused by lockscreen. Remove note. ( if [ -f "${HOME}/.foopausedbylockscreen" ]; then "${HOME}/bin/foobar2000-playonly.sh" rm -f "${HOME}/.foopausedbylockscreen" fi ) &
  - wkat4242 3y ago
    Oh cool I didn't know you could configure events. I made a script that just checks if kscreensaver is running but it always felt a bit duct tapeish. Thanks!
- pritambaral 3y ago
  > I liked that your could turn off the brightness entirely :( Looking at the change, it seems the dbus method[1] to set brightness explicitly to a value should continue to work. A script could be assigned to the lower brightness key that uses this DBus API. Alternatively, the same DBus API also provides a signal for whenever brightness changes, and an autostart script could be written to monitor for the value 1 and immediately set it to 0. 1: https://invent.kde.org/plasma/powerdevil/-/blob/master/daemon/actions/bundled/org.kde.Solid.PowerManagement.Actions.BrightnessControl.xml https://invent.kde.org/plasma/powerdevil/-/blob/master/daemo...

geokon 3y ago

I liked that your could turn off the brightness entirely :( (Though in Kubuntu it doesn't) Not clear how you can even do that now. You can "sleep" the display but it'll turn back on when you hit any key

FirmwareBurner 3y ago
You can always set brightness to zero via the command line using any monitor ddc control tool you can find.
- geokon 3y ago
  ... but then I don't have a shortcut to turn it back on.. lol the convenience is that most laptops have dedicated brightness keys
  - tux3 3y ago
    I think it'd still turn back on if you press brightness up, as before :) And you can make a custom shortcut that runs a brightness to zero script as well, that should work!
circuit10 3y ago
Yes, being able to turn it off might be confusing for some people but it’s useful if you’re aware of it so there should be a setting
mmh0000 3y ago
Make a little script, bind it to a hotkey. For me, I use Windows+S $ cat ~/bin/monitor-off.sh #!/bin/bash sleep .5 xset dpms force off Same little trick for when I lock the screen, (Settings -> Notifications -> Screen Saver -> Configure Events): cat ~/bin/LOCKSCREEN-ACTIONS.sh #!/bin/bash ## Anything that is "slow" should be run in the background otherwise lock/unlock is slowed down #Mute audio on screen lock, only if not already muted: ( if [[ "$(amixer get Master | awk '/Front Left:/ {print $NF}')" = "[on]" ]]; then amixer -q set Master mute touch "${HOME}/.audiomutedbylockscreen" fi ) & #Pause foobar2000 only if playing, and make a note. ( "${HOME}/bin/foobar2000-pauseonly.sh" && touch "${HOME}/.foopausedbylockscreen" ) & #Disable all mouses (to prevent movement waking monitor.) "${HOME}/bin/set-mice-status" disable #Force monitor to sleep. "${HOME}/bin/monitor-off.sh" And finally, I have the inverse of that, which is called on screen unlock, called automatically on screen unlock (Settings -> Notifications -> Screen Saver -> Configure Events): cat ~/bin/UNLOCKSCREEN-ACTIONS.sh #!/bin/bash #Unmute audio only if muted by lockscreen: ( if [ -f "${HOME}/.audiomutedbylockscreen" ]; then amixer -q set Master unmute rm -f "${HOME}/.audiomutedbylockscreen" fi ) & #Enable all mouses. "${HOME}/bin/set-mice-status" enable & #Unpause foobar2000 only if paused by lockscreen. Remove note. ( if [ -f "${HOME}/.foopausedbylockscreen" ]; then "${HOME}/bin/foobar2000-playonly.sh" rm -f "${HOME}/.foopausedbylockscreen" fi ) &
- wkat4242 3y ago
  Oh cool I didn't know you could configure events. I made a script that just checks if kscreensaver is running but it always felt a bit duct tapeish. Thanks!
pritambaral 3y ago
> I liked that your could turn off the brightness entirely :( Looking at the change, it seems the dbus method[1] to set brightness explicitly to a value should continue to work. A script could be assigned to the lower brightness key that uses this DBus API. Alternatively, the same DBus API also provides a signal for whenever brightness changes, and an autostart script could be written to monitor for the value 1 and immediately set it to 0. 1: https://invent.kde.org/plasma/powerdevil/-/blob/master/daemon/actions/bundled/org.kde.Solid.PowerManagement.Actions.BrightnessControl.xml https://invent.kde.org/plasma/powerdevil/-/blob/master/daemo...