https://bugs.kde.org/show_bug.cgi?id=500116
Jakob Petsovits <jpe...@petsovits.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xaver.h...@gmail.com
--- Comment #6 from Jakob Petsovits <jpe...@petsovits.com> ---
I can reproduce this now. It looks like the request comes from KWin directly
through the corresponding "external-brightness-v1" Wayland object that is still
sticking around from before the suspend/disconnect because ddcutil 2.1.4
doesn't necessarily notify us about the monitor's disappearance. The setter for
100% brightness comes in before any powerdevil-side "setBrightness()" calls are
even invoked.
I haven't yet figured out why KWin resets brightness to 100% - if you check
kwinoutputconfig.json after its disappearance, brightness is still at the lower
(e.g. 0.15) value. It only goes up to 1 once the output gets re-enabled.
We can probably work around this by removing PowerDevil's underlying display
objects if the associated KWinDisplayBrightness goes away. But it would also be
good to understand where the 100% are really coming from.
--
You are receiving this mail because:
You are watching all bug changes.
