Originally posted by slacka
View Post
Announcement
Collapse
No announcement yet.
Libinput 1.6 Released With New Touchpad Acceleration
Collapse
X
-
-
Originally posted by omer666 View Post
To be fair, Fedora's Xorg adoption policy is not always welcome, for example they switched to Xorg 1.18 before it had nVidia proprietary driver support, which initiated some flaming from users. Remember that Arch is bleeding edge, rolling realease, but it is by no means meant to be unstable. Also you are free to package it yourself and contribute ;-)
Comment
-
Originally posted by liam View Post
That doesnt sound like an acceleration issue but instead your trackpad is reporting an incorrect resolution.
That can only be addressed through bug reporting and updates to the libinput tweaks file.
Comment
-
Originally posted by andrebrait View Post
Actually, it is exactly an acceleration issue. For one, 1.6 fixes it in my laptop, which reports the cprrect dimensions to the driver, and second, Peter explained how these things could be a result of the bad acceleration algorithms in the pre-1.6 libinput releases. Only issue left for me with libinput is regarding tap misdetection, and I already filled a bug report and provided recordings, etc.
If you've got a link to a bugreport, or something by Peter that explains how this could be I'd appreciate it.
- Likes 1
Comment
-
Originally posted by liam View Post
He did? I don't know how the accel algorithm could go that badly for you without the trackpad reporting bad info. If it was just the algorithm then everyone whose trackpad was detected correctly would have similar problems.
If you've got a link to a bugreport, or something by Peter that explains how this could be I'd appreciate it.
Comment
-
Originally posted by andrebrait View Post
Is his blog entry ok? In it he aknowldged the awfulness of the old acceleration code and how imprecise it could make things and describe how he much improved it for 1.6.0. Anyway, like I said, my touchpad reported correct dimensions and was still a mess before 1.6.0.
http://who-t.blogspot.com.br/2016/12...ation.html?m=1
Ok, I'd read that post some back (you can see my comment), but, assuming libinput has the correct dimensions and resolution for the to, it doesn't explain why some trackpads work fine and others (notably elantech) don't. It simply says that the acceleration curves that were the same for everyone we suboptimal. That's fine, but I don't know why that would cause a working trackpad to accelerate to maximum at the slightest movement.
The problem may simply be that we have different expectations regarding trackpad behavior and thus I just don't notice these issues.
Comment
Comment