some possibly helpful specs: bodhi linux 5.1 (based on ubuntu 18.04) on a thinkpad w540 (i7, 16 gigs o’ ram) with a synaptics branded touchpad and the synaptics input driver installed.
my issue is almost identical to the one posted here. in brief, my touchpad doesn’t work correctly when i wake my system up from suspend. i decided to open a new thread to explore one possible solution. i have tried other unsuccessful methods and can expand on them if need be, but figured i would save making anyone wade through possibly unhelpful details if possible.
the functionality that i lose is that if i keep one finger on the keypad and drag another across it to and highlight text or files in a file manager (which i apparently do often enough that its loss is usually noticeable within 10 minutes after waking my system), the second finger is ignored and the highlight action does not occur. keeping one finger on the pad and dragging it does highlight, but is limited to how far my finger can move and is more complicated to pull off in general. neither
synclient list any differences between the state of the touchpad before or after suspending. luckily i found a similar solution to the one in the post linked above. after i modprobe the entire psmouse array (
sudo modprobe -r psmouse - the array includes my touchpad and a couple of other components) and then back on i can highlight as explained.
it doesn’t take much of an effort to run an alias to wake the pad back up correctly with modprobe, but after reading some suggestions and other threads like this one both here and on other sites i have attempted unsuccessfully to get the system to run the two modprobe commands. the crux of the question (as i see it after spending what feels like way too much time staring at this situation) at this stage is:
when a command that my user needs to run with sudo is placed in a file in /lib/systemd/system-sleep does it make a difference to the system if i add sudo to the command in that file?
i have done so both ways, rebooted the system and there was no difference. one link suggested that the commands should be in a separate file. another said that my commands needed to added to the hdparm file in that directory in order to run with administrative rights.
none of those options worked so i began to wonder (it feels like i am overthinking things and over-analyzing the smallest details at this point, but thought i would post the question and see) is if i needed to an exception in the sudoers file so that the command could be run with sudo but without needing a password entered.
it may help to note that libinput is also installed, but has never affected synaptics functionality on a similar (t430s) system though that system doesn’t suffer from this malfunction after waking from suspend.
i have considered that there might possibly be some conflict between the two, but don’t know enough about what libinput does to decide removing it would be the solution. i could definitely try that, but wanted to see if it was possible to get they system to modprobe (which definitley works) itself since i had spent so much time tinkering with that particular option
thanks in advance if anyone has any thought.