Bug 89235 - Microsoft mouse not recognized on GNOME with Wayland
Summary: Microsoft mouse not recognized on GNOME with Wayland
Status: RESOLVED FIXED
Alias: None
Product: Wayland
Classification: Unclassified
Component: libinput (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: high major
Assignee: Wayland bug list
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-19 22:17 UTC by Bernardo Donadio
Modified: 2015-03-04 05:05 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Bernardo Donadio 2015-02-19 22:17:40 UTC 
Description of problem:
The Microsoft Wireless Optical Desktop 3.0 mouse isn't being recognized by GNOME on Wayland. The USB ID is 045e:009d. GNOME on Wayland works fine with other mouse+keyboard wireless bundles, like the Logitech (Holtek) with the USB ID 04d9:a01c.


Version-Release number of selected component (if applicable): 
libinput-0.7.0.x86_64 (2.20141211git58abea394.fc21)
mutter-3.14.3.x86_64 (1.fc21)


How reproducible: Always, at least on this system.


Steps to Reproduce:
1. Have the said mouse connected.
2. Start the "GNOME on Wayland" session trough gdm.
3. Try to move the said mouse.

Actual results:
It will not move/click, altough it recognizes keyboard input and mouse input from other vendors.

Expected results:
Out-of-the-box working mouse support for all USB HID-compliant mouses.

Additional info:
Additional GPU is also not being recognized (I will open another bug for this, which is waaaaay more complex).
Comment 1 Peter Hutterer 2015-02-25 05:42:57 UTC 
Please run evemu-describe against the device and attach the output here.
Comment 2 Peter Hutterer 2015-03-04 05:05:01 UTC 
commit 0afd0b792fb9c244442ac4532ceeaa9565dd1928
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Wed Jan 21 12:04:48 2015 +0100

    evdev: Be more careful about what we consider a joystick

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.