| 1 |
On 12/15/2009 11:11 AM, Allan Gottlieb wrote: |
| 2 |
> It seems to me that this mouse sends two button events for some of the |
| 3 |
> "physical buttons". For example moving the wheel to the left reports |
| 4 |
> button press 13 |
| 5 |
> button press 6 |
| 6 |
> button release 6 |
| 7 |
> button release 13 |
| 8 |
> |
| 9 |
> Similar results for the many other buttons on the beast. |
| 10 |
> |
| 11 |
> Is this what the device actually does or does it signify a faulty X |
| 12 |
> setup on my part? |
| 13 |
> |
| 14 |
> I have the evdev driver in my kernel. |
| 15 |
> |
| 16 |
> I use xorg.conf and have |
| 17 |
> Section "InputDevice" |
| 18 |
> Identifier "Logitech MX1000" |
| 19 |
> Driver "evdev" |
| 20 |
> Option "Device" "/dev/input/event2" |
| 21 |
> EndSection |
| 22 |
> |
| 23 |
> gottlieb@allan /dev/input/by-id $ ls -l /dev/input/by-id/usb-Logitech_USB_Receiver-event-mouse |
| 24 |
> lrwxrwxrwx 1 root root 9 Dec 15 11:20 /dev/input/by-id/usb-Logitech_USB_Receiver-event-mouse -> ../event2 |
| 25 |
|
| 26 |
As I recall, the fix for this problem is a sys-adm/lomoco. |
| 27 |
|
| 28 |
Logitech mice actually produce those double events... lomoco allows you |
| 29 |
tell the mouse to stop. I've got a udev rule for it, I think lomoco put |
| 30 |
it there, but I've had logitech MX mice for years and lomoco is a fork |
| 31 |
of a fork and may no longer contain the udev script. |
| 32 |
|
| 33 |
You also might look into imwheel from the Mandrake distrabution as it |
| 34 |
contains patches to deal with more than 10 buttons. |
Archives