Can you specify what you mean by "imprecise"?

There's a lack of accuracy, i am not able to precisely point objects, and no matter the speed i configure it, it's pointer either moves too fast or too slow. Sorry for the lack of technical terms but it's kind difficult to describe it as it's a more of a feel.

I can confirm that it happens. And it's bad.

Currently running Arch, using the latest libinput driver available. I've run into this with any distro that uses libinput by default.

The cursor is either too slow or too fast.

It's impossible to move it just a little bit. Any movement makes it run faster than it should. Reducing the acceleration to some negative number just makes it go slow on wide movements. On small, precise movements it's always too fast.

There's currently no support for some highly important settings present in the Synaptics driver, such as:

* FingerLow and FingerHigh pressure configuration, which can correct accidental clicks in several touchpads (it's impossible to work without setting those to a value higher than the default. The computers also displays erratic behavior on Windows but FingerLow and FingerHigh make it possible to fix this on Linux)
* Minimum cursor speed and maximum cursor speed: these are much more relatable to this bug and need to be implemented ASAP. The current lack of ability to set these values is what makes the touchpad feel extremely imprecise.

I can provide any kind of info that should be needed to fix this.

My touchpad is from an Asus UX360CA, identifies itself as ELAN1200. And my biggest issue is that an initial touch on the touchpad is recognized as click, something I could see with libinput-debug-events.

libinput-list-devices has this output:

Device:           ELAN1200:00 04F3:301A Touchpad
Kernel:           /dev/input/event14
Group:            5
Seat:             seat0, default
Size:             103.23x70.90mm
Capabilities:     pointer 
Tap-to-click:     disabled
Tap-and-drag:     enabled
Tap drag lock:    disabled
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: disabled
Calibration:      n/a
Scroll methods:   *two-finger edge 
Click methods:    *button-areas clickfinger 
Disable-w-typing: enabled
Accel profiles:   none
Rotation:         n/a

And while it says that tap-to-click is disabled it isn't via this Xorg config:

Section "InputClass"
        Identifier "touchpad"
        MatchIsTouchpad "yes"
        MatchDevicePath "/dev/input/event14"
        Option "Tapping" "yes"
        Option "NaturalScrolling" "yes"
        Option "DisableWhileTyping" "yes"
EndSection

(In reply to Thomas Bohn from comment #4)

> Section "InputClass"
>         MatchDevicePath "/dev/input/event14"
> EndSection

My issue which I thought was connected to the one describe in the bug was actually the result of a bad config file. Sorry.

Which doesn't mean I didn't experience the bug, I did, and the rest happened while I was trying to fix the issue.

Today, I got xf86-input-libinput 0.20 and since then my touchpad reacts much better and nicer then before, and the symptoms describe here are no longer present. Maybe the others could try and and comment about their experiences.

Yes, after xf86-input-libinput was upgraded to 0.20, it's behaviour improved a lot, i've been using for a couple of hours by now and i have no more complaints.

I upgraded to 0.20 a few days ago and disabled the synaptics drivers. I can confirm I'm using libinput now and tought it got better, it's still to imprecise for me. Nowhere near the precision I get on the synaptics driver. Since libinput doesn't expose the settings I would need to change for it to feel alright (namely, Noise Cancellation, FingerLow and FingerHigh, MinSpeed and MaxSpeed), I went back to using synaptics. IMHO libinput can't be considered ready to replace the synaptics touchpad driver while it doesn't expose comparable configuration options for basic functions like these.

(In reply to leosanvieira from comment #7)
> Yes, after xf86-input-libinput was upgraded to 0.20, it's behaviour improved
> a lot, i've been using for a couple of hours by now and i have no more
> complaints.

that's... odd. I can't remember any touchpad pointer accel code going in. but glad it works now :)

(In reply to André Brait from comment #8)
> I upgraded to 0.20 a few days ago and disabled the synaptics drivers. I can
> confirm I'm using libinput now and tought it got better, it's still to
> imprecise for me. Nowhere near the precision I get on the synaptics driver.
> Since libinput doesn't expose the settings I would need to change for it to
> feel alright (namely, Noise Cancellation, FingerLow and FingerHigh, MinSpeed
> and MaxSpeed), I went back to using synaptics. IMHO libinput can't be
> considered ready to replace the synaptics touchpad driver while it doesn't
> expose comparable configuration options for basic functions like these.

https://who-t.blogspot.com.au/2016/09/synaptics-pointer-acceleration.html
the configuration options are mostly random number generators, so for obvious reasons I don't want them in libinput. there are still rough plans to investigate why things are different, but I don't have enough data yet.

Just to be clear, although i've said it has improved a lot, that only means that now it's good enough. The pointer speed is still faster than i'd like it to be but now i can use it normally and it behaves much like when i'm using windows, but even so i went back to synaptics, because i still think it works better.

(In reply to Peter Hutterer from comment #9)
> (In reply to leosanvieira from comment #7)
> > Yes, after xf86-input-libinput was upgraded to 0.20, it's behaviour improved
> > a lot, i've been using for a couple of hours by now and i have no more
> > complaints.
> 
> that's... odd. I can't remember any touchpad pointer accel code going in.
> but glad it works now :)
> 
> (In reply to André Brait from comment #8)
> > I upgraded to 0.20 a few days ago and disabled the synaptics drivers. I can
> > confirm I'm using libinput now and tought it got better, it's still to
> > imprecise for me. Nowhere near the precision I get on the synaptics driver.
> > Since libinput doesn't expose the settings I would need to change for it to
> > feel alright (namely, Noise Cancellation, FingerLow and FingerHigh, MinSpeed
> > and MaxSpeed), I went back to using synaptics. IMHO libinput can't be
> > considered ready to replace the synaptics touchpad driver while it doesn't
> > expose comparable configuration options for basic functions like these.
> 
> https://who-t.blogspot.com.au/2016/09/synaptics-pointer-acceleration.html
> the configuration options are mostly random number generators, so for
> obvious reasons I don't want them in libinput. there are still rough plans
> to investigate why things are different, but I don't have enough data yet.

Can I provide any information that would help?

> Can I provide any information that would help?

yes, but I'm still trying to figure out what exactly to collect so I have reliable data sets. a few more days, sorry

Ok, one request here so I do at least some evaluation:
https://lists.fedoraproject.org/archives/list/desktop@lists.fedoraproject.org/thread/CUW3IGXUEYATA7GNZMSF5TV5MSO2AUKV/
The attachment will likely be too big for bugzilla, so please put it somewhere else and send me the link.

Created attachment 127918 [details]
Touchpad recording

Comment on attachment 127918 [details]
Touchpad recording

Here's the recording as asked, i hope it's enough. Feel free to ask me if you need anything else.

follow-up questions: do you use tapping? do you use clickfinger or software button areas for physical clicks? and which scroll method do you use? twofinger or edge?

I use tapping, two buttons software button areas for physical clicks and for scrolling, i use the two finger method.

See bug 98535, please try libinput master and report back whether this improves things. Thanks

Yes, it's improved again, very much usable now but still a bit imprecise with small movements like when selecting text, for example.

Just so you known, i installed Arch Linux aur git packages libinput-git and xf86-input-libinput-git so i could try it with X and Wayland and had the same results with both.

I am experience this issue aswell (Have an Elantech Touchpad in an Acer CB3-431 laptop)


With Synaptic driver I can circle my cursor around in a very small circle, around a character like'V' on the screen for example. With Libinput I can't, it ends up being a very messed up circle. 

Using my touchpad with libinput just doesn't feel right, it makes using my laptop feel unstable, I find myself going to back to X even though I want to be in Wayland very badly.

I'm running Arch linux and can try and test any changes that are made or perform tests. Let me know. Thanks for all the hard work that you do.

(In reply to Mike weiss from comment #20)
> I am experience this issue aswell (Have an Elantech Touchpad in an Acer
> CB3-431 laptop)
> 
> 
> With Synaptic driver I can circle my cursor around in a very small circle,
> around a character like'V' on the screen for example. With Libinput I can't,
> it ends up being a very messed up circle. 
> 
> Using my touchpad with libinput just doesn't feel right, it makes using my
> laptop feel unstable, I find myself going to back to X even though I want to
> be in Wayland very badly.
> 
> I'm running Arch linux and can try and test any changes that are made or
> perform tests. Let me know. Thanks for all the hard work that you do.

Could your problem be to related to this issue #99410 ?

Most likely the hysteresis, see bug 98839

Whatever it was, Peter, was completely fixed in 11.1.

Tell me if you think I should close this bug. I feel like I should. I've tested 11.1 in Fedora and it's completely fixed.

Oki, closing then. Thanks for testing and letting me know.