Bug#614936: keyboard-configuration: Modifier keys (ctrl, shift, alt) not working - Bluetooth keyboard

[Jacek Leśniewski <hyrobl@gmail.com>]

On 02/25/2011 07:15 PM, Anton Zinoviev wrote:

> reassign 614936 linux-latest-2.6
> retitle 614936 Modifier keys (ctrl, shift, alt) not working - Bluetooth keyboard
> thanks
>
> On Fri, Feb 25, 2011 at 05:53:59PM +0100, Jacek Leśniewski wrote:
>    
> > I had no problem getting to the ttys, however I do not understand why it
> > would be necessary to run the comands from the text mode console.
> >      
> Because this helps to find the source of the problem:
>
> 1. X
> 2. HID
> 3. low level kernel driver
> 4. the keyboard itself
>
> If you test only from inside of X any of these could be possible.
>
>    
> > > 2. Run "showkey -s".
> > >
> > > 3. Very quickly press Shift, press A, release Shift, release A.
> > >
> > >        
> > The output for this is the following :
> > 0x2a
> > 0xaa 0x1e
> > 0x9e
> >      
> These are the scancodes that the keyboard sends to the computer (after
> some minimal processing by the kernel).  0x2a is the pressed Shift and
> 0xaa is the released Shift - before A is pressed (0x1e).  So I see only
> three possibilities - 1. the keyboard is faulty or 2. the Bluetooth
> keyboard standard has redefined somehow the hardware protocol of the
> comunication between the keyboard and the computer and the keyboard
> driver doesn't support this new protocol or 3. that this keyboard
> generates the hardware interrupts in a strange way that confuse the
> keyboard driver of the kernel.
>
> Because of this I am reassigning the bug.  Hopefully the kernel
> developers will know what to do with this bug.
>
> Anton Zinoviev
>
>    
The keyboard cannot be fault as it works perfectly well in windows 
(annoyingly). Further more I only just bought it a week or so ago. It 
also worked well with an Android found (Samsung Galaxy S) However I'm 
not sure whether the modifiers worked propely.

As to the bluetooth protocol it might in deed be the problem.

PS. Do I have to reassign the bug or change its title, and if I do how 
do I do this ?

Anyhow thank you for the quick response.

--
Regards,
Jacek Leśniewski