Re: X11 keyboard behaving strangely since update

[Florian Kulzer <florian.kulzer+debian@icfo.es>]

On Mon, Feb 02, 2009 at 18:39:43 +0100, Stefan Bellon wrote:
> Sorry for the late response, but somehow I was not allowed to post from
> my work account, so I had to wait till I am at home now ...

Subscribing the other email address to the whitelist might help with
that: http://lists.debian.org/whitelist/ 

> On Sun, 01 Feb, Florian Kulzer wrote:
> > On Sun, Feb 01, 2009 at 10:39:25 +0100, Stefan Bellon wrote:
> 
> > > Since the update the keyboard in X11 has gone weird. Every second
> > > key press under X11 is recognized as if the Ctrl key was pressed,
> > > i.e. every second 'm' is a newline, every second 'd' is a Ctrl-D,
> > > every second 'c' a Ctrl-C, ... you get the idea.
> > 
> > Did you check this with "xev"? Which KeyPress/Release events are
> > reported and in what order?
> 
> I did the following: press "a", release "a", press "a", release "a",
> press "s", release "s", press "s", release "s" (all lower-case):
> 
> KeyPress event, serial 32, synthetic NO, window 0x2000001,
>     root 0x8b, subw 0x2000002, time 748684, (54,33), root:(633,57),
>     state 0x0, keycode 38 (keysym 0x61, a), same_screen YES,
>     XLookupString gives 1 bytes: (61) "a"
>     XmbLookupString gives 1 bytes: (61) "a"
>     XFilterEvent returns: False
> 
> KeyRelease event, serial 35, synthetic NO, window 0x2000001,
>     root 0x8b, subw 0x2000002, time 749459, (54,33), root:(633,57),
>     state 0x5, keycode 38 (keysym 0x41, A), same_screen YES,
>     XLookupString gives 1 bytes: (01) "^A"
>     XFilterEvent returns: False

For the second keypress it looks as if CTRL and SHIFT had been held down
simultaneously ("state 0x5" in the third row), even though there were no
KeyPress events for those modifiers. I am not sure what that means.

[ snip: the same behavior for the "s" key ]

[...]

> > I would like to see the output of the following three commands:
> > 
> > awk '/InputDevice/,/EndSection/' /etc/X11/xorg.conf
> 
> sbellon@io$ awk '/InputDevice/,/EndSection/' /etc/X11/xorg.conf
>         InputDevice    "Generic Keyboard"
>         InputDevice    "Generic Mouse"
> EndSection
> Section "InputDevice"
>         Identifier  "Generic Keyboard"
>         Driver      "kbd"
>         Option      "CoreKeyboard"
>         Option      "XkbRules" "xorg"
>         Option      "XkbModel" "pc105"
>         Option      "XkbLayout" "de"
>         Option      "XkbVariant" "nodeadkeys"
> EndSection

[...]

> > setxkbmap -print
> 
> sbellon@io$ setxkbmap -print
> xkb_keymap {
>         xkb_keycodes  { include "xfree86+aliases(qwertz)"       };
>         xkb_types     { include "complete"      };
>         xkb_compat    { include "complete"      };
>         xkb_symbols   { include "pc+de(nodeadkeys)"     };
>         xkb_geometry  { include "pc(pc105)"     };
> };

That looks OK to me.

> > xmodmap
> 
> sbellon@io$ xmodmap
> xmodmap:  up to 3 keys per modifier, (keycodes in parentheses):

[ snip: your xmodmap output is the same as on my computer ]

Let's look at your versions of a few other packages. What is your output
for this:

dpkg -l xkb-data xserver-xorg-input-kbd xlibs{,-data} libx11{-6,-data} | awk '/^[^D|+]/{print $1,$2,$3}'

-- 
Regards,            | http://users.icfo.es/Florian.Kulzer
          Florian   |