Bug 472 - Error activating XKB configuration
Summary: Error activating XKB configuration
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Input/Keyboard (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
: 514 519 553 562 580 593 649 723 730 747 752 822 823 1063 1371 1493 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-04-14 09:24 UTC by Marshall Boykin
Modified: 2018-11-28 06:08 UTC (History)
17 users (show)

See Also:
i915 platform: ALL
i915 features:


Attachments

Description Marshall Boykin 2004-04-14 09:24:28 UTC
Error after using "yum" to update Fedora core 2 test 2 on April, 14 2004
Error activating XKB configuration. 
Probably internal X server problem. 
 
X server version data: 
The X.Org Foundation 
60700000 
 
If you report this situation as a bug, please include: 
- The result of xprop -root | grep XKB 
[root@Fedora-C2-T2 root]# xprop -root | grep XKB 
_XKB_RULES_NAMES_BACKUP(STRING) = "xfree86", "pc105", "us", "", "" 
_XKB_RULES_NAMES(STRING) = "xfree86", "pc105", "us", "", "" 
 
 
- The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/xkb 
[root@Fedora-C2-T2 root]# gconftool-2 -R /desktop/gnome/peripherals/keyboard/xkb
layouts = [us] 
 model = pc105 
 overrideSettings = false 
 options = []
Comment 1 Stéphane Loeuillet 2004-04-16 11:32:00 UTC
change 'xfree86' to 'xorg' in your /etc/X11/xfree86.conf (or /etc/X11/xorg.conf
if you renamed your old one)

replace
    Option "XkbRules"   "xfree"
by
    Option "XkbRules"   "xorg"
Comment 2 Mike A. Harris 2004-04-17 08:43:29 UTC
This problem is reported in our Red Hat bugzilla multiple times also, and
I tracked the problem down a couple days ago to the same issue.  The
XkbRules line can just be removed from the X server config file entirely
and then the built in default gets used, which is a better solution I believe.

So this bug is actually not an X.org bug, but a config file misconfiguration.
The Red Hat config tools are updated now to not put this line in the config
file.

Closing bug as 'INVALID' as bugzilla does not have a "NOTABUG" resolution.
Comment 3 Stéphane Loeuillet 2004-06-07 02:18:45 UTC
*** Bug 723 has been marked as a duplicate of this bug. ***
Comment 4 Stéphane Loeuillet 2004-06-07 02:19:14 UTC
*** Bug 519 has been marked as a duplicate of this bug. ***
Comment 5 Stéphane Loeuillet 2004-06-07 02:19:43 UTC
*** Bug 562 has been marked as a duplicate of this bug. ***
Comment 6 Stéphane Loeuillet 2004-06-07 02:20:04 UTC
*** Bug 580 has been marked as a duplicate of this bug. ***
Comment 7 Stéphane Loeuillet 2004-06-07 02:20:27 UTC
*** Bug 593 has been marked as a duplicate of this bug. ***
Comment 8 Stéphane Loeuillet 2004-06-07 02:20:38 UTC
*** Bug 649 has been marked as a duplicate of this bug. ***
Comment 9 Stéphane Loeuillet 2004-06-07 02:21:17 UTC
*** Bug 553 has been marked as a duplicate of this bug. ***
Comment 10 Stéphane Loeuillet 2004-06-07 02:22:29 UTC
*** Bug 514 has been marked as a duplicate of this bug. ***
Comment 11 Adam Jackson 2004-06-08 09:33:19 UTC
*** Bug 730 has been marked as a duplicate of this bug. ***
Comment 12 Adam Jackson 2004-06-13 14:07:37 UTC
*** Bug 747 has been marked as a duplicate of this bug. ***
Comment 13 Adam Jackson 2004-06-14 15:08:03 UTC
*** Bug 752 has been marked as a duplicate of this bug. ***
Comment 14 Adam Jackson 2004-07-05 09:36:35 UTC
*** Bug 823 has been marked as a duplicate of this bug. ***
Comment 15 Adam Jackson 2004-08-12 16:14:39 UTC
*** Bug 1063 has been marked as a duplicate of this bug. ***
Comment 16 Adam Jackson 2004-09-14 21:44:09 UTC
*** Bug 1371 has been marked as a duplicate of this bug. ***
Comment 17 Adam Jackson 2004-09-29 11:51:31 UTC
*** Bug 1493 has been marked as a duplicate of this bug. ***
Comment 18 Daniel Stone 2006-04-02 10:41:00 UTC
*** Bug 822 has been marked as a duplicate of this bug. ***


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.