Bug#523562: autodetected keyboard has massively mismapped keycodes

[Julien Cristau <jcristau@debian.org>]

On Fri, 2009-04-10 at 23:08 -0500, Manoj Srivastava wrote:
>         So, I let the server autodetect the keyboard, and it came up
>  with:
>   (**) AT Translated Set 2 keyboard
> 
>         Now, I have a Logitech Cordless Comfort Duo setup. After
>  logging in, I discovered that my arrow keys, home, end, prior, next,
>  print, pause, alt_r, control_r, kp_enter, KP_Divide, Super_r,
>  multi_key had been randomly rearranged, and thus hitting up arrow
>  tried to print the screen.
> 
>         There was an extensive session with xev, xbindkeys -mk, and
>  xmodmap before I could start using the machine, and I suspect most
>  users would not have the knowledge to do what I did.
> 
>         Oh, and  Option "AllowEmptyInput" "false" gave me multiple
>  input devices, I could not login as user  sssrrriiivvvaaassstttaaa.
>  (each keypress resulted in three characters)

The evdev driver, which is used by default with input-hotplug, indeed
uses a different set of keycodes than the traditional kbd driver.  I'm
not sure there's a way to make that transition not painful for people
using xbindkeys/xmodmap and assuming the previous set of keycodes... :(

Cheers,
Julien