AllowEmptyInput and HAL

Peter Hutterer peter.hutterer at who-t.net
Thu May 7 18:42:03 PDT 2009


On Thu, May 07, 2009 at 11:50:40AM +0100, Phil Endecott wrote:
> (gdb) print dev->key->xkbInfo.state
> $4 = {group = 0 '\0', base_group = 0, latched_group = 0, locked_group =  
> 0 '\0', mods = 0 '\0', base_mods = 0 '\0', latched_mods = 0 '\0',  
> locked_mods = 0 '\0',
>   compat_state = 0 '\0', grab_mods = 0 '\0', compat_grab_mods = 0 '\0',  
> lookup_mods = 0 '\0', compat_lookup_mods = 0 '\0', ptr_buttons = 0}
>
> Here initially mods=0, but it changes:
>
> (gdb) cont
> Continuing.
>
> Breakpoint 1, XkbHandleActions (dev=0x82bf838, kbd=0x82bf838,  
> event=0x82c8268) at xkbActions.c:1072
> 1072	{
> (gdb) print dev->key->xkbInfo.state
> $7 = {group = 0 '\0', base_group = 0, latched_group = 0, locked_group =  
> 0 '\0', mods = 5 '\005', base_mods = 5 '\005', latched_mods = 0 '\0',  
> locked_mods = 5 '\005',
>   compat_state = 5 '\005', grab_mods = 5 '\005', compat_grab_mods = 5  
> '\005', lookup_mods = 5 '\005', compat_lookup_mods = 5 '\005',  
> ptr_buttons = 0}
>
> I see a pattern of mods=0 and mods=5 that's consistent with the  
> alternating pattern that I posted in the xev output previously.

this is... weird. does it happen after you run 
setxkbmap -layout "us" -model "pc105" -rules "evdev" -option "" -variant ""
(just to exclude potentially broken layouts)


> I am wondering what I could have done to provoke this.  I had a  
> ~/.xmodmap that maps caps-lock to ctrl, but that is now disabled and I  
> was getting the same problem at the xdm login dialog and when root ran  
> startx.  I also had changes to the console keymap stuff to get the same  
> effect, but I don't believe that the console keymap affects X (hence my  
> question before about where X gets the keymap from in a HAL environment, 
> i.e. does it somehow use the kernel keymap), and anyway that console 
> keymap hack stopped working after the same apt-get that broke X.

X doesn't get the keymap from HAL. The HAL configuration just says "load
this layout", then X goes off and begs xkbcomp to do the right thing. This
is the same process as the xorg.conf process, except that in one case you
load the layout string from dbus and the other time from a file.
either way "us" and "pc105" should be the same in both (or whatever the
layout is).

> And I'm still getting errors from xkbcomp, despite disabling my ~/.xmodmap.

I think it might be best now to take that issue to bugs.freedesktop.org. i
find it hard to follow log files across several emails.

Cheers,
  Peter



More information about the xorg mailing list