https://bugs.freedesktop.org/show_bug.cgi?id=71687
Priority: medium
Bug ID: 71687
Assignee: [email protected]
Summary: Wayland fails to detect Microsoft SideWinder x3 mouse
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: [email protected]
Hardware: x86-64 (AMD64)
Status: NEW
Version: 1.3.0
Component: wayland
Product: Wayland
Created attachment 89342
--> https://bugs.freedesktop.org/attachment.cgi?id=89342&action=edit
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.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Wayland-bugs mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/wayland-bugs
