[Wayland-bugs] [Bug 98904] Race condition when mouse and/or keyboard randomly doesn't work upon fresh boot - Thinkpad Yoga S1
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Nov 29 18:20:19 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=98904
Bug ID: 98904
Summary: Race condition when mouse and/or keyboard randomly
doesn't work upon fresh boot - Thinkpad Yoga S1
Product: Wayland
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: libinput
Assignee: wayland-bugs at lists.freedesktop.org
Reporter: duffy at redhat.com
libinput version: 1.5.1
libinput 1.5.1-1.fc25.x86_64
My Thinkpad Yoga S1 has a weird race condition on bootup affecting input
drivers - maybe 3 out of every 5 boots, the system boots with no working mouse
and/or keyboard. I just reboot again and it works fine, although sometimes it
takes several boots to get both working.
This happened since I got the laptop and loaded it with F23... I upgraded to
F25 + Wayland today and was able to reproduce the issue.
The following are input settings for all devices on the system when it is in
the state where upon boot the keyboard worked but the pointer did not:
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer
(2)]
⎜ ↳ xwayland-touch:13 id=7 [slave pointer
(2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard
(3)]
↳ xwayland-keyboard:13 id=6 [slave keyboard
(3)]
Device 'Virtual core pointer':
Device Enabled (119): 1
Coordinate Transformation Matrix (121): 1.000000, 0.000000, 0.000000,
0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
Device 'Virtual core XTEST pointer':
Device Enabled (119): 1
Coordinate Transformation Matrix (121): 1.000000, 0.000000,
0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
XTEST Device (238): 1
Device 'xwayland-touch:13':
Device Enabled (119): 1
Coordinate Transformation Matrix (121): 1.000000, 0.000000, 0.000000,
0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
Device Accel Profile (242): 0
Device Accel Constant Deceleration (243): 1.000000
Device Accel Adaptive Deceleration (244): 1.000000
Device Accel Velocity Scaling (245): 10.000000
Device 'Virtual core keyboard':
Device Enabled (119): 1
Coordinate Transformation Matrix (121): 1.000000, 0.000000,
0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
Device 'Virtual core XTEST keyboard':
Device Enabled (119): 1
Coordinate Transformation Matrix (121): 1.000000, 0.000000, 0.000000,
0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
XTEST Device (238): 1
Device 'xwayland-keyboard:13':
Device Enabled (119): 1
Coordinate Transformation Matrix (121): 1.000000, 0.000000,
0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
I couldn't run evemu on the pointer because there wasn't a deviec for it if I
understand correctly, just for the touchscreen. If I reboot the system so the
mouse works again, and run xinput list, i get a pointer and relative-pointer
device that wasn't there before:
RL: http://paste.fedoraproject.org/493306/14804435/
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer
(2)]
⎜ ↳ xwayland-pointer:13 id=6 [slave pointer
(2)]
⎜ ↳ xwayland-relative-pointer:13 id=7 [slave pointer
(2)]
⎜ ↳ xwayland-touch:13 id=9 [slave pointer
(2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard
(3)]
↳ xwayland-keyboard:13 id=8 [slave keyboard
(3)]
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/wayland-bugs/attachments/20161129/b1dbde71/attachment-0001.html>
More information about the wayland-bugs
mailing list