<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - kernel: Improve Surface Pro Type Cover 2 support"
href="https://bugs.freedesktop.org/show_bug.cgi?id=99079#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - kernel: Improve Surface Pro Type Cover 2 support"
href="https://bugs.freedesktop.org/show_bug.cgi?id=99079">bug 99079</a>
from <span class="vcard"><a class="email" href="mailto:defree@gmail.com" title="defree@gmail.com">defree@gmail.com</a>
</span></b>
<pre>First, about the touchscreen problem, I confirm it is related to handling of
events higher in the stack (works fine with a clean gnome-shell 3.22, fails
under some circumstances with other GTK apps or Chrome...). Solved as far as
input system is concerned :).
I tested with 4.10-rc2 (not manually built but taken from Manjaro's unstable
repository). Behavior is quite chaotic. I will try to summarize:
- regression on suspend/resume (4.9 release has the best/correct behavior)
- USB initialization is indeed different, but unreliable.
Cursor behavior is changed:
1) Tap-to-click no longer works (but according to our discussion, it used to be
hardware emulation).
2) Movement is still relative but in a weird way. As if coordinates delta were
interpreted in a wrong system (the closest I felt was with a wacom mouse which
movement was interpreted relative to the tablet and not to the orientation of
the mouse itself).
3) Yet libinput-list-devices and xinput list-props reports are the same.
Furthermore, on kernel side device initialization works rarely:
- I have to plug/unplug many times or reboot the device to get it initialized.
- after being initialized with 4.10 kernel, the changes in behavior survive a
reboot and change to kernel 4.9. I have to unplug the usb or power off the
system to get back to the clean behavior.
This "reboot survival" surprised me the most but I was able to reproduce
multiple times.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>