Oh great, now my workaround has been broken, too! Now I have to press
the brightness keys FIVE times to go between adjacent brightness levels
-- and some levels are still missing! I can't, for example, use the
levels 12, 37, 62, or 87, despite those levels working when I directly
manipulate the backlight sysfs entries.
This is the change that re-broke
hal (0.5.9.1-1ubuntu9) gutsy; urgency=low
* debian/patches/64_read_brightness_not_actual_brightness.patch: Read
the brightness from /sys/class/backlight/foo/brightness, not
actual_brightness. It makes more sense to change based on the
brightness that we wanted to set, not the brightness that we
actually set.
Where's the logic in that? You should show the actual brightness, not
what you asked for! Try applying the "act based on what we asked for,
not what we got" logic to everyday situations, and see how well it
works...
Having no_automatic_changes=0 now results in my screen BLINKING every time I
press a brightness key, as the DSDT changes brightness to the right level, and
then gnome-power-manager stupidly changes it back to an invalid value.
Starting from 100%, it's like this:
100%, BLINK, BLINK, BLINK, BLINK, 75%, BLINK, BLINK, BLINK, BLINK, 50%, BLINK,
BLINK, BLINK, BLINK, 25%, BLINK, BLINK, BLINK, BLINK, 0%.
--
LCD backlight turns off between brightness levels during fades, and when on
battery or at idle
https://bugs.launchpad.net/bugs/121833
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
