Summary: | Wacom tablet not found by Gnome 3.22 | ||
---|---|---|---|
Product: | Wayland | Reporter: | camalot |
Component: | libinput | Assignee: | Wayland bug list <wayland-bugs> |
Status: | RESOLVED NOTOURBUG | QA Contact: | |
Severity: | major | ||
Priority: | medium | CC: | peter.hutterer |
Version: | 1.5.0 | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Output of libinput-list-devices
evemu-record of pen attempting to interact with windows Output from libwacom-list-local-devices, looks sane to me. |
Description
camalot
2016-10-14 18:17:28 UTC
Created attachment 127307 [details]
Output of libinput-list-devices
Created attachment 127308 [details]
evemu-record of pen attempting to interact with windows
when the tablet is plugged in, what does libwacom-list-local-devices say? and does libinput-debug-events look sane? i.e. getting events for the tablet, etc. I don't believe that gnome-settings-daemon and gnome-control-center have yet been updated to work with tablets under Wayland. Additionally, there are a lot of applications that simply won't work with tablets at this time until their toolkits start supporting Wayland or until Xwayland supports tablets (see https://plus.google.com/117863863653209681821/posts/7w9USq3fPZ9 -- mea culpa for getting distracted from my Xwayland patches). The "shell" bits of GNOME (e.g. the Activities menu, window decorations, etc.) should usually work from what I understand, though I've had occasional issues with them as well. Created attachment 127371 [details]
Output from libwacom-list-local-devices, looks sane to me.
Jason, thank you for the clarity about what's going on in your comment and the linked Google+ post. That really helps. I had thought from the announcement that tablets work under Wayland/libinput in Gnome 3.22 that they the really did work. Seems like there is a ways to go. If you are aware of a good place to keep tabs on progress on this I would appreciate a pointer, and if there is anything I can help with testing I'd be happy to do it. I'm going to close this issue since I don't see anything that seems wrong on the libinput side, with events being reported by libinput-debug-events and so on. |
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.