Bug 100416

Summary:	Issues with 1.6 version on Dell Precision 5510
Product:	Wayland	Reporter:	Ben Le Corre <ben.lecorre>
Component:	libinput	Assignee:	Wayland bug list <wayland-bugs>
Status:	RESOLVED MOVED	QA Contact:
Severity:	normal
Priority:	medium	CC:	peter.hutterer
Version:	unspecified
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Ben Le Corre 2017-03-27 14:29:55 UTC

Hello,
I have several issues with libinput since version 1.6, the first one with acceleration, and the second one with tapping sometimes not taken into account (I tested the version 1.6 for few days, and then the versions 1.6.1, 1.6.2, 1.6.3 and the version 1.7, and none of them solved my issues, but I have to say that the last one is improving a bit the situation, the pointer is way less slow).
Since I did not have much time to debug this, I downgraded to the version 1.5.4 which btw was really perfect, way better than synaptics.
But since few days, two fingers scrolling is really lagging, especially on Firefox, so I took some time to try to fix these issues. 
As I understand, there is no way to configure in detail libinput in Gnome on Wayland (e.g. acceleration). Moreover, my scrolling issue is most probably linked to the gnome wayland composer (Cf. https://bugs.freedesktop.org/show_bug.cgi?id=96312 I have thousands of these messages in my logs).
So for these reasons, I decided to leave wayland, at least for several weeks/months, and go back to X11.
But since libinput seems very customizable on X11, I was wondering if there was a way to use the last version of libinput (1.7) with the same parameters as the version 1.5.4, instead of using the version 1.5.4? When possible I try to run the last versions of the software I use.
PS: I'm running Gnome on Arch on a Dell Precision 5510 developer edition (a linux version of the XPS15).
Rgrds,
Ben

Comment 1 Peter Hutterer 2017-04-03 01:24:53 UTC

if i read this correctly, you have three issues: acceleration, tapping and laggy scrolling. The last one is most likely an issue in the compositor, the other two are legitimate bugs. Please file a separate one for each of them though, it's too hard to track multiple issues in the same bug . I'm closing this bug as MOVED for now, please file the two extra bugs, one for each issue (there are a couple of acceleration bugs already open, you could just tack onto those).

Also, make sure you either cc me or assign it to me, that way I see it quicker ;)

Comment 2 Ben Le Corre 2017-04-04 13:22:41 UTC

Hello, sorry if I was not very clear, my goal here was to not to create another bug regarding libinput, wayland and Dell laptops (I'm already following some of these bugs reports). 
My message was really focused on X11, I just wanted to know if there was a way to make it usable on Dell laptops since libinput on X11 can be configured with more details. 
But after a lot of tests, the answer seems to be no. So ok to close this, I will stick to version 1.5.4, hoping the next versions will get back to 1.5.4 behavior's ;)

Comment 3 Peter Hutterer 2017-04-05 00:53:57 UTC

(In reply to Ben Le Corre from comment #2)
> But after a lot of tests, the answer seems to be no. So ok to close this, I
> will stick to version 1.5.4, hoping the next versions will get back to 1.5.4
> behavior's ;)

without a bug to analyse, this won't happen except maybe by accident, we really need the data so we can work with it.

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.