https://bugs.kde.org/show_bug.cgi?id=499034
--- Comment #5 from amdfa...@gmail.com --- (In reply to Nate Graham from comment #4) > I agree we shouldn't override the hardware's *default* brightness setting. > But is that actually what we're doing? > > In other words, if you have a monitor that's set to 25% brightness by > default the first time you plug it in, and you change it to 50% in your > current user account, and then you create a new user account, is it getting > set to 100% in the new user account? Or 50%? Here's an example: - Through my monitor's built in controls and on-screen-display, I manually set the monitor's brightness to 30% - If I boot into Windows, Ubuntu or KDE X11, the monitor's brightness remains at 30%. KDE X11 will even acknowledge the monitor's brightness being 30% in the brightness tray icon - Creating and then logging into a new account on Windows, Ubuntu, or KDE X11 will respect the 30% brightness level the monitor already has set. - A fresh install of an OS with KDE Wayland will *not* respect the monitor's already existing hardware brightness level. First log-in on Fedora KDE or Tumbleweed with a KDE Wayland will force the monitor to 100% brightness. If I manually go into my monitor, and reset the brightness to 30%, or set the brightness to 30% using the tray slider, it will remember it. - If I create a new account and log in to that new account, or re-install the OS, it will override my brightness settings back to 100%, even though I already turned them back to 30% prior. -- You are receiving this mail because: You are watching all bug changes.
