| Summary: | No input devices work and then mapping doesn't work | ||||||
|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Dave Gilbert <freedesktop> | ||||
| Component: | Input/evdev | Assignee: | Peter Hutterer <peter.hutterer> | ||||
| Status: | RESOLVED INVALID | QA Contact: | Xorg Project Team <xorg-team> | ||||
| Severity: | major | ||||||
| Priority: | medium | CC: | edt | ||||
| Version: | unspecified | ||||||
| Hardware: | Other | ||||||
| OS: | Linux (All) | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
|
Description
Dave Gilbert
2010-04-02 08:00:22 UTC
I've got similar problems here.
Section "InputDevice"
Identifier "Keyboard0"
Driver "evdev
option "Device" "/dev/input/event0"
# option "CoreKeyboard"
option "XkbModel" "pc105"
option "XkbLayout" "ca"
option "XkbVariant" "fr"
Option "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection
My up and down keys do not work. Interestingly xev shows the correct keys pressed...
I am using gentoo with xorg 1.8
Also, synergy makes these keys work on the remote synergy client but not on the local machine running the server. Using the old kbd driver (1.4) bypasses the problem here - would be nice to be able to use evdev for keyboards though... Thanks to Sarvatt on #ubuntu-x for spotting I'd got an ancient package in my xorg-edgers installation; so for me that's fixed - but that leaves Ed's problem which had the same symptom as mine from the mapping. Ed: Perhaps you've got a mismatched package somewhere as well? Dave What specific package caused the problem? And what files did it contain? This install has been around a while its possible there is some crud that needs cleaning here too. Rebuild libX11 helped here. Now only the 'UP' key is failing. Interestingly xev shows no KeyPress event when up is pressed:
FocusOut event, serial 34, synthetic NO, window 0x1a00001,
mode NotifyGrab, detail NotifyAncestor
FocusIn event, serial 34, synthetic NO, window 0x1a00001,
mode NotifyUngrab, detail NotifyAncestor
KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 8 0 0 0 0 0 0 0 0 0 0 0 0 4294967168 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
KeyRelease event, serial 34, synthetic NO, window 0x1a00001,
root 0x108, subw 0x0, time 72962426, (281,42), root:(285,65),
state 0x0, keycode 111 (keysym 0xff52, Up), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
Ideas?
Looks like libXi needed to be updated to the latest (git) version too. All is working now here. can we close this bug then? there are some issues with keyboard handling that clients (namely metacity) don't handle well, so if you disable hotplugging but still use evdev, you're going to run into issues with different keymaps on the VCP and the physical device. We've covered the standard use-cases but some special ones cannot be handled easily. Dave - I guess the initial lack of devices may have to do with the switch to udev, just guessing though. In both cases, the problem turned out to be a miss match between packages (we talked on irc). Here libXi needed to be from git along with a few others. As far as I am concerned this can be closed. thanks, closing as invalid then, caused by some package mismatch. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.