Comment 62 for bug 261721

i still have the problem with this
Linux rook 2.6.27-10-generic #1 SMP Fri Nov 21 12:00:22 UTC 2008 i686
GNU/Linux

so i am using the purposed via synaptic
it is nice that i know i can just hit ctrl+alt+f2 to fix it (rather than
having to reboot, like i used to. but it seems that this is a major problem
that needs to be fixed for most laptop systems.

On Fri, Nov 28, 2008 at 1:17 PM, Andy Whitcroft <email address hidden> wrote:

> On Fri, Nov 28, 2008 at 04:47:03PM -0000, Cory wrote:
> > I previously thought the upgrade to 2.6.27-8 solved the problem, but I
> > just had my keyboard disabled again when trying to change brightness.
> > I've attached my lspci -nn output.
>
> Could you try the 2.6.27-10.20 release currently in -proposed.
> This has some specific fixes for brightness control. Please see
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
> enable and use -proposed. Thank you in advance!
>
> --
> X never sees brightness key release events
> https://bugs.launchpad.net/bugs/261721
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "linux" source package in Ubuntu: Fix Committed
> Status in "xorg-server" source package in Ubuntu: Invalid
>
> Bug description:
> Binary package hint: gnome-power-manager
>
> Pressing either of the brightness keys brings up the g-p-m brightness OSD.
> This has changed recently such that it now steals keyboard focus. It
> eventually disappears, leaving corruption on the screen, giving my caret
> back. However, I can't type again until I switch to another VT and back.
>
> It also sometimes doesn't appear at all, or just appears with some
> uninitialized texture (but still steals focus).
> --
>
> This is caused by X invoking autorepeat on the brightness keys, as it never
> appears to see a release event.
>