I added a simple login shell script to “System Settings - Startup and Shutdown - Autostart” that enables locked by default “tap-to-click” option via xinput (not available at all in input settings).
#!/bin/sh
xinput set-prop 14 332 1
But it doesn’t work. I have to run my sh file every time I reboot my laptop.
The first one might be more reliable as you can ensure your script is run just right after the touchpad is available and registered. The second one can also quite reliable by targeting an event that happens way later, like graphical.target as opposed to multi-user.target, for instance.
But before that, you might want to ensure that your script is really executed by logging something to a file in your home directory, like the command output and probably timestamp.
Just saw this, and it looked remarkably like what I’m doing with my PC. Although, I don’t to it globally, only for my user, seeing as I’m the only one that uses my computer. But I’m guessing that doing it globally would be very much the same. That being said, the way I did it, is as follows:
Create the file where the contains the command to run:
nano ~/.config/plasma-workspace/env/<filename>.sh
Replace <filename> with an appropriate name for your purpose. Something like set_touchpad_tap-to-click would work.
This will create the file file ~/.config/plasma-workspace/env/<filename>.sh in your home directory for running when (in my case) KDE logs in. I’m guessing the directory would only be slightly different if you do not use KDE.
Populate the newly created file with your contents. Mine has an export statement chained by an and and an OR: