Bug 1194469

Summary: Microsoft mouse not recognized on GNOME with Wayland
Product: [Fedora] Fedora Reporter: Bernardo Donadio <bcdonadio>
Component: libinputAssignee: Peter Hutterer <peter.hutterer>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 21CC: awilliam, bcdonadio, peter.hutterer, satellitgo
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: libinput-0.7.0-3.20141211git58abea394.fc21 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-06 07:00:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
evemu-describe output of mouse
none
evemu-record output of mouse none

Description Bernardo Donadio 2015-02-19 22:08:26 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-20 00:02:56 UTC 
record the device with evemu-record please and attach it here.

http://www.freedesktop.org/wiki/Evemu
Comment 2 Bernardo Donadio 2015-02-26 05:38:02 UTC 
Created attachment 995464 [details]
evemu-describe output of mouse

The attached file is the output of

$ sudo evemu-describe /dev/input/event18

and event18 is the event related to the mouse part of the wireless bundle, according to /proc/bus/input/devices:

I: Bus=0003 Vendor=045e Product=009d Version=0111
N: Name="Microsoft Microsoft Wireless Optical Desktop® 2.10"
P: Phys=usb-0000:00:12.0-5/input0
S: Sysfs=/devices/pci0000:00/0000:00:12.0/usb4/4-5/4-5:1.0/0003:045E:009D.0006/input/input20
U: Uniq=
H: Handlers=sysrq kbd event17 
B: PROP=0
B: EV=120013
B: KEY=1000000000007 ff800000000007ff febeffdff3cfffff fffffffffffffffe
B: MSC=10
B: LED=107

I: Bus=0003 Vendor=045e Product=009d Version=0111
N: Name="Microsoft Microsoft Wireless Optical Desktop® 2.10"
P: Phys=usb-0000:00:12.0-5/input1
S: Sysfs=/devices/pci0000:00/0000:00:12.0/usb4/4-5/4-5:1.1/0003:045E:009D.0007/input/input21
U: Uniq=
H: Handlers=sysrq kbd mouse2 event18 
B: PROP=0
B: EV=10001f
B: KEY=3f0003007f 0 0 4c3ffff17aff32d bf54445600000000 c000000001f0001 130f938b17c007 ffff7bfad951dfff febeffdfffefffff fffffffffffffffe
B: REL=fc3
B: ABS=ffffff01000701ff
B: MSC=10
Comment 3 Bernardo Donadio 2015-02-26 05:52:23 UTC 
Created attachment 995465 [details]
evemu-record output of mouse

This is the evemu-record output (with the describe part omitted) while running on Gnome on wayland of some clicking and moving.
Comment 4 Fedora Update System 2015-02-26 07:39:19 UTC 
libinput-0.7.0-3.20141211git58abea394.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/libinput-0.7.0-3.20141211git58abea394.fc21
Comment 5 Adam Williamson 2015-02-26 20:27:02 UTC 
This seems like something we should probably pull into Alpha? Not being able to move the mouse is bad. Nominating as an FE.
Comment 6 Bernardo Donadio 2015-02-27 05:57:45 UTC 
I confirm that libinput-0.7.0-3.20141211git58abea394.fc21 solves the problem.
Comment 7 Fedora Update System 2015-02-27 09:23:38 UTC 
Package libinput-0.7.0-3.20141211git58abea394.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libinput-0.7.0-3.20141211git58abea394.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-2699/libinput-0.7.0-3.20141211git58abea394.fc21
then log in and leave karma (feedback).
Comment 8 Adam Williamson 2015-03-02 20:39:25 UTC 
Actually the fix for this should be in libinput 0.11.0 in F22 already, so I withdraw the F22 FE proposal. (It landed upstream between 0.8.0 and 0.9.0.)
Comment 9 Peter Hutterer 2015-03-03 21:24:45 UTC 
yeah, that fix is in F22 already, this was a backport. F21 has an older version of libinput, F22 is almost upstream master.
Comment 10 Fedora Update System 2015-03-06 07:00:06 UTC 
libinput-0.7.0-3.20141211git58abea394.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.