Right click is registered twice sometimes with Razer DeathAdder 2013 mouse

[Peter Hutterer]

On Wed, Jun 04, 2014 at 06:54:39PM +0200, Double V wrote:
> Thanks for answering,
> 
> The same behaviour happens, I tried multiple times and get sometimes
> double clicks too:

note that evemu merely records the events as they come out of the kernel, it
doesn't do anything to the device itself.

 
> ################################
> #      Waiting for events      #
> ################################
> E: 0.000000 0004 0004 589826    # EV_MSC / MSC_SCAN 589826
> E: 0.000000 0001 0111 0001    # EV_KEY / BTN_RIGHT            1
> E: 0.000000 0000 0000 0000    # ------------ SYN_REPORT (0) ----------
> E: 0.062974 0004 0004 589826    # EV_MSC / MSC_SCAN 589826
> E: 0.062974 0001 0111 0000    # EV_KEY / BTN_RIGHT            0
> E: 0.062974 0000 0000 0000    # ------------ SYN_REPORT (0) ----------
> E: 0.071971 0004 0004 589826    # EV_MSC / MSC_SCAN 589826
> E: 0.071971 0001 0111 0001    # EV_KEY / BTN_RIGHT            1
> E: 0.071971 0000 0000 0000    # ------------ SYN_REPORT (0) ----------
> E: 0.076967 0004 0004 589826    # EV_MSC / MSC_SCAN 589826
> E: 0.076967 0001 0111 0000    # EV_KEY / BTN_RIGHT            0
> E: 0.076967 0000 0000 0000    # ------------ SYN_REPORT (0) ----------

the time between release and press is just 9 ms, and 5 ms between the second
release. This looks awfully fast and suggests a hw problem. And a 2-min
search for "razer deathadder click problem" suggests this is a common
problem on those devices.

If you still have warranty on the thing, I suggest to try to swap it.
easiest solution all round.

otherwise we really have to add debouncing (there was a bug for this a few
months back but I can't find it now), though I'd prefer this to be in the
kernel, not in the xorg driver.

> Sometimes not:
> 
> ################################
> #      Waiting for events      #
> ################################
> E: 0.000000 0004 0004 589826    # EV_MSC / MSC_SCAN 589826
> E: 0.000000 0001 0111 0001    # EV_KEY / BTN_RIGHT            1
> E: 0.000000 0000 0000 0000    # ------------ SYN_REPORT (0) ----------
> E: 0.006945 0004 0004 589826    # EV_MSC / MSC_SCAN 589826
> E: 0.006945 0001 0111 0000    # EV_KEY / BTN_RIGHT            0
> E: 0.006945 0000 0000 0000    # ------------ SYN_REPORT (0) ----------
> 
> Also I noted that my mouse is listed multiple times when starting
> the command:

you'll probably find that the other devices are either mute or only send
specific events. It's quite common to have multimedia keys on a different
kernel device than other keys.

Cheers,
   Peter