Bug 8131 - setxkbmap dislikes xf86config's configurations
setxkbmap dislikes xf86config's configurations
Product: Red Hat Linux
Classification: Retired
Component: XFree86 (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Preston Brown
Depends On:
  Show dependency treegraph
Reported: 2000-01-03 00:21 EST by David Baron
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-02-03 16:32:41 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Baron 2000-01-03 00:21:59 EST
Using a configuration generated by xf86config, setxkbmap gives an error
every time it is run that is something like (I don't want to go back to my
old configuration right now, but this is based on my memory, enhanced by
'strings `which setxkbmap`'):

  Couldn't interpret _XKB_RULES_NAMES property

The problem seems to be that xf86config generates a line at the end of the
keyboard section like:

      XkbKeymap   "xfree86(us)"

whereas Xconfigurator, in that same place, generates:

     XkbKeycodes     "xfree86"
     XkbTypes        "default"
     XkbCompat       "default"
     XkbSymbols      "us(pc101)"
     XkbGeometry     "pc"
     XkbRules        "xfree86"
     XkbModel        "pc101"
      XkbLayout       "us"

setxkbmap works like a charm when I change the first line (as generated by
xf86config) to the above 8 (as generated by Xconfigurator).
Comment 1 Preston Brown 2000-02-03 16:32:59 EST
don't use xf86config.  We don't support it.

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