Hi Javier, I was facing the same problem like Magnus. Switching from synaptics to libinput with the config form the wiki link you posted worked just fine! Tapping works again for me now. Thank you very much! Cheers, Daniel (@FillFeile) On 16.06.2016 22:59, Javier Vasquez via arch-general wrote:

...

On Thu, Jun 16, 2016 at 2:34 PM, Magnus Therning wrote:

Yesterday I could tap my touch pad to trigger mouse clicks (single finger for left mouse button, ...), but today nothing! ... Did you happen to upgrade your Arch box in the middle of "it worked" and "it doesn't work"? And did you happed to use the synaptics Xorg driver?

I think Xorg now uses libinput as default as opposed to prior versions. I have been using libinput any ways since it was made available, so the transition didn't affect me, and besides I'm OK with the tapping offered by libinput. Actually I removed totally the xf86-input-synaptics package from my Arch boxes already. You can take a look at the install message:

https://git.archlinux.org/svntogit/packages.git/tree/trunk/xf86-input-synapt...

And if you want to read how to enable tapping on libinput:

https://wiki.archlinux.org/index.php/Libinput#Touchpad_configuration

Hopefully this helps,

On Thu, Jun 16, 2016 at 7:50 PM, Kyle Terrien wrote:

...

Javier Vasquez via arch-general wrote: ...

https://git.archlinux.org/svntogit/packages.git/tree/trunk/xf86-input-synapt...

I saw that message while upgrading a couple of days ago.

xf86-input-synaptics driver is on maintenance mode and xf86-input-libinput driver must be prefered over.

But I didn't understand what "must be prefered over" means (grammar error).

You suggested that libinput is the default now. That would make more sense. So is this a warning of some sort, or is it a notification to try to encourage people to switch to libinput?

Does switching break any older desktop environments? (e.g. MATE, Window Maker)

Hi Kyle, Although stalling development (just maintenance for now) on the Xorg synaptics driver doesn't mean it's deprecated, I prefer the move onto libinput as I did some time back. Not related to what Arch might encourage, but I would encourage the move. BTW, I have a libinput config to enable tapping, without specifying the "Driver" since november, and if present, Xorg has always treated libinput as the default over Synaptics. The thing is that now the Arch xorg-server package requires the libinput driver as well as the evdev one. And that makes libinput the default no matter you wanted it (as I did by installing it) or not (you can still opt for the synaptics driver through config). I use plain fluxbox WM, no DE, so I guess other more used and/or supported WMs/DEs might work just fine. The support for libinput on Xorg by Arch is not new. The anouncement of the availability to chose for it is from 2015-11-13: https://www.archlinux.org/news/xorg-1180-enters-testing So it might be it's been tested on different WMs/DEs by now, and by different users. One can still keep using the synaptics driver if preferred as mentioned. It provides more options to tweak (for those who understand them and care). Its config is similar to its libinput counterpart (just longer), and its main requirement is to specify to use the synaptics "Driver" in there. You can read the wiki for some synaptics config basics: https://wiki.archlinux.org/index.php/Touchpad_Synaptics Or use the config from Fabien on this same thread: https://lists.archlinux.org/pipermail/arch-general/2016-June/041457.html -- Javier

Kyle Terrien via arch-general writes:

Javier Vasquez via arch-general wrote:

...

I think Xorg now uses libinput as default as opposed to prior versions. I have been using libinput any ways since it was made available, so the transition didn't affect me, and besides I'm OK with the tapping offered by libinput. Actually I removed totally the xf86-input-synaptics package from my Arch boxes already. You can take a look at the install message:

https://git.archlinux.org/svntogit/packages.git/tree/trunk/xf86-input-synapt...

I saw that message while upgrading a couple of days ago.

xf86-input-synaptics driver is on maintenance mode and xf86-input-libinput driver must be prefered over.

But I didn't understand what "must be prefered over" means (grammar error).

I found this text on the Arch site: Xorg 1.18.0 is entering [testing] with the following changes: * You can now choose between xf86-input-evdev and xf86-input-libinput. * xf86-input-aiptek will not be updated and will be removed when xorg-1.18.0 is moved to [extra] Update: Nvidia drivers are now compatible with xorg-1.18.0 (ABI 20) So I tried switching between input-evdev (what I used before) and input-libinput, but no change. From others in the thread I gather that removing input-synaptics and configuring libinput properly will fix it. I'll have to wait with trying until I'm in front of my laptop this evening. It's not easy to cover all use cases when making switches like this, so it's wonderful that the Arch users are as helpful as they are :) /M -- Magnus Therning OpenPGP: 0x927912051716CE39 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus Finagle's First Law: To study a subject best, understand it thoroughly before you start.

Fabien Dubosson via arch-general:

Hi,

...

Yesterday I could tap my touch pad to trigger mouse clicks (single finger for left mouse button, ...), but today nothing!

Anyone else seeing this, or am I alone?

I had the same problem yesterday after an update. I don't know what is the cause, but it seems that the synaptic options "TapButton[123]" are set to zero instead of "[123]" respectively now.

...

I had a quick look around but found no news suggesting that any recent upgrade requires configuring my touchpad, or that I need to install any new package to get my touch pad back to working the way I want.

I also haven't seen any information about this.

...

Any and all suggestions are welcome :)

I solved this by creating a "/etc/X11/xorg.conf.d/10-synaptics.conf" file with the following content:

Section "InputClass" Identifier "Touchpad" Driver "synaptics" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "TapButton1" "1" Option "TapButton2" "2" Option "TapButton3" "3" EndSection

++ Fabien

I did the same as Fabien but a litle tuned because I use a chrombook: Section "InputClass" Identifier "touchpad peppy cyapa" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" MatchProduct "cyapa" Option "FingerLow" "10" Option "FingerHigh" "10" Option "TapButton1" "1" Option "TapButton2" "2" Option "TapButton3" "3" EndSection Its very nice that you can have the full control of your pad conf! cheers