https://bugs.kde.org/show_bug.cgi?id=494408

Jakob Petsovits <jpe...@petsovits.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|general                     |output configuration
                 CC|                            |xaver.h...@gmail.com
           Assignee|plasma-b...@kde.org         |jpe...@petsovits.com
            Product|Powerdevil                  |kwin
     Ever confirmed|0                           |1
             Status|NEEDSINFO                   |CONFIRMED
         Resolution|WAITINGFORINFO              |---

--- Comment #4 from Jakob Petsovits <jpe...@petsovits.com> ---
KWin defaults the brightness of every monitor to 100% and that's a bug that I
can confirm. It happens on session startup, monitor wake-up, and possibly other
KWin output configuration change events, until the default brightness is
changed. I have seen reports of this on Reddit and Lemmy.

To reproduce:
* Log out of Plasma
* Delete the "brightness" property from your monitor entry in
.config/kwinoutputconfig.json
* Manually reduce hardware brightness for your display
* Start a new Plasma Wayland session.

KWin will ask PowerDevil to max out the brightness for any display without this
entry, even if hardware brightness is currently lower than max.

The power-profile-daemon installation seems like a red herring, because monitor
brightness controls should be available with just PowerDevil by itself.
(Without PowerDevil, hardware screen brightness would not be raised.) But the
point is that the user needs to change the brightness default to get back to
their previously configured monitor brightness, and they shouldn't have to do
that.

The bad news is that a fix will require an addition to
plasma-wayland-protocols, plus matching patches in PowerDevil (to announce the
initial monitor brightness) and KWin (to use it if it was announced). While I
know that this can be done in a backwards-compatible way, I'm not sure if the
existing guidelines around Wayland protocol versioning will allow me to make it
so that PowerDevil will keep working with KWin from 6.2.0. That's a discussion
topic for the merge review though.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to