Bug 30666 - Pressing numlock breaks left click on the Sharkoon Fireglider mouse
Summary: Pressing numlock breaks left click on the Sharkoon Fireglider mouse
Status: RESOLVED WONTFIX
Alias: None
Product: xorg
Classification: Unclassified
Component: Input/evdev (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Peter Hutterer
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-06 14:33 UTC by Luke Benstead
Modified: 2016-11-28 04:39 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Luke Benstead 2010-10-06 14:33:07 UTC
I'm running Ubuntu 10.10 RC. I only upgraded the other day and noticed this bug immediately so I know it's a regression between the xorg versions of 10.04 and 10.10. It's reported downstream here: https://bugs.launchpad.net/ubuntu/+bug/637062

Basically, when pressing numlock with this mouse connected, a mouse button 1 event is sent but not released. So basically if numlock is enabled the mouse acts like you are holding down the first button.
Comment 1 Peter Hutterer 2010-10-12 22:27:03 UTC
what's the xserver version you're running? 

please attach the evtest output for the device when pressing the button
Comment 2 Luke Benstead 2010-10-12 23:51:52 UTC
Hi Peter,

The top of my Xorg.0.log says:

X.Org X Server 1.9.0
Release Date: 2010-08-20

Also this part of the log looks interesting:

[    17.322] (**) A4Tech USB Full Speed: Applying InputClass "evdev pointer catchall"
[    17.322] (**) A4Tech USB Full Speed: always reports core events
[    17.322] (**) A4Tech USB Full Speed: Device: "/dev/input/event4"
[    17.361] (II) A4Tech USB Full Speed: Found 20 mouse buttons
[    17.361] (II) A4Tech USB Full Speed: Found scroll wheel(s)
[    17.361] (II) A4Tech USB Full Speed: Found relative axes
[    17.361] (II) A4Tech USB Full Speed: Found x and y relative axes
[    17.361] (II) A4Tech USB Full Speed: Configuring as mouse
[    17.361] (**) A4Tech USB Full Speed: YAxisMapping: buttons 4 and 5
[    17.361] (**) A4Tech USB Full Speed: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[    17.361] (II) XINPUT: Adding extended input device "A4Tech USB Full Speed" (type: MOUSE)
[    17.361] (II) A4Tech USB Full Speed: initialized for relative axes.
[    17.361] (II) config/udev: Adding input device A4Tech USB Full Speed (/dev/input/mouse0)
[    17.361] (II) No input driver/identifier specified (ignoring)
[    17.362] (II) config/udev: Adding input device A4Tech USB Full Speed (/dev/input/event5)
[    17.362] (**) A4Tech USB Full Speed: Applying InputClass "evdev keyboard catchall"
[    17.362] (**) A4Tech USB Full Speed: always reports core events
[    17.362] (**) A4Tech USB Full Speed: Device: "/dev/input/event5"
[    17.401] (II) A4Tech USB Full Speed: Found 1 mouse buttons
[    17.401] (II) A4Tech USB Full Speed: Found scroll wheel(s)
[    17.401] (II) A4Tech USB Full Speed: Found relative axes
[    17.401] (II) A4Tech USB Full Speed: Found absolute axes
[    17.401] (II) A4Tech USB Full Speed: Found x and y absolute axes
[    17.401] (II) A4Tech USB Full Speed: Found keys
[    17.401] (II) A4Tech USB Full Speed: Configuring as mouse
[    17.401] (II) A4Tech USB Full Speed: Configuring as keyboard
[    17.401] (**) A4Tech USB Full Speed: YAxisMapping: buttons 4 and 5
[    17.401] (**) A4Tech USB Full Speed: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[    17.401] (II) XINPUT: Adding extended input device "A4Tech USB Full Speed" (type: KEYBOARD)

Notice how it seems to be reported as both a mouse and a keyboard.

I'm not totally sure how to run evtest. I've just tried but now I've lost left-click (it's like it's held down) and can only navigate with the keyboard so I'll have to try again later.
Comment 3 Peter Hutterer 2016-11-28 04:39:43 UTC
This is a mass change of bugs. Bugs assigned to me that haven't been updated in the last 3 years are closed as WONTFIX, because, well, let's at least be honest about it.

Please do not re-open unless you have a really good reason to do so (e.g. you're fixing it yourself). If it hasn't been fixed in the last 3 years, it probably won't be fixed anytime soon either. Sorry.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.