From: Allan Gottlieb <gottlieb@nyu.edu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] off-topic: logitech mice (MX1000)
Date: Mon, 21 Dec 2009 23:15:47 -0500 [thread overview]
Message-ID: <yu91vinhcek.fsf@nyu.edu> (raw)
In-Reply-To: <4B2F01CC.7040808@cox.net> (John Campbell's message of "Sun, 20 Dec 2009 21:04:12 -0800")
At Sun, 20 Dec 2009 21:04:12 -0800 John Campbell <jdc.rpv@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
>>
>> gottlieb@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
prev parent reply other threads:[~2009-12-22 4:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 19:11 [gentoo-user] off-topic: logitech mice (MX1000) Allan Gottlieb
2009-12-16 2:09 ` [gentoo-user] " walt
2009-12-16 6:05 ` Allan Gottlieb
2009-12-16 19:06 ` walt
2009-12-16 21:36 ` Albert Hopkins
2009-12-17 3:51 ` Allan Gottlieb
2009-12-17 15:07 ` walt
2009-12-17 15:30 ` Michael Schreckenbauer
2009-12-17 21:09 ` Allan Gottlieb
2009-12-17 16:49 ` Albert Hopkins
2009-12-17 21:23 ` Allan Gottlieb
2009-12-17 23:34 ` walt
2009-12-18 2:14 ` Allan Gottlieb
2009-12-21 5:04 ` [gentoo-user] " John Campbell
2009-12-22 4:15 ` Allan Gottlieb [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yu91vinhcek.fsf@nyu.edu \
--to=gottlieb@nyu.edu \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox