[Bug 39509] Re: [regression] Pointer events ignored if 'Buttons' events exist on the same /dev/input device (Logitech MX 700 keyboard)

[Rob Hughes]

This is how I have my udev rules set up. It's not really a work around. I followed a how-to I found on linux-gamers.net for setting up a mx-1000.

/etc/udev/rules.d
# cat 01_logitech.rules
KERNEL="event*", SYSFS{idVendor}="046d", SYSFS{idProduct}="c512" NAME="input/event-mx3100" SYMLINK="input/%k"
KERNEL="mouse*", SYSFS{idVendor}="046d", SYSFS{idProduct}="c512" NAME="input/event-mx3100" SYMLINK="input/%k"
KERNEL="event*", SYSFS{idVendor}="046d", SYSFS{idProduct}="c041" NAME="input/event-g5" SYMLINK="input/%k"
KERNEL="mouse*", SYSFS{idVendor}="046d", SYSFS{idProduct}="c041" NAME="input/event-g5" SYMLINK="input/%k"

Which gives:
ls -l /dev/input/
total 0
crw-rw---- 1 root root    13,  64 2006-04-24 12:28 event0
crw-rw---- 1 root root    13,  65 2006-04-24 12:29 event1
lrwxrwxrwx 1 root root          8 2024-04-24 17:28 event2 -> event-g5
crw-rw---- 1 root root    13,  67 2006-04-24 12:29 event3
crw-rw---- 1 root root    13,  68 2006-04-24 12:29 event4
crw-rw---- 1 root root    13,  69 2024-04-24 17:28 event5
lrwxrwxrwx 1 root root         12 2006-04-24 12:29 event6 -> event-mx3100
lrwxrwxrwx 1 root root         12 2006-04-24 12:29 event7 -> event-mx3100
crw-rw---- 1 root root    13,  66 2024-04-24 17:28 event-g5
crw-rw---- 1 root root    13,  71 2006-04-24 12:29 event-mx3100
crw-rw---- 1 root plugdev 13,   0 2006-04-24 12:29 js0
crw-rw---- 1 root root    13,  63 2006-04-24 12:28 mice
lrwxrwxrwx 1 root root          8 2024-04-24 17:28 mouse0 -> event-g5
crw-rw---- 1 root root    13,  33 2024-04-24 17:28 mouse1
lrwxrwxrwx 1 root root         12 2006-04-24 12:29 mouse2 -> event-mx3100
crw-rw---- 1 root root    13, 128 2024-04-24 17:28 ts0
crw-rw---- 1 root root    13, 129 2024-04-24 17:28 ts1
crw-rw---- 1 root root    13, 130 2006-04-24 12:29 ts2

When I use this, xorg reports that the mx 1000 mouse (the mx 3100 combo is a mx 1000 mouse and a lx 700 keyboard feeding into a single dual-channel receiver) lacks corepointer capability.

Also, it should be noted that without my udev rules, the g5 mouse is mapped to event1 and the mx 1000 is mapped to event5.

I also found something else; if I use a different mouse as the corepointer, then X starts and I see the extended buttons from the keyboard. But these event numbers are getting mapped to bizarre keycodes that are completely different than what they got mapped to under hoary. Many of the extended keys map to various punctuation, letter and number keys. This is very strange and it's quite possible that I still don't fully understand what's going on here.

-- 
[regression] Pointer events ignored if 'Buttons' events exist on the same /dev/input device (Logitech MX 700 keyboard)
https://launchpad.net/bugs/39509