Seems like it's not an udev or X problem - kernel thinks it found a
joystick: it has an entry 'js0' in '/sys/class/input'.  Moreover it
reports two interface descriptors for the device (as seen in attached
'lsusb -v -d 09da:8090' output).  One for mouse and another one for ...
keyboard.  When I tried to look at the events evtest was able to capture
for the corresponding to the 'js0' '/dev/input/eventN' device node it
showed a long list of key events with different codes (along with
joystick events).  I was once even able to receive some events by
clicking on the mouse whell - and couldn't reproduce it later.  So this
is probably just another buggy A4Tech device (afaik there are already a
couple of quirks in the kernel for their HID devices).

PS: I have an A4Tech X7 mouse but the symptoms are quite the same.  It
even has the same USB ids.

** Attachment added: "lsusb output"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/713556/+attachment/2158626/+files/a4tech-lsusb.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/713556

Title:
  Sharkoon Fireglider mouse is wrongly detected as a joystick

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to