After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 137438 - Error activating XKB configuration
Error activating XKB configuration
Status: RESOLVED NOTGNOME
Product: gnome-control-center
Classification: Core
Component: Keyboard
2.5.x
Other Linux
: Normal major
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
: 139462 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-03-17 00:21 UTC by Reinout van Schouwen
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description Reinout van Schouwen 2004-03-17 00:21:34 UTC
Upon launching 2.6 beta, I am greeted with a message that there was an
error activating the XKB-configuration.

The X-server version info is: Mandrake Linux (XFree86 4.3, patch level 29mdk)
40300001

The result of xprop -root |grep XKB:
_XKB_RULES_NAMES_BACKUP(STRING) = "xfree86", "pc105", "en_US", "", ""
_XKB_RULES_NAMES(STRING) = "xfree86", "pc105", "en_US", "", ""

The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/xkb:
 layouts = [en_US,us_intl]
 model = pc105
 overrideSettings = false
 options = []
Comment 1 Andrew Sobala 2004-04-01 20:16:32 UTC
Sergey, is this one of yours?
Comment 2 Diego Pontoriero 2004-04-08 20:36:59 UTC
Don't know if some additional info is relevant.

2.6.0, Gentoo Linux (fresh install).  xorg-x11 server.

result of xprop -root | grep XKB:
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc101", "us", "", ""
_XKB_RULES_NAMES(STRING) = "xorg", "pc101", "us", "", ""

result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/xkb:
 layouts = [us]
 model = pc101
 overrideSettings = false
 options = []
Comment 3 Sergey V. Udaltsov 2004-04-08 21:13:55 UTC
Well, it looks like mine but ... 

First, about the first problem. It is really xfree bug. Just try: 

# setxkbmap -layout en_US,us_intl

It does not work for me ("Error loading new keyboard description") - it means X
is not able to handle this combination (welcome to xfree bugzilla)

Second, there is a problem with the last example. There should NOT be "xorg" in
XKB_RULES_NAMES. It is a bug in xorg server (it seems some IDIOT replaced all
occurences of xfree with xorg). This is the name of the file with rules - and
its name is xfree86 (see /usr/X11R6/lib/X11/xkb/rules/xfree86*).

Also
Comment 4 Sergey V. Udaltsov 2004-04-08 21:15:16 UTC
So, closing it. GNOME cannot fix X server problems.
Comment 5 Sergey V. Udaltsov 2004-04-09 08:18:52 UTC
For Diego: actually, I told yesterday to Keithp, the "xorg" rules name is not a
bug in xorg server, it's a feature. The only problem is that libxklavier is not
able to handle it properly. I will try to release the version of libxklavier
supporting this feature ASAP. Thanks for reporting.
Comment 6 Reinout van Schouwen 2004-04-09 09:33:33 UTC
FWIW, I'm the original reporter, and I'm not using an Xorg server.
Comment 7 Sergey V. Udaltsov 2004-04-09 10:10:48 UTC
For Reinout: I know:) Your problem is caused by xfree - it cannot handle these
two layouts together. Did you try "setxkbmap -layout en_US,us_intl"?
Comment 8 Sergey V. Udaltsov 2004-04-09 20:44:56 UTC
Diego: would you mind trying the version 1.01 of libxklavier? Just do "configure
--with-xkb-rules-set=xorg"
Comment 9 Reinout van Schouwen 2004-04-10 15:10:05 UTC
$ setxkbmap -layout en_US,us_intl
Error loading new keyboard description
Comment 10 Sergey V. Udaltsov 2004-04-11 20:36:16 UTC
Reinout: exactly what I meant! Broken XFree xkbcomp. It is either the famous fix
for xfree which was not applied (it was put short after 4.3 release) or
something which was never reported and fixed.
Comment 11 Diego Pontoriero 2004-04-11 23:10:24 UTC
Sergey:

Yes.  I created a new ebuild in gentoo for 1.01, added that flag, upgraded, and
things are good again.  Volume keys work as well once configured!

Thank you :-)
Comment 12 Sergey V. Udaltsov 2004-04-12 01:44:07 UTC
Diego: Thanks. I could not check it myself so your test was very important for me.
Comment 13 Jody Goldberg 2004-04-13 19:13:59 UTC
*** Bug 139462 has been marked as a duplicate of this bug. ***
Comment 14 Sander 2004-04-14 16:02:57 UTC
Diego, you said: "Just do "configure --with-xkb-rules-set=xorg" ", but if I do
that in a terminal I get an error the command configure is not found. So what am
I doing wrong ?
Comment 15 Sergey V. Udaltsov 2004-04-14 16:19:10 UTC
Sander: take and build libxklavier 1.02 - you won't need this option at all!
Same recommendation for all other people. The version 1.02 provides dynamic
run-time xkb rules set detection - and I'd be grateful if people with xorg
server report their results against new version.
Comment 16 Sander 2004-04-15 13:20:36 UTC
Sergey: It didn't work for me :(
My keyboard is "dead" in Gnome, but I figured out my keyboard does work as root,
but not as a normal user :S
I think it has something to do with that I don't have the right permissions or
so as a normal user, but I don't know wich permissions and for which file...
Comment 17 Sergey V. Udaltsov 2004-04-15 14:35:10 UTC
which permissions???? No permissions are involved. As long as gconf is working
for you. 

Well, could you please clean gconf properties related to
/desktop/gnome/peripherals/keyboard/xkb - probably this will "reset" the
situation. If you cannot do it in X, do it in console - in $HOME/.gconf directory.
Comment 18 Sander 2004-04-15 14:51:30 UTC
Does that mean I can just empty
$HOME/.gconf/desktop/gnome/peripherals/keyboard/xkb or should I edit the file
%gconf.xml in that directory ?
Comment 19 Sander 2004-04-15 15:01:02 UTC
Nevermind, I edited the file
$HOME/.gconf/desktop/gnome/peripherals/keyboard/xkb/%gconf.xml.

the xkbLayout was wrong in that file, so I changed it, and now everything is
working OK :):):)
Comment 20 Sander 2004-04-15 15:01:38 UTC
Before I forget:

Thanks very much Sergey !!!! :)
Comment 21 Sergey V. Udaltsov 2004-04-15 15:35:50 UTC
:) No problem. Glad we made it.:)
Comment 22 kang 2004-04-19 12:49:30 UTC
hi,
i'm using x.org and gnome 2.6 and i'm getting the same error. I had the error
already in xfree4.3 when i upgraded to gnome 2.6, now switched to x.org and have
the same problem.
I am using libxklavier 1.02
I tried changing the values in .gconf/desktop/gnome/peripherals/keyboard/xkb
I tried removing all gnome settings (rm'ed all the .gnome .gconf .gst etc files)

And.. I still get the problem :/

--
xprop -root |grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "fr", "", ""
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "fr", "", ""

gconftool-2 -R /desktop/gnome/peripherals/keyboard/xkb
 layouts = [fr]
 model = pc105
 overrideSettings = false
 options = []

Release Date: 18 December 2003
X Protocol Version 11, Revision 0, Release 6.7
Build Operating System: Linux 2.6.4-rc2 i686 [ELF]

(**) |-->Input Device "Keyboard1"
(**) Option "XkbModel" "pc105"
(**) XKB: model: "pc105"
(**) Option "XkbLayout" "fr"
(**) XKB: layout: "fr"
(==) Keyboard: CustomKeycode disabled

setxkbmap -layout fr_FR
Error loading new keyboard description


I'm really a bit stuck 
Comment 23 Sergey V. Udaltsov 2004-04-19 13:22:39 UTC
kang:

First, your setxkbmap command is wrong. Please try "setxkbmap -layout fr".

Does this work?

The x.org server is getting pain in the arse, xkb-wise :/
Comment 24 Andrew Sobala 2004-04-19 13:25:21 UTC
svu, remember to reopen the bug if it turns out to still be an issue.
Comment 25 Arwed v. Merkatz 2004-04-19 16:06:16 UTC
Works fine here with the x.org server and libxklavier 1.02.
Comment 26 mark 2004-05-25 22:04:26 UTC
I am using Accelarated X rather than Xfree or Xorg an I get the same problem,

this is the output from 

xprop -root | grep XKB
'nothing, nada blank'

and for

gconftool-2 -R /desktop/gnome/peripherals/keyboard/xkb
 layouts = [us]
 model = pc105
 overrideSettings = false
 options = []

any ideas
Comment 27 Sergey V. Udaltsov 2004-05-25 22:31:41 UTC
Sure your X server is BROKEN. I cannot do much about it. The root window
property _XKB_RULES_NAMES should be set properly. This bug exists for Solaris X
server - they addmitted it and fixed it. libgswitchit (libxklavier, to be true)
cannot live without this property. I think you should claim this bug to the
vendor's support service.

Sorry for bad news.
Comment 28 Ed Catmur 2004-05-25 23:46:38 UTC
Well, the problem is still in evidence here.
$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "gb", "", ""
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "gb", "", ""
$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/xkb
 layouts = [gb]
 model = pc105
 overrideSettings = false
 options = []
$ setxkbmap -layout gb
Error loading new keyboard description

xorg version 6.7.0, libxklavier 1.02

A workaround is to use `setxkbmap -layout gb -print | xkbcomp - $DISPLAY' - for
some reason xkbcomp works though setxkbmap fails. I have this in my
/etc/xprofile and while the error dialog still appears at least the keyboard works.
I appreciate that this is a bug in X.org, not in Gnome, but would it be possible
to fall back to using xkbcomp?
Comment 29 Sergey V. Udaltsov 2004-05-26 01:05:01 UTC
Actually x server DOES use xkbcomp. The only thing is that it is doing it in
some weird way:( Well, I am going to install FC2 soon so I'll play with X.org
server and probably get more info on this #$%^&*() server...
Comment 30 Sergey V. Udaltsov 2004-05-27 08:42:21 UTC
Yesterday installed FC2 - and it worked for me ok. Just one thing I had to do is
symlink xorg.xml to xfree86.xml - and it was ok.
Comment 31 Ed Catmur 2004-06-03 22:15:07 UTC
Finally I've fixed it on my machine. After looking at the source (yeah, should
have done that earlier) I found that X doesn't call /usr/X11R6/bin/xkbcomp, it
calls /usr/X11R6/lib/X11/xkb/xkbcomp; it turns out the latter wasn't getting
installed properly.
Once that's fixed it works fine.

You may be able to close this bug now, sorry for wasting your time.
Comment 32 Sergey V. Udaltsov 2004-06-03 22:39:31 UTC
No problem. If there are no objections, I am closing it...