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!
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!
FS#59956 - libinput - touchpad no longer has Click Method property
Attached to Project:
Arch Linux
Opened by Peter Fajdiga (peterfaj) - Thursday, 06 September 2018, 08:15 GMT
Last edited by Eli Schwartz (eschwartz) - Thursday, 10 January 2019, 03:34 GMT
Opened by Peter Fajdiga (peterfaj) - Thursday, 06 September 2018, 08:15 GMT
Last edited by Eli Schwartz (eschwartz) - Thursday, 10 January 2019, 03:34 GMT
|
DetailsDescription:
After an update on 2018-08-20 (or maybe a few days earlier), the touchpad no longer has a Click Method property. I don't know which package could have caused this, libinput was not updated. I have attached the output of 'cat /var/log/pacman.log | grep -i upgraded' from 2018-08-08 to 2018-08-20. I'm using a Thinkpad T480s, the touchpad is listed as "Elan Touchpad" by xinput. Before the update, it was listed as something longer but similar (it still had both Elan and Touchpad in its name). Additional info: libinput package version: 1.11.3-1 xf86-input-libinput package version: 0.28.0-1 Steps to reproduce: xinput list-props "pointer:Elan Touchpad" | grep -i click (nothing is printed) |
This task depends upon
Closed by Eli Schwartz (eschwartz)
Thursday, 10 January 2019, 03:34 GMT
Reason for closing: Fixed
Additional comments about closing: OP request: It's back to normal.
Thursday, 10 January 2019, 03:34 GMT
Reason for closing: Fixed
Additional comments about closing: OP request: It's back to normal.
Comment by Peter Fajdiga (peterfaj) -
Wednesday, 09 January 2019, 21:27 GMT
This was fixed just as suddenly as it was broken. I can confirm it works as expected again.
updates