Bug 98535

Summary: libinput touchpad acceleration tracker bug
Product: Wayland Reporter: Peter Hutterer <peter.hutterer>
Component: libinputAssignee: Wayland bug list <wayland-bugs>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: medium CC: lukebenes, nate, peter.hutterer
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Bug Depends on: 90735, 94986, 96848, 97355, 98556, 98835, 98839, 98845, 100752, 101139, 101140, 101428    
Bug Blocks: 99000, 99695    

Description Peter Hutterer 2016-11-01 21:36:35 UTC
Tracker bug for libinput touchpad acceleration. Please do not comment here, file a new bug with your laptop's model number and make it block this one here.
Comment 1 Peter Hutterer 2016-12-21 03:09:20 UTC
A set of touchpad acceleration improvements has landed. They fix a couple of things, most notably the problematic mouse movement at low speeds.

commit acbbe882a2938183da7f4169a289e3589553374c
Merge: 0bd94a1 f4ff619
Author: Peter Hutterer <peter.hutterer@who-t.net>
Date:   Wed Dec 21 11:34:37 2016 +1000

    Merge branch 'touchpad-pointer-accel-revamp'


There's a writeup of the changes here:
https://who-t.blogspot.com.au/2016/12/libinput-touchpad-pointer-acceleration.html

This makes the touchpad a lot more usable and while there are some remaining issues, these should probably be tracked in a different bug. So I'm closing this one as fixed for now.
Comment 2 Peter Hutterer 2017-05-19 05:05:46 UTC
Reopening, because we still get complaints
Comment 3 Peter Hutterer 2018-05-25 05:46:59 UTC
New touchpad accel code merged as part of #101139. That's probably the last time I'll touch that code given that the feedback is limited to people complaining but no-one working on it and only very very few people bothering to test anything.  So closing, this is fixed now.
Comment 4 Nate Graham 2018-05-25 14:43:32 UTC
It's vastly better for me now, FWIW. Thanks for your hard work on this. It's much appreciated.

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.