Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#44536 - [gnome-control-center] Touchpad controls do not seem to work with xf86-input-libinput

Attached to Project: Arch Linux
Opened by Britt Yazel (brittyazel) - Friday, 10 April 2015, 17:25 GMT
Last edited by Jan de Groot (JGC) - Friday, 16 October 2015, 17:12 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No

Details

In gnome 3.16, when using the X11 environment paired with xf86-input-libinput for the input driver, the touchpad configurable settings in Gnome-Control-Center do not seem to have any effect. Toggling the touchpad on and off, tweaking the sensitivity, two finger scroll, etc. does nothing. I assume, however, that these settings should have an effect, as with 3.14 none of these settings were exposed when using xf86-input-libinput.

Further, testing under a wayland environment shows that the Gnome-control-center settings do properly work when running directly off of libinput.

Something specific about the xf86-input-libinput wrapper is not working as intended.
This task depends upon

Closed by  Jan de Groot (JGC)
Friday, 16 October 2015, 17:12 GMT
Reason for closing:  Fixed
Additional comments about closing:  3.18
Comment by Britt Yazel (brittyazel) - Wednesday, 15 April 2015, 23:15 GMT
I can confirm that the upgrade to 3.16.1 does not solve this issue. Though now I have a 'greyed' out "two-finger-scroll" option under X11, even though two-finger scrolling works. Also, at some point tap-to-click must have stopped working (or never did, I don't know), regardless of being checked.
Comment by Britt Yazel (brittyazel) - Wednesday, 13 May 2015, 18:33 GMT
Again, the update the 3.16.2 did not fix this. Upstream doesn't have this bug reported. Maybe it is Arch specific?
Comment by Britt Yazel (brittyazel) - Friday, 16 October 2015, 16:10 GMT
This does not seem to bean issue anymore. You can close this bug.

Loading...