After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 762767 - Kinetic scrolling not stopped by leaving finger with libinput under X11
Kinetic scrolling not stopped by leaving finger with libinput under X11
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: X11
3.18.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2016-02-27 11:27 UTC by Milan Bouchet-Valat
Modified: 2018-04-15 00:19 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Bouchet-Valat 2016-02-27 11:27:21 UTC 
When using vertical kinetic scrolling with libinput on my Synaptics touchpad (with one finger, on the side), leaving the finger on the touchpad without moving does not stop the scrolling at all. Also, doing a finger move in the reverse direction to stop the scrolling has a small delay. Or at least a larger part of the finger move has no effect on the pointer.

After checking with libinput developers [1], it appears that 0/0 scroll events are correctly sent, so that this is a bug in GTK. Yet, in Bug 756729 it is said that this currently works under X11.

This is on Fedora 23, GTK 3.18.7-2.


1: https://bugs.freedesktop.org/show_bug.cgi?id=93923
Comment 1 Matthias Clasen 2018-02-10 05:02:50 UTC 
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 2 Matthias Clasen 2018-04-15 00:19:10 UTC 
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new