Red Hat Bugzilla – Bug 150159
Adding new kbd language fails
Last modified: 2008-02-06 19:22:27 EST
Description of problem:
Adding new kbd language fails on some languages but not all.
Version-Release number of selected component (if applicable):
FC3 Kernel 2.6.10; X with Gnome
Adding language to kbd as described in following steps
Steps to Reproduce:
2. Select language in right column (all French fails and some others)
3. Click Add then ERROR
Error activating XKB configuration.
Probably internal X server problem.
X server version data:
The X.Org Foundation
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/xkb
New language added
dumps of statements asked for in error message in attachment
Created attachment 111605 [details]
dump of the second request from error message
Created attachment 111606 [details]
dump of the first request from error message
The 'kbd' suite of utilities is for changing the console keymap, not for X.
I might have selected the wrong component in the list as I am not
knowledgeable into that, I just selected whatever seemed the closest to what I
tried to do. If you know what component my bug relates to, can you reassign
because if it is for console or X, the Applications/Preferences/Keyboard still
cause an error (for me at least).
I just want to add a little correction. Not all French keyboards crash, but
for sure that French Canadian and Swiss French have problems. (Azerbaijani
also crashes and some others as well).
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Fedora Core 3 is not maintained anymore.
Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release please reopen this bug and assign it to the corresponding