Bug 380159 - Wayland: Scrolling with touchpad is choppy
Summary: Wayland: Scrolling with touchpad is choppy
Status: RESOLVED NOT A BUG
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: 5.9.5
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-24 19:13 UTC by Michael D
Modified: 2017-06-18 12:18 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael D 2017-05-24 19:13:28 UTC
Scrolling on Wayland is choppy unless, e.g., one sets in the GUI "mouse wheel scrolls by" to 1 line, rather than the default 3, for example. This is true for both gtk and qt(5) apps. I'm using an Elan touchpad.
Comment 1 Patrick Silva 2017-05-26 23:54:55 UTC
My elantech touchpad works fine on neon dev, Wayland session.
I use two fingers to scroll.
Comment 2 Michael D 2017-05-27 07:27:26 UTC
Is Neeon Dev using Plasma 5.10? And were any input changes made in 5.10? Is your scrolling experience *exactly the same* under Wayland and X11?
Comment 3 Patrick Silva 2017-05-27 17:42:38 UTC
Neon dev runs plasma 5.10.90 here.
Scrolling is a bit faster under Wayland.
Scrolling sometimes becomes choppy on Discover app under Wayland.
Comment 4 Michael D 2017-05-30 20:52:31 UTC
I'm now on 5.10.0 and scrolling is actually worse than it was on 5.9.5. It's so bad, I can't use wayland as my default session. I'm not sure what's going on, but touchpad scrolling behavior is completely different on wayland than it is on X.
Comment 5 Martin Flöser 2017-06-17 12:04:05 UTC
The setting is completely irrelevant for GTK applications. Thus I have to doubt that it has any influence.

This cannot be a bug in KWin as we only take the events from libinput and forward them to the applications. Thus it's either a problem in libinput or in the applications. Marking as invalid for kwin.
Comment 6 Michael D 2017-06-18 12:18:32 UTC
I guess it's an issue with libinput, since it's used in wayland but not X11 in Neon (as far as I'm aware).