Bug 71687 - Wayland fails to detect Microsoft SideWinder x3 mouse
Summary: Wayland fails to detect Microsoft SideWinder x3 mouse
Status: RESOLVED FIXED
Alias: None
Product: Wayland
Classification: Unclassified
Component: wayland (show other bugs)
Version: 1.3.0
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Wayland bug list
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-17 01:33 UTC by Jonathan A.
Modified: 2013-12-17 00:16 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
output of udevadm test $(udevadm info --query=path -n /dev/input/js0) (8.01 KB, text/plain)
2013-11-17 01:33 UTC, Jonathan A.
Details
output of evtest /dev/input/event0 (4.42 KB, text/plain)
2013-12-07 15:17 UTC, Jonathan A.
Details

Description Jonathan A. 2013-11-17 01:33:29 UTC
Created attachment 89342 [details]
output of udevadm test $(udevadm info --query=path -n /dev/input/js0)

Distrobution: is Arch Linux

First up: I'm unsure if it's weston that is the issue, but I belive wayland is the cause. This mouse works normal with X and appears (strangely?) under /dev/input/js0 .

When I launch Weston (via weston-launch) while using my Microsoft SideWinder x3 mouse no cursor appears, mouse movement does nothing (at least visaible), and clicking mouse buttons also appear to do nothing.

I'm fairly certain weston/wayland isn't frozen because the moment I plug in another mouse a cursor appears and everything works normal. In addition with all my other mice I have if they're plugged in they work fine.

I somewhat recall a message previously (in a lesser version probably) mentioning something around the lines of "Ignoring a joystick" while launching weston, but I'm uncertain if it was related.

I'm unaware of how to get startup logs and such, but willing to try and work it out if you need me to do something

Attached is the output of `udevadm test $(udevadm info --query=path -n /dev/input/js0)` in case it's of any use.
Comment 1 Kristian Høgsberg 2013-12-05 20:49:51 UTC
Can you attach the output of evtest on the /dev/input/eventX file for the mouse?

thanks,
Kristian

http://cgit.freedesktop.org/evtest/
Comment 2 Jonathan A. 2013-12-07 15:17:50 UTC
Created attachment 90412 [details]
output of evtest /dev/input/event0

Added output of evtest /dev/input/event0 (my mouse), just interrupted once it got to the testing section as I doubt 100 lines of me moving my mouse is useful.
Comment 3 Kristian Høgsberg 2013-12-17 00:16:50 UTC
Should be fixed in master:

commit d0cb10a36bbc95ecfc2ba3f225a02c07300bdfe3
Author: Kristian Høgsberg <krh@bitplanet.net>
Date:   Mon Dec 16 15:57:53 2013 -0800

    evdev: Drop joystick rejection heurstics
    
    We now no longer add joysticks at all.  They show up as absolute motion
    devices without has_button, so we don't add them as a pointer.  We may add
    a keyboard for the keyboard-style keys, but that's fine.  With the previous
    commit, we no longer generate spurious absolute pointer motion for the abs
    axes.
    
    https://bugs.freedesktop.org/show_bug.cgi?id=71687


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.