Summary: | Input events show up as scroll events, not drag events | ||
---|---|---|---|
Product: | Wayland | Reporter: | Linus Torvalds <torvalds> |
Component: | libinput | Assignee: | Wayland bug list <wayland-bugs> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | benjamin.tissoires, peter.hutterer |
Version: | 1.5.0 | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
libinput-debug-events --berbose
evemu-record output |
Created attachment 129994 [details]
evemu-record output
Here is the output from evemu-record.
Note - not same gesture as the libinput-debug-events output, but similar: move mouse around to the window header, and try to drag the window around.
Alrighty, this is a kernel bug, INPUT_PROP_BUTTONPAD is missing. That causes libinput to be generally confused about things such as "is a finger used for clicking?". On a device with separate physical buttons, we can assume that two fingers on the touchpad are scrolling, hence the behaviour you're seeing. Unless you have a special edition of the XPS that I'm not aware of and that has the same touchpad as the old apple one-button touchpads from 2007, I'm punting this to Benjamin to fix the kernel patches. I've applied the fix from Benjamin Tissoires, and it is now commit 522214d9be9c ("Input: rmi4 - f30: detect INPUT_PROP_BUTTONPAD from the button count") in the kernel. Thanks. |
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.
Created attachment 129993 [details] libinput-debug-events --berbose My XPS 13 touchpad started acting up when switching to the RMI driver. Almost everything works, and I use 'tap-to-click' for things. But then when I want to drag things a longer distance, I will do a real full click with one finger, and then drag another finger to drag it. That used to work fine with the PS/2 emulation, but seems to not work with the touchpad in RMI mode. This is Fedora 24 with libinput-1.5.4-1.fc24.x86_64 and I'm attaching the output of libinput-debug-evnts --verbose as the attachement. Note how it goes from gesture state: GESTURE_STATE_UNKNOWN → GESTURE_STATE_SCROLL event16 POINTER_AXIS +2.98s vert 0.00 horiz 3.94* even though the button is pressed, which apparently shouldn't be the case. If there is anything else I can do, holler.