| Summary: | MX1000 is incorrectly configured with evdev | ||
|---|---|---|---|
| Product: | xorg | Reporter: | Jeremy Nickurak <freedesktop-bugs> |
| Component: | Input/evdev | Assignee: | Peter Hutterer <peter.hutterer> |
| Status: | RESOLVED NOTOURBUG | QA Contact: | Xorg Project Team <xorg-team> |
| Severity: | normal | ||
| Priority: | high | CC: | daniel, erik.andren, floam, freedesktop-bugs, jk |
| Version: | 7.1 (2006.05) | ||
| Hardware: | x86 (IA32) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Jeremy Nickurak
2006-01-12 17:54:38 UTC
Related to https://bugs.freedesktop.org/show_bug.cgi?id=5256 ? In the above linked bug, another user gets 'o' and 'p' keys under the same configuration. Under my dvorak keyboard, that's 'r' and 'l', so the fact that they stand for left and right may just be a weird coincidence. I only see the extre key events when the mouse isn't the core pointer. With 'CorePointer' instead of 'SendCoreEvents' it works fine. The extra 11 and 12 button events occur in both configuartions. Reassign to the new evdev maintainer. Any improvement with the new 1.1.1 release driver? I can't get recent xf86-input-evdev working with debian's build of xorg 7.0. Hopefully I can test this once 7.1 is packaged for debian. If it's supposed to be possibly to make 1.1.1 work without having to upgrade to 7.1 or recompile 7.0, I can try it earlier, but atm it just segfaults. I have the bluetooth version from the mx5000 and I don't have the extra-button press problem, but I have the reversed scroll problem. evdev 1.1.2: - Still has the cruise-control bug - Still reverses the left/right scroll - doesn't produce the keypress events anymore master still has reversed tilt for me also. Marking broken (status null/blank) bugs in xorg with no activity in a long time as fixed. Please reopen if you think it's necessary, but first do a search if a similar bug report is already filed and in a NEW/ASSIGNED state. These bugs do not currently show in most search results as they do not have any status. Sorry for this janitorial spam, you know where to send hate mails to when your inbox gets full of bugs you're subscribed to. *** Bug 7630 has been marked as a duplicate of this bug. *** Still present. Marking some duplicates. mass reassignment. Zephaniah isn't the maintainer anymore. No update for more than 12 months old, closing as WONTFIX. Please reopen if this is still an issue with the current release. Still an issue under xserver-xorg-input-evdev 2.0.99 git 20080912 (latest in ubuntu intrepid). If there's a newer version worth trying, please mark NEEDINFO and I'll test. evdev 2.1 has been released since, so that'd be the preferred one to test. See http://ftp.x.org/pub/individual/driver/ Please download http://people.freedesktop.org/~whot/evtest.c, compile it with "gcc -o evtest evtest.c" and then run it as root with "./evtest /dev/input/eventX" where X is the number for the device. You can get the number by looking at /proc/bus/input/devices. Hit all buttons that don't do what they should do and attach the output of evtest here. Please also describe for each button what the desired behaviour is. No response for 30 days. INVALID. Please reopen once the requested information has been provided. This behavior persists in evdev 2.2.5. As requested, here's an annotated evtest output: Clicking the cruise-control-up button produces the following, where it should be a press and release of the Up wheel button: Event: time 1268026127.353861, type 4 (Misc), code 4 (ScanCode), value 90007 Event: time 1268026127.353882, type 1 (Key), code 278 (BackBtn), value 1 Event: time 1268026127.353896, -------------- Report Sync ------------ Event: time 1268026127.369838, type 2 (Relative), code 8 (Wheel), value 1 Event: time 1268026127.369858, -------------- Report Sync ------------ Event: time 1268026127.465861, type 4 (Misc), code 4 (ScanCode), value 90007 Event: time 1268026127.465878, type 1 (Key), code 278 (BackBtn), value 0 Event: time 1268026127.465890, -------------- Report Sync ------------ Clicking the cruise-control-down button produces the following, where it should be a press and release of the Up wheel button: Event: time 1268026129.377860, type 4 (Misc), code 4 (ScanCode), value 90008 Event: time 1268026129.377882, type 1 (Key), code 279 (TaskBtn), value 1 Event: time 1268026129.377896, -------------- Report Sync ------------ Event: time 1268026129.401829, type 2 (Relative), code 8 (Wheel), value -1 Event: time 1268026129.401850, -------------- Report Sync ------------ Event: time 1268026129.537856, type 4 (Misc), code 4 (ScanCode), value 90008 Event: time 1268026129.537876, type 1 (Key), code 279 (TaskBtn), value 0 Event: time 1268026129.537888, -------------- Report Sync ------------ Clicking the wheel-left-tilt produces the following, where it should be a press and release of the left wheel button: Event: time 1268026131.521867, type 4 (Misc), code 4 (ScanCode), value 90009 Event: time 1268026131.521887, type 1 (Key), code 280 (?), value 1 Event: time 1268026131.521893, -------------- Report Sync ------------ Event: time 1268026131.537833, type 2 (Relative), code 6 (HWheel), value -1 Event: time 1268026131.537855, -------------- Report Sync ------------ Event: time 1268026131.609851, type 4 (Misc), code 4 (ScanCode), value 90009 Event: time 1268026131.609867, type 1 (Key), code 280 (?), value 0 Event: time 1268026131.609872, -------------- Report Sync ------------ Clicking the wheel-right-tilt produces the following, where it should be a press and release of the right wheel button: Event: time 1268026132.777866, type 4 (Misc), code 4 (ScanCode), value 9000a Event: time 1268026132.777883, type 1 (Key), code 281 (?), value 1 Event: time 1268026132.777888, -------------- Report Sync ------------ Event: time 1268026132.801849, type 2 (Relative), code 6 (HWheel), value 1 Event: time 1268026132.801871, -------------- Report Sync ------------ Event: time 1268026132.881868, type 4 (Misc), code 4 (ScanCode), value 9000a Event: time 1268026132.881887, type 1 (Key), code 281 (?), value 0 Event: time 1268026132.881891, -------------- Report Sync ------------ Note that each button press has a correct Wheel or HWheel event in between the incorrect press/release buttons for the secondary event. Note also that holding the button down will correctly repeat the respective Wheel or HWheel event. Possibly related to: http://bugzilla.kernel.org/show_bug.cgi?id=1786, reposting this information there. thanks for the update - this is a kernel issue though. We don't have hardware-specific hacks in evdev (one could say the whole point of evdev is to have hardware-specific hacks in the kernel) so we need to wait until the kernel bug is resolved. sorry. kernel bug as per comment 18 and 19. Closing. |
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.