mactel-support team mailing list archive
-
mactel-support team
-
Mailing list archive
-
Message #02682
[Bug 662420] Re: brightness control with a too low increment (+-1) compare to brightness number (>10000)
same thing for me: after a suspend/resume, the brightness can be set so low that I thought my laptop was not resuming properly.
So it's just as if the 0-256 brightness is now coded on 0-65535 or something like this. This is great for a smoother brightness control, but it seems default value for brightness and brightness increment have not been adapted to that.
--
brightness control with a too low increment (+-1) compare to brightness number (>10000)
https://bugs.launchpad.net/bugs/662420
You received this bug notification because you are a member of Mactel
Support, which is the registrant for Mactel Support.
Status in Mactel Support: New
Bug description:
Hello,
For some days, my brightness control do not work on mbp 6.2 + Lucid.
Although the brightness level is displayed in the upper-right corner of the screen when I press the F1 and F2 keys, the brightness level does not change at all.
However, trying sudo pommed -d in a terminal gives me:
KEY: LCD backlight down
LCD stepping -1 -> 29464
E: Not primary DBus name owner
KBD: inhibit clear 0x08 -> 0x00
KEY: LCD backlight down
LCD stepping -1 -> 29463
E: Not primary DBus name owner
when I press two times the F1 key (=>decrease brightness). So it seems the stepping (-1) is just too small compared to the number representing the brightness (here: 29464), the brightness control is just too slow to be visible on a human time scale..
References