[solved]"Error activating XKB configuration"

Question

[2009-02-14 00:55] upgraded compizconfig-python (0.7.8-1 -> 0.7.8-2)
[2009-02-14 00:55] ==> Updating icon cache.....
[2009-02-14 00:55] upgraded fusion-icon (20080313-1 -> 20090213-1)
[2009-02-14 00:55] upgraded libtasn1 (1.7-1 -> 1.8-1)
[2009-02-14 00:55] upgraded gnutls (2.6.3-1 -> 2.6.4-1)
[2009-02-14 00:55] upgraded hdparm (9.6-1 -> 9.10-1)
[2009-02-14 00:55] upgraded inputproto (1.4.4-1 -> 1.5.0-1)
[2009-02-14 00:55] upgraded libice (1.0.4-1 -> 1.0.5-1)
[2009-02-14 00:55] upgraded xcb-proto (1.2-2 -> 1.3-1)
[2009-02-14 00:55] upgraded libxcb (1.1.90.1-1 -> 1.1.93-1)
[2009-02-14 00:55] upgraded libx11 (1.1.5-2 -> 1.1.99.2-2)
[2009-02-14 00:55] upgraded xextproto (7.0.4-1 -> 7.0.5-1)
[2009-02-14 00:55] upgraded libxext (1.0.4-1 -> 1.0.5-1)
[2009-02-14 00:55] upgraded libxi (1.1.4-1 -> 1.2.0-1)
[2009-02-14 00:55] upgraded pciutils (3.0.3-1 -> 3.1.2-1)
[2009-02-14 00:55] upgraded pixman (0.12.0-1 -> 0.14.0-1)
[2009-02-14 00:55] upgraded sound-theme-freedesktop (0.1-1 -> 0.2-1)
[2009-02-14 00:55] upgraded xf86-input-evdev (2.1.0-1 -> 2.1.2-1)
[2009-02-14 00:55] upgraded xf86-input-keyboard (1.3.1-1 -> 1.3.2-1)
[2009-02-14 00:55] upgraded xf86-input-synaptics (0.99.3-1 -> 1.0.0-1)
[2009-02-14 00:55] upgraded xkeyboard-config (1.4-2 -> 1.5-1)
[2009-02-14 00:55] upgraded xterm (239-1 -> 241-1)
And now every time I fire up my Gnome session via startx I got this error message:
Error activating XKB configuration.
It can happen under various circumstances:
- a bug in libxklavier library
- a bug in X server (xkbcomp, xmodmap utilities)
- X server with incompatible libxkbfile implementation
X server version data:
The X.Org Foundation
10503000
If you report this situation as a bug, please include:
- The result of xprop -root | grep XKB
- The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "dvorak,us", "", "caps:swapescape"
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "dvorak,us", "", "caps:swapescape"
Or "evdev" if I enabled hotplugging
gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
layouts = [dvorak,us]
model = pc104
options = [grp grp:toggle]
Doesn't matter if I use hotplugging or not (cuz even if I do away with xorg.conf, I still encounter this problem). I am stuck with the US layout, and unable to Ctrl-Alt-Backspace, or Ctrl-Alt-F1 etc.
Any suggestions?
Last edited by allbluedream (2009-02-15 03:09:19)

Answer 1

I have the same problem, but that fix didn't help.  I incorrectly get QWERTY in the login manager (slim) and the same error as allbluedream when logging into a Gnome session.
$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "evdev", "dvorak,us", "", "grp:shift_toggle"
_XKB_RULES_NAMES(STRING) = "evdev", "evdev", "dvorak", "", "grp:shift_toggle"
$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
layouts = []
model = thinkpad60
options = []
$ cat /etc/hal/fdi/policy/10-keymap.fdi
<?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- -->
<deviceinfo version="0.2">
<device>
<match key="info.capabilities" contains="input.keymap">
<append key="info.callouts.add" type="strlist">hal-setup-keymap</append>
</match>
<match key="info.capabilities" contains="input.keys">
<merge key="input.xkb.rules" type="string">base</merge>
<!-- If we're using Linux, we use evdev by default (falling back to
keyboard otherwise). -->
<merge key="input.xkb.model" type="string">keyboard</merge>
<match key="/org/freedesktop/Hal/devices/computer:system.kernel.name"
string="Linux">
<merge key="input.xkb.model" type="string">evdev</merge>
</match>
<merge key="input.xkb.layout" type="string">us,us</merge>
<merge key="input.xkb.variant" type="string">dvorak,basic</merge>
<merge key="input.xkb.options" type="string">grp:shift_toggle</merge>
</match>
</device>
</deviceinfo>