https://bugs.kde.org/show_bug.cgi?id=485437
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |DUPLICATE
Status|NEEDSINFO |RESOLVED
--- Comment #4 from Nate Graham <n...@kde.org> ---
Well, we're in an awkward situation here where we don't have any ideal choices:
1. Always let the brightness go to 0% - with many devices and drivers, this
turns off the backlight entirely, which is not useful. We get bug reports.
2. Always stop at 1% - for devices where the minimum brightness value doesn't
turn off the backlight, the lowest brightness level is locked out. We get bug
reports.
3. Usually stop at 1%, but allow going down to 0% with some kind of less
obvious UI - inconsistency that people don't understand. We get bug reports.
4. Make it user-configurable: amounts to a workaround for hardware/driver bugs
that 99.9% of users will not understand or care about; increasing complexity in
the process. We would probably stop getting bug reports, but at the cost of a
more cluttered UI unless we hid the setting somewhere deep in the powerdevil
KCM, in which case people who could benefit from it might not find it and we'd
get bug reports anyway.
5. Go out there and fix all hardware and GPU drivers to never turn off the
backlight at minimum brightness - infeasible as we lack the resources and
technical know-how.
Maybe #4 is the last-bad choice, and in fact Natalie submitted a merge request
to do this in
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4117. Let's
follow up there.
*** This bug has been marked as a duplicate of bug 483490 ***
--
You are receiving this mail because:
You are watching all bug changes.
