| Summary: | kernel: touchpad jump (libinput 1.9.3) Lenovo R61 | ||
|---|---|---|---|
| Product: | Wayland | Reporter: | Dave <davefreitag> |
| Component: | libinput | Assignee: | Wayland bug list <wayland-bugs> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | CC: | benjamin.tissoires, peter.hutterer |
| Version: | unspecified | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
evemu-record capture of the event
dmesg output |
||
|
Description
Dave
2018-01-27 18:46:26 UTC
Attach a dmesg please and the output of hid-record for the device, thanks. Created attachment 137157 [details]
dmesg output
Dmesg output attached. I tried using hid-recorder against the input device, but it just returns an error. ``` # hid-recorder /dev/input/event4 D: 0 HIDIOCGRDESCSIZE: Invalid argument Unable to open device: Invalid argument No events where recorded. ``` Everything I've seen online and in the man pages indicates it should be recording a /dev/hidraw<x> device, but I don't have any hidraw devices anywhere under /dev. Is there something I need to do to enable those devices? seems similar to the bug I just reported https://bugs.freedesktop.org/show_bug.cgi?id=105022 benjamin, any comments? (In reply to Dave from comment #3) > Dmesg output attached. I tried using hid-recorder against the input device, > but it just returns an error. > > ``` > # hid-recorder /dev/input/event4 > D: 0 > HIDIOCGRDESCSIZE: Invalid argument > Unable to open device: Invalid argument > > No events where recorded. > ``` > > Everything I've seen online and in the man pages indicates it should be > recording a /dev/hidraw<x> device, but I don't have any hidraw devices > anywhere under /dev. Is there something I need to do to enable those devices? Well, your touchpad is using PS/2 so no it's normal you do not have any hidraw node. The dmesg shows that your touchpad is ps2 only, so there won't be much we can do in the kernel if the evemu-record. Peter if you can pinpoint where the jump happens in the evemu-file I might be able to tell if if this is fixable in the kernel or not. sorry, should've checked myself first. Jump happens on single-finger to double-finger change, see E: 0.703993 0003 0000 2457 # EV_ABS / ABS_X 2457 E: 0.703993 0003 0001 2527 # EV_ABS / ABS_Y 2527 E: 0.703993 0003 001c 0005 # EV_ABS / ABS_TOOL_WIDTH 5 E: 0.703993 0001 0145 0000 # EV_KEY / BTN_TOOL_FINGER 0 E: 0.703993 0001 014d 0001 # EV_KEY / BTN_TOOL_DOUBLETAP 1 E: 0.703993 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +10ms E: 0.716439 0003 0000 2525 # EV_ABS / ABS_X 2525 E: 0.716439 0003 0001 5159 # EV_ABS / ABS_Y 5159 E: 0.716439 0003 001c 0010 # EV_ABS / ABS_TOOL_WIDTH 10 E: 0.716439 0001 0145 0001 # EV_KEY / BTN_TOOL_FINGER 1 E: 0.716439 0001 014d 0000 # EV_KEY / BTN_TOOL_DOUBLETAP 0 E: 0.716439 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +13ms E: 0.729451 0003 0000 2639 # EV_ABS / ABS_X 2639 E: 0.729451 0003 0001 5132 # EV_ABS / ABS_Y 5132 E: 0.729451 0003 001c 0008 # EV_ABS / ABS_TOOL_WIDTH 8 E: 0.729451 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +13ms Needs an axis range fix too, still using the traditional made-up synaptics ranges and 5132 is quite a bit out of that... Anyway, I noticed this is a touchpad from 2007. We have some code in place to ignore jumps on finger count changes and that should/may work with this touchpad but tbh, I don't have any spare time to invest in hw that's 10 years old. Given that we notice the jump and discard it, the worst bit right now is the error message, right? So I'll just do the jedi-wave, tell you this is not the error message you're looking for and close this as WONTFIX. Sorry. |
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.