Bug 98008 - Cannot start two-finger scroll from bottom area of touchpad
Summary: Cannot start two-finger scroll from bottom area of touchpad
Status: RESOLVED NOTOURBUG
Alias: None
Product: Wayland
Classification: Unclassified
Component: libinput (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Wayland bug list
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-01 19:08 UTC by buggit
Modified: 2016-10-04 04:50 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
output of xinput list-props (1.23 KB, text/plain)
2016-10-01 19:08 UTC, buggit
Details

Description buggit 2016-10-01 19:08:30 UTC
Created attachment 126948 [details]
output of xinput list-props

I cannot start a two-finger scroll action from the bottom ~30% of the touchpad, it is interpreted as an ordinary cursor move instead. I can start a scroll above the bottom area and continue scrolling into it but I cannot start in it. It works correctly in Windows.

I am using fedora 24, 4.7.4. Problem exists in both Wayland & X (xorg-x11-drv-libinput 0.19.0).

My touchpad is a clickpad, the entire bottom area can be depressed like a button and I assume left-click/right-click is software-defined. I tried changing "ClickMethod" to each of the available options but it seemed to have no effect.

I have provided the output of 'xinput list-props'. I can provide other info if wanted. To determine whether this can be fixed by libinput, etc.

see http://askubuntu.com/questions/706369/two-finger-scrolling-and-two-finger-pointer-moving-if-1-finger-is-in-lower-20 for an alternative description of this issue
Comment 1 buggit 2016-10-04 04:50:36 UTC
OK it isn't a problem with libinput. I found that my libinput configuration options applied correctly after a suspend. Learned of libinput-debug-events and found the device 'ALP000F:00 044E:120C' was generating events before suspend, 'AlpsPS/2 ALPS GlidePoint' with correct config applied afterwards. Workaround for my issue was to blacklist i2c_designware_core to basically disable the first device. Not sure now where the bug actually lies, hope this at least helps anyone with this annoying issue find a workaround.

see also...
http://forums.fedoraforum.org/showthread.php?t=300522 https://ask.fedoraproject.org/en/question/84372/touchpad-doesnt-work-until-after-suspend/


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.