Bug 185943 - evdev driver wrong keyboard mapping
evdev driver wrong keyboard mapping
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-evdev (Show other bugs)
5
All Linux
medium Severity medium
: ---
: ---
Assigned To: X/OpenGL Maintenance List
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-03-20 05:37 EST by Jan "Yenya" Kasprzak
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-03-20 14:44:38 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
FreeDesktop.org 3912 None None None Never
FreeDesktop.org 5696 None None None Never

  None (edit)
Description Jan "Yenya" Kasprzak 2006-03-20 05:37:15 EST
Description of problem:
When using a keyboard handled by "evdev" driver (which is needed on multi-seat
computers), the keyboard has wrong layout (the keycodes sent by some keys are
different than when using the "kbd" driver, so that the default XKB maps do not
work).

Version-Release number of selected component (if applicable):
xorg-x11-drv-evdev-1.0.0.5-1.2

How reproducible:
100%

Steps to Reproduce:
1. Use the following keyboard section in the xorg.conf file:
Section "InputDevice"
        Identifier  "PS2Keyboard"
#       Driver      "kbd"
#       Option      "Protocol" "standard"
        Driver      "evdev"
        Option      "Device" "/dev/input/keyboard_first" # or whatever your
keyboard is
EndSection
2. run xev from terminal.
3. switch keyboard focus to xev
4. press the "down arrow" key on the "inverted T" part of the keyboard
  
Actual results:
xev reports the "Prior" keysym

Expected results:
xev should report the "Down" keysym

Additional info:
This is a problem of special keys (modifiers, arrows, edit keys, etc.). As far
as I can see the letters, F1-F12 keys, and numbers are OK). I have been able to
make xev report the correct keys with the following xmodmap, but it still has
some problems (maybe with XKB settings or whatever) - even after this
modification my window manager cannot recognize the Ctrl-Alt-DownArrow key combo
to switch to another virtual desktop (I use 3x3 layout).

keycode 50 = Shift_L
keycode 133 = Super_L
keycode 108 = Alt_R
keycode 134 = Super_L
keycode 135 = Menu
keycode 105 = Control_R
keycode 107 = Print
keycode 127 = Pause
keycode 118 = Insert
keycode 119 = Delete
keycode 110 = Home
keycode 115 = End
keycode 112 = Prior
keycode 117 = Next
keycode 113 = Left
keycode 111 = Up
keycode 116 = Down
keycode 114 = Right
keycode 104 = KP_Enter
keycode 106 = KP_Divide
Comment 1 Mike A. Harris 2006-03-20 14:44:38 EST
The evdev driver does not have any xkb support at all.
Comment 2 Jan "Yenya" Kasprzak 2006-03-20 15:05:13 EST
OK, then - forget the XKB part. However, it should report the keysyms as expected.
Comment 3 Jan "Yenya" Kasprzak 2006-03-20 15:13:57 EST
For further referece, I have added two references to the freedesktop.org
bugzilla, which try to solve this problem.
Comment 4 Mike A. Harris 2006-03-20 19:05:55 EST
The information provided in the referenced upstream bugzilla reports
indicates that this is new feature support, which is developmental code
which is still being developed right now, and is in a state of flux.
There does not yet appear to be a new "stable" evdev driver release which
contains this support as of yet.

In the mean time, users are encouraged to work with the upstream X.Org
community to test and provide feedback on the new support.  Please use the
xorg@lists.freedesktop.org mailing list to discuss any problems encountered
with the upstream developers, and http://bugs.freedesktop.org to report
any bugs/problems encountered with the experimental code.

Once there is a new upstream X.Org release of the evdev driver which contains
the new feature support, we will review it for consideration in a future
release of Fedora Core, and may also consider it as a candidate for a
driver update to Fedora Core 5.

Thanks for testing.

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