<html>
<head>
<base href="https://bugzilla.gnome.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - gdk_device_get_source: assertion 'GDK_IS_DEVICE (device)' failed"
href="https://bugzilla.gnome.org/show_bug.cgi?id=753185#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - gdk_device_get_source: assertion 'GDK_IS_DEVICE (device)' failed"
href="https://bugzilla.gnome.org/show_bug.cgi?id=753185">bug 753185</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>Created <span class=""><a href="attachment.cgi?id=308683&action=diff" name="attach_308683" title="gdkevent: Hold refs to device/source_device">attachment 308683</a> <a href="attachment.cgi?id=308683&action=edit" title="gdkevent: Hold refs to device/source_device">[details]</a></span> <a href='review?bug=753185&attachment=308683'>[review]</a>
gdkevent: Hold refs to device/source_device
The extra reference will be held from GdkEventPrivate data, so there's
a common place to all events. Without this, events queued after devices/
capabilities disappear (eg. on TTY switch) might hold invalid pointers.
Windowing level operations on those devices (queries, grabs...) are
expected to fail at that time, but we should hold meaningful data for
the regular event handling paths.</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>