At Sun, 20 Dec 2009 21:04:12 -0800 John Campbell <jdc....@cox.net> wrote:
> On 12/15/2009 11:11 AM, Allan Gottlieb wrote: >> It seems to me that this mouse sends two button events for some of the >> "physical buttons". For example moving the wheel to the left reports >> button press 13 >> button press 6 >> button release 6 >> button release 13 >> >> Similar results for the many other buttons on the beast. >> >> Is this what the device actually does or does it signify a faulty X >> setup on my part? >> >> I have the evdev driver in my kernel. >> >> I use xorg.conf and have >> Section "InputDevice" >> Identifier "Logitech MX1000" >> Driver "evdev" >> Option "Device" "/dev/input/event2" >> EndSection >> >> gottl...@allan /dev/input/by-id $ ls -l >> /dev/input/by-id/usb-Logitech_USB_Receiver-event-mouse >> lrwxrwxrwx 1 root root 9 Dec 15 11:20 >> /dev/input/by-id/usb-Logitech_USB_Receiver-event-mouse -> ../event2 > > As I recall, the fix for this problem is a sys-adm/lomoco. > > Logitech mice actually produce those double events... lomoco allows you > tell the mouse to stop. I've got a udev rule for it, I think lomoco put > it there, but I've had logitech MX mice for years and lomoco is a fork > of a fork and may no longer contain the udev script. > > You also might look into imwheel from the Mandrake distrabution as it > contains patches to deal with more than 10 buttons. Magnificent!! I did really think the mouse could be sending button events for two different logical buttons when only one physical button was pushed. That got me looking at xorg.conf to see where I screwed up. But, as you said, the MX mice do send events for two buttons. As you also said lomoco fixes it. "sudo lomoco --nosms" is now in my startup script. Thank you very much ! allan
