https://bugs.kde.org/show_bug.cgi?id=469819
Jakob Petsovits <jpe...@petsovits.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jpe...@petsovits.com
--- Comment #3 from Jakob Petsovits <jpe...@petsovits.com> ---
Just to add some clarity: When you say lid open/closed, you have Sleep
(suspend-to-RAM) configured as lid action in the Energy Saving settings page,
yes?
PowerDevil's HandleButtonEvents action only restores keyboard brightness on
lid-open if the stored brightness was greater than 0 to begin with. And there
are two other places in PowerDevil that, confusingly, also mess with keyboard
brightness: the DPMS action, which has the same guard and shouldn't be executed
anyway in your (suspend) case; and the DimDisplay action, which doesn't trigger
on lid state changes but only on user activity timeouts.
So I do wonder where your "Keyboard backlight is set to 0" at the end of the
"lid close-open" list actually comes from.
Keeping keyboard backlights untouched by PowerDevil if systemd-backlight is
running seems decent. I'd have to see how we can reliably check from PowerDevil
that it's running.
Another idea would be to scrap the whole "restore previous value" concept and
instead always use the value that the user last set via PowerDevil applet
and/or KCM. Once we have that, we can take out all of the "save for later" code
and unify all the "restore brightness" code into a single place. Which would
hopefully be executed last in the wake-up process, and override whatever
systemd may or may not have dealt with.
--
You are receiving this mail because:
You are watching all bug changes.
