https://bugs.kde.org/show_bug.cgi?id=506708
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|INTENTIONAL |WAITINGFORINFO --- Comment #6 from [email protected] --- Thank you for clarifying that brightness is shared globally across VTs. I do understand and fully accept that fact. However, the specific behavior I am seeing does not seem to match simply “shared brightness”: When I log into the Wayland KDE Plasma session, the brightness of the desktop is set to a normal level (e.g., 50%). At the same moment, the brightness of the TTY switches to 255 (full brightness). Even though the desktop is running with a lower brightness, the TTY stays stuck at 255. After logging out of the desktop session, the brightness cannot be adjusted anymore in the TTY by any means (brightnessctl, KDE tools, etc.). Effectively, the brightness set in KDE Plasma is not actually applied consistently to the TTY or SDDM—instead, it is forced to maximum brightness, which makes it difficult to use the system outside the desktop session. This is why I think this behavior goes beyond simply “brightness is shared across VTs,” and appears more like a bug or unintended interaction. Could you please confirm whether this specific behavior (TTY forced to max brightness even if Plasma uses a lower level) is intended? -- You are receiving this mail because: You are watching all bug changes.
