Arch Linux

ChrispyChris3

Member

Registered: 2018-10-08

Posts: 19

Xinput Touchpad Device Changing ID Randomly

This morning I was having issues with my touchpad and this led me to do some investigating. I found out the reason for my issue, but this still left me confused why my aliases to enable and disable the touchpad suddenly stopped working. The touchpad device went from id=10 to id=11 and I found this because when running the alias to enable tapping, it reported that the device had no such property. Suddenly "Mouse" was device 10. I was hoping someone could maybe help explain why this issue would suddenly crop up after months of never having any issues like this.

Also another question pertaining to this: How would I keep my aliases working if the device number does change for my touchpad with the "Tapping Enabled" property? I do have a configuration file with "Option 'Tapping' 'on'" but I do like to turn it off at times. That was just so when booting the touchpad would work consistently.

Thanks!

Last edited by ChrispyChris3 (2024-07-28 18:59:10)

Maniaxx

Member

Registered: 2014-05-14

Posts: 758

Re: Xinput Touchpad Device Changing ID Randomly

Probably depends on udev finding one first. Same as HDDs (sda<>sdb). Don't rely on that.
If you tell us your "alias" we might find a more proper method.

---

sys2064

ChrispyChris3

Member

Registered: 2018-10-08

Posts: 19

Re: Xinput Touchpad Device Changing ID Randomly

Ahh, okay. That's so weird considering I don't plug anything into this laptop. I do see what you're saying, although I'm wondering what mouse udev suddenly started finding. My aliases are:

alias touchon="xinput set-prop 10 'libinput Tapping Enabled' 1"
alias touchoff="xinput set-prop 10 'libinput Tapping Enabled' 0"

Maniaxx

Member

Registered: 2014-05-14

Posts: 758

Re: Xinput Touchpad Device Changing ID Randomly

Use 'device name' (xinput --list) instead of 'id'. That should be more persistent.

---

sys2064