<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Touchscreen function broken on F24 Alpha" href="https://bugs.freedesktop.org/show_bug.cgi?id=95169#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Touchscreen function broken on F24 Alpha" href="https://bugs.freedesktop.org/show_bug.cgi?id=95169">bug 95169</a> from <a class="email" href="mailto:killertofu@gmail.com" title="Jason Gerecke <killertofu@gmail.com>"> Jason Gerecke</a> <pre>(In reply to Robert de Rooy from <a href="show_bug.cgi?id=95169#c12">comment #12</a>) > Also, when I say touch does not work, what I see is one of the following; > - touch causes mouse cursor to disappear, but I cannot interact with anything > OR > - mouse cursor follows finger for a bit, then vanishes, but again no > interaction with anything on screen is possible > This (along with the provided hid-recorder dumps) strongly suggests that the kernel driver is working well enough and that the problem may be in userspace. I don't see anything strange when replaying the "broken" event stream locally, but that doesn't mean a whole lot. You might try uninstalling the xf86-input-wacom driver to see if the evdev / libinput driver works correctly with the touchscreen. In the meantime, I'll try to grab a copy of the F24 alpha to see if replaying the event stream within it works any differently than on my current box. > I also guess the pen not working in Wayland is a separate issue from the > above. Wayland pen support is still a work in progress. We recently had a protocol for stylus events accepted, but there's still additional protocol to finalize and then work to implement everything in the various compositors. Its slow going, but definitely in the works :)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>