https://bugs.kde.org/show_bug.cgi?id=495544
Zamundaaa <xaver.h...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |CONFIRMED
Ever confirmed|0 |1
--- Comment #1 from Zamundaaa <xaver.h...@gmail.com> ---
> https://discuss.kde.org/t/powerdevil-is-re-setting-my-display-brightness-after-the-display-wakes-up/23079/11
> mentions that unexpected brightness changes are a blow to professional
> calibrated setups. It's a little ironic that KWin, which now has so many
> great color management features, can also be responsible for breaking these
> setups by insisting to handle monitor brightness.
That comment complains about software brightness... but wrongly so. Software
brightness is very much a serious method and does not invalidate a profiled
setup, and it's actually the only way to correctly change the brightness with
an ICC profile, as they only contain data about one fixed backlight level.
I'm fine with making powerdevil no longer integrate with KWin for 6.2, but I
just wanted to emphasize that for color management we actually really benefit
from having control over it because of that whole issue with ICC profiles only
supporting one fixed setup. In the long term it would be best if we could
control all the screen settings, record them when the screen is profiled, and
ensure they're set the very same way whenever that profile is used.
About
> a "Disable brightness controls for this display" checkbox
I don't think it's worth having that for external tools (no need to repeat my
opinion about that here), but I've seen a few people complain their monitors do
weird things like change some contrast option instead of the backlight, so I
don't think we can get around it.
--
You are receiving this mail because:
You are watching all bug changes.
