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 323462 - Error activating XKB configuration.
Error activating XKB configuration.
Status: RESOLVED DUPLICATE of bug 322955
Product: gnome-control-center
Classification: Core
Component: [obsolete] settings-daemon
2.12.x
Other All
: Normal major
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-12-07 12:39 UTC by Mark Nowiasz
Modified: 2005-12-07 15:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Description Mark Nowiasz 2005-12-07 12:39:50 UTC 
Please describe the problem:
After upgrading from 2.12.1 to Gnome 2.12.2 every time I log in I'm encountering
an error dialog: "Error activating XKB configuration.". 

It's not possible to change the keyboard or -layout using the
gnome-keyboard-properties - the same window as described above opens.

>xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "microsoftpro", "de", "", ""
_XKB_RULES_NAMES(STRING) = "xorg", "microsoftpro", "de", "", ""

>gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = [de,de       nodeadkeys,de   nodeadkeys]
 model = microsoftpro
 options = [grp grp:alts_toggle]
 overrideSettings = true


Steps to reproduce:
1. Just login :-/
2. Or try to change the keyboard
3. 


Actual results:
The aforesaid error dialog opens.

Expected results:
I would expect to change my keyboard.

Does this happen every time?
Yes.

Other information:
*Lots* of FreeBSD user are encountering the same bug - and a friend of mine,
who's running Gentoo is - after upgrading some gnome components to 2.12.2 -
having the same trouble.
Comment 1 Sebastien Bacher 2005-12-07 15:11:59 UTC 
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of 322955 ***