https://bugzilla.redhat.com/show_bug.cgi?id=1049304
Peter Hutterer <peter.hutterer(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |NOTABUG
Last Closed|2014-10-15 03:42:59 |2015-11-12 16:13:40
--- Comment #4 from Peter Hutterer <peter.hutterer(a)redhat.com> ---
(In reply to Zbigniew Jędrzejewski-Szmek from comment #1)
This list is read from /usr/share/X11/xkb/rules/base.lst.
for correctness, you should read evdev.lst though the two files have the same
content.
Karel - do you have some xorg.conf.d snippets? can you attach your Xorg.log? we
switched evdev to pc105 a while ago in the server and the evdev driver, so I'm
wondering where this setting comes from.
Aside from that, it's not really a bug, the setxkbmap output is not
trustworthy. The RMLVO keyboard specification is just the entry point to switch
to the actual format that xkb uses, see [1] for more details.
The evdev rule has a couple of catchalls, look at
/usr/share/X11/xkb/rules/evdev in e.g. the !model = keycodes section. The last
line there is:
* = evdev
this means "any model maps to the evdev keycodes". You can run setxkbmap -model
"foo" and now you've set the model "foo" even though it
doesn't exist. You got
the evdev keycodes and triggered a couple of other generic matches, but
specifying foo neither helped nor made it worse. The same applies to evdev -
there is no real evdev model.
[1]
http://who-t.blogspot.com.au/2008/09/rmlvo-keyboard-configuration.html
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug
https://bugzilla.redhat.com/token.cgi?t=GWATS56c5n&a=cc_unsubscribe