You are not logged in.
Pages: 1
I have the following udev rule to turn laptop touchpad off/on when an external mouse is in use:
SUBSYSTEM=="input", ACTION=="add", ATTR{name}=="Logitech Pebble Mouse", RUN+="/bin/su <user> -c 'DISPLAY=:0 xinput --disable 11'"
SUBSYSTEM=="input", ACTION=="remove", ATTR{name}=="Logitech Pebble Mouse", RUN+="/bin/su <user> -c 'DISPLAY=:0 xinput --enable 11'"That kind of rule works fine with USB mice, but does not behave correctly with a bluetooth mouse (Logitech Pebble) I'm currently using. The touchpad gets disabled when I power on the BT mouse, like it should. But when I power off the mouse, BlueMan correctly informs that the mouse is disabled, but the touchpad fails to become re-enabled. Obviously, the bluetooth subsystem is not relaying to the kernel the information that the BT mouse is not there any more.
How should I modify the udev rule to make it work with a BT mouse?
Of course, I could just type
xinput --enable 11into terminal to enable the touchpad, but that feel kind of... kludgey. I'd rather have udev to properly handle it.
Offline
You can use this to check what the kernel & udev receive from the mouse when it's turned off:
udevadm monitorThis post seems to suggest the "hid" subsystem might be more useful for Bluetooth.
Disclaimer: I don't use Bluetooth myself so I can't test.
Jin, Jîyan, Azadî
Offline
Thanks for the link, that might actually work.
Offline
No, using the 'hid' subsystem as per the thread didn't work at all
. Well, it was almost 10 years old thread...
Offline
So what did udevadm show?
Jin, Jîyan, Azadî
Offline
Pages: 1