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