Description of problem: It appears that the touchpad tap-and-drag behavior in libinput is not configurable. In the old synaptics driver and Windows, releasing your finger after a tap-and-drag gesture released the cursor button immediately. The new libinput Version-Release number of selected component (if applicable): libinput-0.15.0-1.fc22.x86_64 How reproducible: Steps to Reproduce: 1. Double tap and hold 2. Move finger to desired position 3. Release Actual results: Cursor button stays in pressed position until a timeout value. Expected results: Cursor button is released immediately if configured. Additional info: https://bugs.freedesktop.org/show_bug.cgi?id=90255 https://bugzilla.redhat.com/show_bug.cgi?id=1181565
The description here is a bit off but I can overally confirm that we have a bug here. Documentation is here: http://wayland.freedesktop.org/libinput/doc/latest/tapping.html It say's that when you want to tap-drag something, you have to do a second tap after dragging, to end the dragging. But that second tap to cancel dragging is not working. In any case this new feature seems akwardly implemented, it should be left for the user to choose how they want the touch gestures to work.
(In reply to Veske from comment #1) > The description here is a bit off but I can overally confirm that we have a > bug here. > > Documentation is here: > http://wayland.freedesktop.org/libinput/doc/latest/tapping.html > > It say's that when you want to tap-drag something, you have to do a second > tap after dragging, to end the dragging. But that second tap to cancel > dragging is not working. that's the documentation for current git master, the feature was merged after 0.15 which is the one in F22 atm. 0.16 should be out next week, I hope. > In any case this new feature seems akwardly implemented, it should be left > for the user to choose how they want the touch gestures to work. every configuration option ends up in a combinatorial explosion of test case. and we'd honestly rather provide behaviour that we know works than a bunch of config options that have undefined interactions.
libinput-0.15.0-4.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/libinput-0.15.0-4.fc22
(In reply to Peter Hutterer from comment #2) > (In reply to Veske from comment #1) > > The description here is a bit off but I can overally confirm that we have a > > bug here. > > > > Documentation is here: > > http://wayland.freedesktop.org/libinput/doc/latest/tapping.html > > > > It say's that when you want to tap-drag something, you have to do a second > > tap after dragging, to end the dragging. But that second tap to cancel > > dragging is not working. > > that's the documentation for current git master, the feature was merged > after 0.15 which is the one in F22 atm. 0.16 should be out next week, I hope. > > > In any case this new feature seems akwardly implemented, it should be left > > for the user to choose how they want the touch gestures to work. > > every configuration option ends up in a combinatorial explosion of test > case. and we'd honestly rather provide behaviour that we know works than a > bunch of config options that have undefined interactions. That's fine, but the new behavior is a departure what most users are used to. I should have written the description better, but I'm just asking for a customizable timeout value. This would allow users to preserve the old behavior.
Gave the new Fedora 22 to a couple of tech illeterate people, they took the tap-to-drag new behaviour as something that was completely broken. I don't think that new people should be forced to learn new ways to handle the most basic tasks in computing.
Package libinput-0.15.0-4.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libinput-0.15.0-4.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-9063/libinput-0.15.0-4.fc22 then log in and leave karma (feedback).
Thank you. 0.15.0-4 corrects the behavior of -tap-to-release-.
libinput-0.16.0-3.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/libinput-0.16.0-3.fc22
libinput-0.16.0-4.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/libinput-0.16.0-4.fc22
libinput-0.15.0-4.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
Linked fix does not fix this issue.
libinput-0.16.0-3.fc22 should fix it. it's still not configurable but the timeout is now short enough that it shouldn't matter.
libinput-0.17.0-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/libinput-0.17.0-1.fc22
*** Bug 1227990 has been marked as a duplicate of this bug. ***
*** Bug 1226529 has been marked as a duplicate of this bug. ***
The timeout is still pretty noticeable - around a second.
Package libinput-0.17.0-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libinput-0.17.0-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-9555/libinput-0.17.0-1.fc22 then log in and leave karma (feedback).
I used exactly this package to test. Unfortunately the timeout is still noticeable. That's very strange option to have this timeout at the first place...
libinput-0.17.0-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
The timeout is still noticeable with libinput-0.17.0-1.fc22
The issue is better now, but still not released *immediately*.
Yaroslav: the timeout is still there and will always be noticeable (especially when you know what to look for). It's down to 300ms now though which should be significantly less invasive. As for why it is there: http://wayland.freedesktop.org/libinput/doc/latest/tapping.html picture d), to be able to lift and continue with the tap. If you want to release the drag immediately you can simply tap one more time (picture f)
Thanks for the explanation. Will wait for this option to be configurable (if it is planned at all). Thanks.