Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

power: Do not compute percentage on keyboard disappearing #43

Merged
merged 1 commit into from Jan 4, 2018
Merged

Conversation

carlocaione
Copy link
Contributor

When the module in charge of the keyboard backlight is rmmod-ed, upower
emits a new signal to communicate to gsd that we don't have backlight
anymore. This signal is carrying (value == -1, max == 0).
In this case we do not want to calculate the new brightness.

Signed-off-by: Carlo Caione <carlo@endlessm.com>
@wjt wjt merged commit 56b2d11 into master Jan 4, 2018
@wjt wjt deleted the T19702 branch January 4, 2018 16:29
gnomesysadmins pushed a commit to GNOME/gnome-settings-daemon that referenced this pull request Sep 3, 2020
When the module in charge of the keyboard backlight is rmmod-ed, upower
emits a new signal to communicate to gsd that we don't have backlight
anymore. This signal is carrying (value == -1, max == 0).
In this case we do not want to calculate the new brightness.

Signed-off-by: Carlo Caione <carlo@endlessm.com>

Note 2020-09-03: Based on discussion on the Endless bug tracker, the
steps to reproduce this are to unplug a Filco USB keyboard from a
Mission One, but perhaps it's applicable on other hardware as well.
The original PR for this was
endlessm/gnome-settings-daemon#43
- mwleeds
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants