Error activation XKB-config

[Sean Earp]

The latest from Mike Harris on this issue (bug 120858):

"Having spent several hours investigating this problem, yes, I
am very sure how it works.  ;o)

I have personally tested this problem and reproduced it on 2 systems
now, and I have applied the latest packages from our internal
dist-fc2 collection instance which contain fixes, including
pyxf86config, and libxklavier, and system-config-display.  Once all
X server configuration files are physically removed, and a single
brand new xorg.conf file generated, and hand inspected to ensure
that the XkbRules line is *not* present, the problem no longer
occurs for the setxkbmap issue, and other issues that have
been reported.

It is possible that there may still be other bugs present, however
so far, none of the bugs discovered with respect to the xkb rules
file have been xorg-x11 bugs.  I have discovered the config file
bug responsible for setxkbmap breaking, and confirmed the fix, and
we have discovered libxklavier hard codes the name of the rules
file as "xfree86" which is broken as designed.  Jeremy Katz has
changed libxklavier to use "xorg" as the rules file, which is a
kludge for now to get it to work, however the upstream developers
of libxklavier should change it to query the X server to get the
name of the rules file.

This issue (and others) are not closed yet in bugzilla you'll note,
which is to give enough time for all of our fixes to both get
merged into publically visible rawhide, and allow end users time
to upgrade to the new packages.  Some things were fixed only this
morning, and most likely are not publically visible yet.

Please have patience with this issue, until our fixes are available.
Once we have confirmed each issue is properly fixed, we will update
the various Xkb rules related bug reports and close them as duplicates
as can be confirmed, and close them as RAWHIDE once that can
be confirmed as well.

If gnome-keyboard-properties still is broken after these updates,
then most likely gnome-keyboard-properties or something it links
to is broken also, possibly needing a recompile, or additional
fixes.  Either way, these issues will definitely be resolved
in future builds.

Thank you once again for your patience, and your testing efforts."


On Friday, April 16, 2004, at 11:35AM, Efthym <efthym at gmx.net> wrote:

>Tried with XFConfig and xorg.conf.
>Doesn't work for me either :(

>On Fri, 16 Apr 2004 06:50:50 -0700, Sean Earp <smearp at mac.com> wrote:
>
>> Add your experiences to the bug report below so Mike can work towards 
>> tracking down the problem (if his suggestion doesn't work). Thanks,
>>
>> -Sean
>>
>> On Apr 15, 2004, at 7:12 PM, Draek wrote:
>>
>>> I spoke too soon, it doesnt work.
>>>
>>> Removed the line from /etc/X11/XF86Config and I still have the same
>>> problem with the XKB error.
>>>
>>> I also tried to just change the Xfree86 to xorg, and it didnt work
>>> either.
>>>
>>> Please help!
>>>
>>> On Thu, 2004-04-15 at 23:57, Sean Earp wrote:
>>>> Already in Bugzilla:
>>>> <https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=120858>
>>>>
>>>>  From Mike Harris (the xorg maintainer):
>>>>
>>>> "The problem is because our config tool hard codes:
>>>>
>>>>      Option "XkbRules" "xfree86"
>>>>
>>>> in the config file.  Xorg X11 uses "xorg", not "xfree86" so it
>>>> breaks.  Remove that line from the config entirely and it should
>>>> work on both XFree86 and Xorg."
>>>>
>>>> HTH,
>>>>
>>>> -Sean
>>>>
>>>> On Apr 15, 2004, at 10:34 PM, Trond Danielsen wrote:
>>>>
>>>>> After updating to xorg-x11-6.7.0-0.4, I get this error when starting
>>>>> X. X still starts, so I don't know whats the problem.