Bug 100696 - libinput 1.7 multitouch broken after update for elantech
Summary: libinput 1.7 multitouch broken after update for elantech
Status: RESOLVED DUPLICATE of bug 100463
Alias: None
Product: Wayland
Classification: Unclassified
Component: libinput (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Wayland bug list
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-16 18:36 UTC by Craig
Modified: 2017-04-27 06:02 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
xinput list-props output (1.60 KB, text/plain)
2017-04-16 18:36 UTC, Craig
Details
modalias info (219 bytes, text/plain)
2017-04-16 18:36 UTC, Craig
Details
udevadm recording of issues (509 bytes, text/plain)
2017-04-16 18:37 UTC, Craig
Details
evemu recording of issues (1.34 MB, text/plain)
2017-04-16 18:37 UTC, Craig
Details

Description Craig 2017-04-16 18:36:22 UTC
Created attachment 130862 [details]
xinput list-props output

Hey guys, after 1.7 update my touchpad become extremely frustrating to use. Running Arch Linux the latest updates received libinput 1.7 and lots of issues, all having to do with multitouch capabilities/detection.

Two finger scrolling: 50-75% of time it didn't trigger and just moves the mouse, I have to really tap both at the EXACT same time and HARD to get it to detect and even then it can still be hit/miss. This is a killer for me and is forcing me to downgrade (about to after getting the necessary info of course) - maybe it has something to do with pressure or just multitouch in general? But it's very bad

Multi-touch in general: For example, I click on the X button to close a window then change my mind, I can't move the cursor with my other finger to NOT click if you know what I mean. While pressing the button I cannot move the cursor with my other finger at all. If my second finger (used for moving cursor) is already on the pad when I click to close I can move it and sometimes I can if I push hard enough but it seems to be worst when clicking and then putting finger down trying to move, this one maybe just something to do with pressure but no idea

MSI GS63VR Stealth Pro 4k Laptop (228US)
Touchpad - buttons are built into the touchpad/same pad but physical clicks underneath if you know what I mean/all one pad

I've attached all the requested info including the evemu capture showing me trying to scroll up/down multiple times with two-fingers and it missing registering multiple times/just moving the cursor. Also tried closing a window then scrolling the mouse away to NOT close it and did not move.

Let me know ANY other info I can provide to help, loved libinput thus far but this update was a killer haha, running KDE Plasma (X with xf86 libinput 0.25)

Appears I can't add more than one attachment at once so will add separately
Comment 1 Craig 2017-04-16 18:36:58 UTC
Created attachment 130863 [details]
modalias info
Comment 2 Craig 2017-04-16 18:37:27 UTC
Created attachment 130864 [details]
udevadm recording of issues
Comment 3 Craig 2017-04-16 18:37:51 UTC
Created attachment 130865 [details]
evemu recording of issues
Comment 4 Craig 2017-04-16 18:38:21 UTC
Comment on attachment 130864 [details]
udevadm recording of issues

mistyped the description for udevadm its not a recording of course :P just the info per standard info provided
Comment 5 aun 2017-04-19 07:58:48 UTC
I assume this could be the same issue like https://bugs.freedesktop.org/show_bug.cgi?id=100463. You can find a fix to apply for testing in that bug report.
Comment 6 Peter Hutterer 2017-04-24 05:26:47 UTC
I agree, this sounds like the pressure values are off, please check with bug 100463 and also have a look at this series here: https://lists.freedesktop.org/archives/wayland-devel/2017-April/033930.html

I haven't been able to review that yet, but it's a start :)
Comment 7 Peter Hutterer 2017-04-27 06:02:47 UTC
marking as dupe for now, we can de-duplicate when the other bug is fixed and it turned out to be a different issue.

*** This bug has been marked as a duplicate of bug 100463 ***


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.