Bug 94283

Summary:	two-finger scrolling delayed after keyboard use
Product:	Wayland	Reporter:	erusan
Component:	libinput	Assignee:	Wayland bug list <wayland-bugs>
Status:	RESOLVED NOTOURBUG	QA Contact:
Severity:	normal
Priority:	medium	CC:	peter.hutterer
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description erusan 2016-02-24 21:15:30 UTC

Keyboard use (whether typing, switching windows with alt+tab) causes a delay before two-finger scrolling works again.

Actions like moving the pointer and clicking work immediately.

This does not appear related to a movement threshold, because wildly exaggerated movements fail to cause two-finger scroll to register.

Delay seems to be at least one full second, perhaps longer.

Comment 1 Peter Hutterer 2016-02-25 01:45:44 UTC

weird. the timeout for dwt after multiple key presses is 500ms, so any timeout should not be longer than that. There is nothing specific about scrolling here, if movement works then gestures should work too.

Please run libinput-debug-events --verbose and try to reproduce this issue, then attach the output here. Maybe there's some bug in the state transition you're triggering.

The only legitimate case where this may be triggered is if you put the first finger down while still typing, stop typing and then put the second finger down to scroll. The first finger will be identified as palm and continue to be identified as such - you'd get pointer motion but no 2fg scrolling.

Comment 2 erusan 2016-02-25 02:56:26 UTC

Whoops! Forgive the oversight -- the observed behavior did not occur in a session running libinput. libinput is indeed working as expected.

Apologies for the sloppy bug report.

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.