Bug 120989 - Can't find xfree86 rules file error message
Summary: Can't find xfree86 rules file error message
Status: CLOSED DUPLICATE of bug 121016
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-04-15 21:54 UTC by Dax Kelson
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2006-02-21 19:02:37 UTC


Attachments (Terms of Use)

Description Dax Kelson 2004-04-15 21:54:39 UTC
Description of problem:

When installing rawhide April 14 2004, the GUI starts up, but if I
shell back out to CTL-ALT-F1 I see the error message:

Can't find/load the xfree86 rules file (or something like that)

I'm sure it's related to the xorg change.

I didn't notice any ill effects during the install I could attribute
to this error message.

Comment 1 Jeremy Katz 2004-04-15 22:29:19 UTC
Bad setxkbmap, no cookie
[katzj@orodruin anaconda]$ setxkbmap -layout us -model pc104 -option ""
Couldn't find rules file (xfree86) 


Comment 2 Mike A. Harris 2004-04-16 02:46:20 UTC
Can you strace that?

Comment 3 Mike A. Harris 2004-04-16 03:41:30 UTC
This appears to be caused by the X server config file containing
an unnecessary XkbRules "xfree86" option.

Comment 4 Mike A. Harris 2004-04-19 19:17:11 UTC

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

Comment 5 Nicolas Zujev 2004-06-11 06:18:44 UTC
it's like a KDE and xOrg bug.
cause xOrg has rewrote rules files from xfree86* (XFree86) to xorg*

so to do it working  just make 2 links:
~ cd /etc/X11/xkb/rules
~ ln -s xorg.lst xfree86.lst
~ ln -s xorg.xml xfree86.xml

and restart the X server

but better, I think, to recompile KDE to work with new xorg* rules files

Comment 6 Red Hat Bugzilla 2006-02-21 19:02:37 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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