We are running thin clients based on thinstation (thinstation.sf.net) 2.2beta1. It has Xorg X server and uses _only_ precompiled xkbmaps.
I googled out that _XKB_RULES_NAMES property is not set for precompiled keymaps (see http://sourceforge.net/mailarchive/message.php?msg_id=11096034 for details). Setxkbmap should however be smart enough to handle such case, which is AFAIK (=as I was told) correct as far as XKB specification goes. The very same problem is the source of some GNOME-keyboard-switching bugs (_XKB_RULES_NAMES not set, but GNOME wrongly expects it). Screenshot (yes, it has the "Warning: Multiple definitions of keyboard model" line if run with -v, as in the original report): [EMAIL PROTECTED]:~$ setxkbmap us Couldn't interpret _XKB_RULES_NAMES property Use defaults: rules - 'xfree86' model - 'pc101' layout - 'us' free(): invalid pointer 0x41152030! Error loading new keyboard description [EMAIL PROTECTED]:~$ setxkbmap -print us Couldn't interpret _XKB_RULES_NAMES property Use defaults: rules - 'xfree86' model - 'pc101' layout - 'us' free(): invalid pointer 0x41152030! xkb_keymap { xkb_keycodes { include "xfree86+aliases(qwerty)" }; xkb_types { include "complete" }; xkb_compat { include "complete" }; xkb_symbols { include "pc/pc(pc101)+pc/us" }; xkb_geometry { include "pc(pc101)" }; }; [EMAIL PROTECTED]:~$ Eventually, I was able to load a keymap into the Xserver (with bunch of warnings from xkbcomp, but it worked at least) as follows: [EMAIL PROTECTED]:~$ setxkbmap -print us | grep -v -e 'Couldn' -e 'Use' | xkbcomp - $DISPLAY Setxkbmap should NOT use stdout for error messages (that's what stderr is for), feeding garbage into xkbcomp. I don't know if this has not been fixed in xorg, that is however irrelevant for sarge at least. Anyone knowing how to fix this for GNOME/KDE please contact me or post here for record. If you need any additional information, I will be happy to provide it. Regards, VS ii xbase-clients 4.3.0.dfsg.1-8 ii xlibs 4.3.0.dfsg.1-10 ii xlibs-data 4.3.0.dfsg.1-10 -- Vaclav Smilauer <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
