xkb: wrong KeySym at first start of X

[chris_honschu at gmx.de]

On Thursday, 13. August 2009, Peter Hutterer wrote:
> On Tue, Aug 11, 2009 at 04:15:37PM +0200, chris_honschu at gmx.de wrote:
> > at the first start and at the very beginning of a running X
> > the KeySym changes from a wrong value to the correct
> > one.
> > Is this a bug? Because thereby my window-manager
> > keymappings go wrong.
> >
> > I have a 'de' (German) keyboard (qwertz).
> > For the first ~14k loops of xkeytest the button "y" is
> > referred to a 'z':
> >
> > loop-nr.:0 testing KeyCode=52 -> KeySym 0x7a name=z
> > loop-nr.:13906 testing KeyCode=52 -> KeySym 0x79 name=y
>
> the internal virtual keyboard is initialized with the default layout
> ('us'), the physical keyboard with 'de' per your configuration. once you
> hit a key on the german layout, this layout it copied over into the virtual
> one and the virtual keyboard also has a german layout.
> so the change from 'us' to 'de' is not accidental.

/tmp/xkeytest:
*** date:
Tue Aug 11 15:13:51 CEST 2009
loop-nr.:0 testing KeyCode=52 -> KeySym 0x7a name=z
*** xprop -root | grep XKB
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "de", "", ""

I didn't have a look at the sourcecode of xprop but shouldn't it print out 
a 'us' instead of a 'de' keyboard layout,?
So here is a bug in either xprop or in xorg. Am I right?

> the problem here seems to be that the client doesn't listen to mappin
> a client should listen to MappingNotify or the respective XKB events to
> re-load the keysym table when the layout changes.

Thanks for the hint.