<html>
<head>
<base href="https://bugzilla.gnome.org/" />
</head>
<body>
<p>
<div>
<b><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#c8">Comment # 8</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 <span class="vcard"><a href="page.cgi?id=describeuser.html&login=carlosg%40gnome.org" title="Carlos Garnacho <carlosg@gnome.org>"> <span class="fn">Carlos Garnacho</span></a>
</span></b>
<pre>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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>