Not on master, targeted to Plasma/6.2 only at Xaver Hugl's request.
Brightness controls owned by KWin have proven controversial,mostly because it doesn't currently take any pre-configuredhardware brightness values into account on startup or when theuser adjusts brightness in their OSD menu. As a result, a sizeablenumber of users have resorted to setting POWERDEVIL_NO_DDCUTIL=1.
Disabling KWin brightness control integration is a first steptoward stopping the bleeding. After this, pre-configured hardwarebrightness will mostly be respected again. (PowerDevil itselfcontains one more "non-requested" brightness write in DDCutilDisplay,which gets performed after the monitor wakes up. We'll need to dealwith that one separately.)
In order to work as expected, PowerDevil cannot completely ignoreKWin's Wayland protocols. If we simply omitted our display findings,KWin configurations from before commit 4f18aae6 would use thepreviously stored hardware brightness as software brightness,and dim the screen more than necessary, without obvious recourse.
Instead, we continue to announce our external brightness devicesto KWin, but ignore KWin's listings and requests when it arrivesback at the PowerDevil service. This ensures that KWin will setsoftware brightness to 1.0, and adds a flag to KWin's output configthat will later allow us to leave the brightness device unannounced.
KWin brightness control integration is only disabled for SDR outputs.HDR brightness will continue to be exposed in the brightness applet.SDR brightness control integration can be manually enabled by settingthe environment variable POWERDEVIL_USE_KWIN_SDR_BRIGHTNESS=1until we have sufficiently addressed user concerns.
