https://bugs.kde.org/show_bug.cgi?id=506708
--- Comment #4 from [email protected] --- Thank you for the response. I would like to clarify the problem further, because it seems there may have been a misunderstanding: When I am not logged into the Wayland desktop, brightness can be freely adjusted both in SDDM and in any TTY using brightnessctl or similar tools. When I log into the Wayland KDE Plasma session, brightness is adjusted as expected inside the desktop environment. However, at this point: The brightness of the TTY switches to the maximum level (255). After that, neither KDE tools nor brightnessctl can change the TTY brightness anymore, even if I switch back to TTY or log out of the desktop session. This behavior is reproducible every time. >From a user perspective, it effectively makes TTY brightness permanently locked after starting a Wayland session, unless I reboot the system. I believe this is a usability problem (or a bug), since it is not documented or expected that using the desktop session would permanently disable brightness control in other virtual consoles. If this is indeed intentional design, could you please confirm it explicitly? Otherwise, I think it should be considered at least a usability issue. -- You are receiving this mail because: You are watching all bug changes.
