This almost feels like a ritual that I go through every 3-4 years: figure
out how to disable the laptop's obnoxious touchpad from registering phantom
tap clicks.
This time around Google claims XFCE's "Mouse and Touchpad" settings has a
checkbox for that. Google also gives instructions for u
On 15/09/2021 07:59, Sam Varshavchik wrote:
This almost feels like a ritual that I go through every 3-4 years: figure out
how to disable the laptop's obnoxious touchpad from registering phantom tap
clicks.
This time around Google claims XFCE's "Mouse and Touchpad" settings has a
checkbox for
Ed Greshko writes:
On 15/09/2021 07:59, Sam Varshavchik wrote:
This almost feels like a ritual that I go through every 3-4 years: figure
out how to disable the laptop's obnoxious touchpad from registering phantom
tap clicks.
This time around Google claims XFCE's "Mouse and Touchpad" settin
On any given reboot/login/logout the id= can and will change. The
scanning order/process should be the same, but if all devices are
asked in parallel tiny timing differences in how each answers can
change the order.
You generally need code first to find the current ID for the given
named device,
On Wed, Sep 15, 2021 at 12:24:32PM -0500, Roger Heflin wrote:
On any given reboot/login/logout the id= can and will change. The
scanning order/process should be the same, but if all devices are
asked in parallel tiny timing differences in how each answers can
change the order.
You generally nee
Sam Varshavchik writes:
So, after reading your message, this morning I went back in. For some
inexplicable reason:
1) xinput now tells me that id=12 is an "ETPS/2 Elantech Touchpad"
And today it's back to a PS/2 mouse.
mrsam@traveler ~]$ xinput list
⎡ Virtual core pointer
Sam Varshavchik writes:
Sam Varshavchik writes:
So, after reading your message, this morning I went back in. For some
inexplicable reason:
1) xinput now tells me that id=12 is an "ETPS/2 Elantech Touchpad"
And today it's back to a PS/2 mouse.
mrsam@traveler ~]$ xinput list
⎡ Virtual core
