Bug 180861 - Error activating XKB configuration
Summary: Error activating XKB configuration
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: gnome-applets
Version: 4.0
Hardware: ia64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Ray Strode [halfline]
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
: 180862 180863 180864 180865 180866 180867 180868 180869 180870 180872 180873 180874 180875 180876 180877 180878 180879 180880 180881 180882 180883 180884 180885 180886 180887 180888 180889 180890 180891 180892 180893 180894 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-02-10 11:06 UTC by Karsten Elgaard Sørensen
Modified: 2012-06-20 13:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 13:26:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Karsten Elgaard Sørensen 2006-02-10 11:06:10 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50215)

Description of problem:
After graphical login a window with the following text is displayed:

Error activating XKB configuration.
Probably internal X server problem.

This is happening both on local console and on login via XDMCP.

LOCALLY:
# xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "dk", "", ""
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "dk", "", ""
# gconftool-2 -R /desktop/gnome/peripherals/keyboard/xkb
 layouts = []
 model = pc105
 overrideSettings = false
 options = []
 update_handlers = []
#
XDCMP:
# xprop -root | grep XKB
# gconftool-2 -R /desktop/gnome/peripherals/keyboard/xkb
 layouts = [us]
 model = pc105
 overrideSettings = false
 options = []
 update_handlers = []

Version RHEL4 update 2

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.login via graphical interface
2.
3.
  

Additional info:

Comment 1 Adam Jackson 2006-02-12 03:55:34 UTC
*** Bug 180862 has been marked as a duplicate of this bug. ***

Comment 2 Adam Jackson 2006-02-12 03:56:03 UTC
*** Bug 180864 has been marked as a duplicate of this bug. ***

Comment 3 Adam Jackson 2006-02-12 03:56:07 UTC
*** Bug 180863 has been marked as a duplicate of this bug. ***

Comment 4 Adam Jackson 2006-02-12 03:56:23 UTC
*** Bug 180865 has been marked as a duplicate of this bug. ***

Comment 5 Adam Jackson 2006-02-12 03:56:28 UTC
*** Bug 180866 has been marked as a duplicate of this bug. ***

Comment 6 Adam Jackson 2006-02-12 03:56:43 UTC
*** Bug 180867 has been marked as a duplicate of this bug. ***

Comment 7 Adam Jackson 2006-02-12 03:57:00 UTC
*** Bug 180868 has been marked as a duplicate of this bug. ***

Comment 8 Adam Jackson 2006-02-12 03:57:09 UTC
*** Bug 180869 has been marked as a duplicate of this bug. ***

Comment 9 Adam Jackson 2006-02-12 03:57:24 UTC
*** Bug 180870 has been marked as a duplicate of this bug. ***

Comment 10 Adam Jackson 2006-02-12 03:58:12 UTC
*** Bug 180872 has been marked as a duplicate of this bug. ***

Comment 11 Adam Jackson 2006-02-12 03:58:20 UTC
*** Bug 180873 has been marked as a duplicate of this bug. ***

Comment 12 Adam Jackson 2006-02-12 03:58:33 UTC
*** Bug 180875 has been marked as a duplicate of this bug. ***

Comment 13 Adam Jackson 2006-02-12 03:58:38 UTC
*** Bug 180874 has been marked as a duplicate of this bug. ***

Comment 14 Adam Jackson 2006-02-12 03:58:50 UTC
*** Bug 180876 has been marked as a duplicate of this bug. ***

Comment 15 Adam Jackson 2006-02-12 03:59:04 UTC
*** Bug 180877 has been marked as a duplicate of this bug. ***

Comment 16 Adam Jackson 2006-02-12 03:59:16 UTC
*** Bug 180878 has been marked as a duplicate of this bug. ***

Comment 17 Adam Jackson 2006-02-12 03:59:32 UTC
*** Bug 180879 has been marked as a duplicate of this bug. ***

Comment 18 Adam Jackson 2006-02-12 03:59:32 UTC
*** Bug 180880 has been marked as a duplicate of this bug. ***

Comment 19 Adam Jackson 2006-02-12 03:59:46 UTC
*** Bug 180881 has been marked as a duplicate of this bug. ***

Comment 20 Adam Jackson 2006-02-12 03:59:59 UTC
*** Bug 180882 has been marked as a duplicate of this bug. ***

Comment 21 Adam Jackson 2006-02-12 04:00:20 UTC
*** Bug 180883 has been marked as a duplicate of this bug. ***

Comment 22 Adam Jackson 2006-02-12 04:00:23 UTC
*** Bug 180884 has been marked as a duplicate of this bug. ***

Comment 23 Adam Jackson 2006-02-12 04:00:38 UTC
*** Bug 180886 has been marked as a duplicate of this bug. ***

Comment 24 Adam Jackson 2006-02-12 04:00:40 UTC
*** Bug 180885 has been marked as a duplicate of this bug. ***

Comment 25 Adam Jackson 2006-02-12 04:01:00 UTC
*** Bug 180887 has been marked as a duplicate of this bug. ***

Comment 26 Adam Jackson 2006-02-12 04:01:27 UTC
*** Bug 180888 has been marked as a duplicate of this bug. ***

Comment 27 Adam Jackson 2006-02-12 04:01:31 UTC
*** Bug 180889 has been marked as a duplicate of this bug. ***

Comment 28 Adam Jackson 2006-02-12 04:01:49 UTC
*** Bug 180890 has been marked as a duplicate of this bug. ***

Comment 29 Adam Jackson 2006-02-12 04:01:49 UTC
*** Bug 180891 has been marked as a duplicate of this bug. ***

Comment 30 Adam Jackson 2006-02-12 04:02:14 UTC
*** Bug 180892 has been marked as a duplicate of this bug. ***

Comment 31 Adam Jackson 2006-02-12 04:02:15 UTC
*** Bug 180893 has been marked as a duplicate of this bug. ***

Comment 32 Adam Jackson 2006-02-12 04:02:39 UTC
*** Bug 180894 has been marked as a duplicate of this bug. ***

Comment 33 Mike A. Harris 2006-02-13 23:06:54 UTC
Unfortunately, GNOME's keyboard applet displays this message, and incorrectly
blames the problem on a faulty X server.  It turns out the majority of the
problems are traced down to being bugs in libxklavier or the keyboard applet
itself.

I really wish the GNOME developers (or at least the Red hat package maintainer)
would remove this erroneous error message.

Reassigning to gnome-applets for diagnosis.

Comment 34 Joachim Backes 2009-06-10 21:39:22 UTC
The problem persists in F11.

Comment 35 Joachim Backes 2009-06-11 06:36:20 UTC
xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "evdev", "us", "nodeadkeys", "terminate:ctrl_alt_bksp"
_XKB_RULES_NAMES(STRING) = "evdev", "evdev", "us", "nodeadkeys", "terminate:ctrl_alt_bksp"

============================================================================
gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = []
 overrideSettings = false
 options = []
 model = pc101

Comment 36 Joachim Backes 2009-06-11 06:44:48 UTC
I got rid from the problem by re-changing my keyboard controls using System->preferences-keyboard to Germany-no-deadkeys.

Comment 37 Alexandr Kara 2009-06-14 10:14:08 UTC
Fixed by going to System -> Preferences -> Keyboard -> Layouts and selecting "Reset to Defaults" and changing settings again.

Maybe changing "Keyboard model" to "Evdev-managed keyboard" would help, too.

Comment 38 Tim Jackson 2009-06-29 19:20:36 UTC
Had the problem on an F10->F11 upgrade.
"Reset to defaults" didn't fix it for me, but going to System -> Preferences -> Keyboard and adding the same layout ("United Kingdom") as I already had, and then deleting the original (now duplicate) in the list fixed it.

My original (broken) output:

$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "evdev", "us", "", "terminate:ctrl_alt_bksp"
_XKB_RULES_NAMES(STRING) = "evdev", "evdev", "gb", "", ""
$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = [uk]
 options = []
 model = evdev

After I fiddled with it and it worked:
$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "evdev", "us", "", "terminate:ctrl_alt_bksp"
_XKB_RULES_NAMES(STRING) = "evdev", "evdev", "gb", "", "grp:shift_caps_toggle"
$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = [gb]
 options = [grp	grp:shift_caps_toggle]
 model =

Comment 39 Jiri Pallich 2012-06-20 13:26:56 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.


Note You need to log in before you can comment on or make changes to this bug.