On Wed, 7 Jun 2017 19:52:51 +0100 andrea wrote: > andrea@localhost:~$ xinput --list > ⎡ Virtual core pointer id=2 [master pointer (3)] > ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] > ⎜ ↳ xwayland-pointer:13 id=6 [slave pointer (2)] > ⎜ ↳ xwayland-relative-pointer:13 id=7 [slave pointer (2)] > ⎣ Virtual core keyboard id=3 [master keyboard (2)] > ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] > ↳ xwayland-keyboard:13 id=8 [slave keyboard (3)] > > tried xinput get-button-map and the ones that show something show all an unaltered map > > andrea@localhost:~$ xinput get-button-map 4 > 1 2 3 4 5 6 7 8 9 10 id 4 is the virtual pointer for the XTEST extension and isn't a actual mouse. Try id 6 instead of 4. I suspect that represents the real mice which wayland has mushed together into a single mouse. Here's what I get when I plug in my 2nd mouse while not using wayland: zooty> xinput --list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Kensington Kensington Expert Mouse id=8 [slave pointer (2)] ⎜ ↳ Logitech Logitech Illuminated Keyboard id=10 [slave pointer (2)] ⎜ ↳ Kensington Kensington Expert Mouse id=13 [slave pointer (2)] I do see two real mice show up, id 8 and id 13. (I have no idea what part of my keyboard it thinks is a pointer, so ignore that :-). Looks like you'll have to not use wayland if you want to remap buttons in just one mouse. (Unless there is some super secret way to burrow under the layers xinput can see). The challenge might be in determining the ID numbers to use since they'll probably vary at random, especially if you plug and unplug the mice. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
