What is the difference in using xinput and synclient for deactivating a touchpad in X

Asked Apr 01 '16 at 19:30

Active Dec 29 '16 at 08:43

Viewed 726 times

I have troubles using xinput --disable or --set-prop "Device Enabled" or set-prop "Synaptics Off".

It seems that --disable / --enable and "Device Enabled" are meant to deactivate the whole device, meaning buttons and touchpad, whereas "Synaptics Off" just works on the touchpad.

However, when I want to deactivate the touchpad using udev rules when a USB mouse is attached, neither of those mechanism works. I then can only use synclient "TouchpadOff=1" to deactivate the touchpad.

What is the difference in all those mechanisms, and why does --disable / --enable work within an X session (even as another user, e.g. root when setting DISPLAY and XAUTHORITY accordingly), but not when executed by a rule in udev?

edited Apr 01 '16 at 21:55

techraf

5,941

asked Apr 01 '16 at 19:30

Joysn

1

Why synclient does not work anymore: https://who-t.blogspot.com.au/2016/07/why-synclient-does-not-work-anymore.html – Michael Yoo Dec 28 '16 at 14:07
Have a look at those explanations: http://who-t.blogspot.ch/2016/07/why-synclient-does-not-work-anymore.html https://wiki.archlinux.org/index.php/Touchpad_Synaptics – Grandswiss Dec 29 '16 at 08:35
Why udev, you may go directly with xorg.conf . see https://unix.stackexchange.com/a/439528/12209 – user.dz Oct 14 '19 at 10:44
@MichaelYoo - what do you mean? I am using that in Mint Xfce to toggle touchpad on/off – cipricus Jan 05 '21 at 12:21

What is the difference in using xinput and synclient for deactivating a touchpad in X

0 Answers0