<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Cursors for Wacom tablets are not always updated correctly under Wayland" href="https://bugzilla.gnome.org/show_bug.cgi?id=785375#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Cursors for Wacom tablets are not always updated correctly under Wayland" href="https://bugzilla.gnome.org/show_bug.cgi?id=785375">bug 785375</a> from <a href="page.cgi?id=describeuser.html&login=killertofu%40gmail.com" title="Jason Gerecke <killertofu@gmail.com>"> Jason Gerecke</a> <pre>(In reply to Carlos Garnacho from <a href="show_bug.cgi?id=785375#c8">comment #8</a>) > Ah I see, then it falls on the "no zwp_tablet support" case, totally > expected :). FWIW, it's also the same with clients failing to call > wl_pointer.set_cursor, on mutter and weston, the last cursor remains set. It > can be seen just launching a client from a terminal, freezing it with ctrl-z > and hovering it. > > I guess mutter could set a more appropriate cursor if no zwp_tablet > supporting client is underneath, maybe the "forbidden sign" one, since input > will be broken anyway... Feel free to file a bug for that. My prior comment must have been confusing... I *do* have the zwp_tablet patches (running `xinput list` shows "xwayland-stylus" and friends, and `xinput test-xi2` reports proper pressure-sensitive events) but *still* see the stale cursor when entering an xwayland window.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>