https://bugs.kde.org/show_bug.cgi?id=489020
Jakob Petsovits <jpe...@petsovits.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jpe...@petsovits.com
Resolution|--- |WAITINGFORINFO
Status|REPORTED |NEEDSINFO
--- Comment #6 from Jakob Petsovits <jpe...@petsovits.com> ---
(In reply to mr.yamamoto from comment #5)
> To be clear, it seems as though whatever controls the values from kdes side
> (which it would seem is powerdevil ddcutil?) is changing the values to
> something that isn't correct, as it's not simply alternating the brightness.
> What I'm doing to "fix" it, is using ddcutil, and factory resetting the
> monitor, then changing the brightness to 100. The incorrect thing that is
> happening, is it doesn't seem to be changing the brightness, but the
> contrast and other random settings, which was not a behavior I observed
> until upgrading to 6.1
What PowerDevil does is to query the monitor's capabilities using libddcutil,
and if the "brightness" capability (VCP code 10) is supported then it sets the
value for VCP code 10 that to whatever brightness is requested by other Plasma
components. The main components that request brightness changes are the
Brightness and Color applet as well as the "Dim screen" option in System
Settings / Power Management. Plasma 6.1 does not set brightness on session
start-up.
The part that's new in Plasma 6.1 is that we're now also observing monitor
connection & disconnection & sleep events through a function that was
introduced recently in libddcutil 2.x. There is a chance that somehow your
Wacom responds poorly to this? But I don't know what DDC commands are emitted
by libddcutil to implement this functionality. Other than that, Plasma's use of
DDC commands is the same as before.
It would be great if you could use `ddcutil dumpvcp` to compare whether any
monitor settings (a.k.a. VCP feature values) are different before and after the
undesired change. Realistically though, if this comparison doesn't show an
obvious mistake on our part, you may have to create a ticket on the GitHub
issue tracker of upstream ddcutil.
Note that as a workaround, you can disable the use of ddcutil in
Plasma/PowerDevil by setting an enviroment variable POWERDEVIL_NO_DDCUTIL=1.
For more details, see the PowerDevil README:
https://invent.kde.org/plasma/powerdevil/-/blob/master/README.md#troubleshooting-ddcci-monitor-brightness-controls
--
You are receiving this mail because:
You are watching all bug changes.
