Bug 1246433 - Recent updates have broken two fingers scroll support for touchpad
Summary: Recent updates have broken two fingers scroll support for touchpad
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: libinput
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Hutterer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-24 10:19 UTC by Germano Massullo
Modified: 2015-08-16 10:32 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-16 10:32:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Germano Massullo 2015-07-24 10:19:46 UTC
Description of problem:
Recent updates have broken two fingers scroll support for touchpad. I tried also on other existing users on my laptop.
I tried disabling and re-enabling again the proper option in system settings, but it did not help.

Version-Release number of selected component (if applicable):
plasma-systemsettings-5.3.2-1.fc22.x86_64

Comment 1 Peter Hutterer 2015-07-26 23:15:19 UTC
could be fallout fron the thumb detection, see bug 1246093. If so, does https://admin.fedoraproject.org/updates/libinput-0.20.0-3.fc22 fix it?

Comment 2 Germano Massullo 2015-07-27 10:11:47 UTC
(In reply to Peter Hutterer from comment #1)
> could be fallout fron the thumb detection, see bug 1246093. If so, does
> https://admin.fedoraproject.org/updates/libinput-0.20.0-3.fc22 fix it?

No, it does not fix it

Comment 3 Peter Hutterer 2015-07-27 22:46:10 UTC
Most likely a dupe of bug 1246868, the distance between the fingers matters. Could it be that you're holding the fingers more than 30mm apart? See https://bugzilla.redhat.com/show_bug.cgi?id=1246868#c7 for more details. If that's not it, please attach an evemu-recording of a scroll sequence that doesn't work.

Comment 4 Germano Massullo 2015-08-16 10:32:36 UTC
A new Fedpra update fixed the problem


Note You need to log in before you can comment on or make changes to this bug.