I can confirm this also with a IBM X41, on the latest gutsy x86.

For me, this is a regression from Feisty and, I think, early Gutsy.

What happens for me though, is that pressing Fn+Home takes my screen
very quickly through all the levels to full brightness, and Fn+End to
minimum (however, pressing the opposite key stops it at that point).
Also, the strange thing is that gpm cannot seem to set the requested
brightness correctly - for example on battery I've set it to 50%, but
once gpm detects this, it looks as if it tries to set it to 50%, but it
ends up going all the way down to 0%. (In a related note, the X server
seems to be responding to the AC event much slower than in Feisty, as
shown by xev again)

I'm currently loading thinkpad-acpi manually using /etc/modules to
enable brightness support, and I can confirm that xev receives multiple
brightness up/brightness down events - and running gpm in debug mode, no
daemon, shows that it is reacting to these events.

Should this be a bug filed in X server and not here in GPM, then?

-- 
lcd brightness down doesn't work when gpm running (t60)
https://bugs.launchpad.net/bugs/123548
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

Reply via email to