Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#16158 - [hal] brigthness problems
Attached to Project:
Arch Linux
Opened by mattia (nTia89) - Saturday, 12 September 2009, 16:31 GMT
Last edited by Jan de Groot (JGC) - Sunday, 07 March 2010, 13:43 GMT
Opened by mattia (nTia89) - Saturday, 12 September 2009, 16:31 GMT
Last edited by Jan de Groot (JGC) - Sunday, 07 March 2010, 13:43 GMT
|
DetailsDescription:
brigthness problems OR brigthness broken on Apple MacBook (2,1) Additional info: * 2.6.30.5 kernel on x86_64 * openbox 3.4.7.2 * HAL 0.5.13 Steps to reproduce: when i press the dedicated monitor's up-brightness key , brigthness value become 0, then if i press the key again, brightness suddenly become to the right value and this is in a circle. if i press again brightness s key that become 0, then if i press key again brigthness become to the right value instead if i want to reduce the brigthness by right key i can't because it increases |
This task depends upon
Closed by Jan de Groot (JGC)
Sunday, 07 March 2010, 13:43 GMT
Reason for closing: Fixed
Additional comments about closing: Should be fixed in 0.5.14-2. ioperm address reservation calls were wrong in macbook(pro) backlight backends.
Sunday, 07 March 2010, 13:43 GMT
Reason for closing: Fixed
Additional comments about closing: Should be fixed in 0.5.14-2. ioperm address reservation calls were wrong in macbook(pro) backlight backends.
Comment by mattia (nTia89) -
Saturday, 12 September 2009, 16:32 GMT
instead of decreasing !!!!
Comment by Jan de Groot (JGC) -
Sunday, 08 November 2009, 22:31 GMT
Is this still a problem with recent kernels, drivers and hal packages?
Comment by mattia (nTia89) -
Monday, 09 November 2009, 22:27 GMT
yes, with latest x86_64 package and gnome 2.28 (.1)