<html>
<head>
<base href="https://bugzilla.gnome.org/" />
</head>
<body><span class="vcard"><a href="page.cgi?id=describeuser.html&login=mclasen%40redhat.com" title="Matthias Clasen <mclasen@redhat.com>"> <span class="fn">Matthias Clasen</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED OBSOLETE - with wayland and gtk_window_begin_move_drag there's apparently no way to track where the window is"
href="https://bugzilla.gnome.org/show_bug.cgi?id=768128">bug 768128</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEEDINFO
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>OBSOLETE
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED OBSOLETE - with wayland and gtk_window_begin_move_drag there's apparently no way to track where the window is"
href="https://bugzilla.gnome.org/show_bug.cgi?id=768128#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED OBSOLETE - with wayland and gtk_window_begin_move_drag there's apparently no way to track where the window is"
href="https://bugzilla.gnome.org/show_bug.cgi?id=768128">bug 768128</a>
from <span class="vcard"><a href="page.cgi?id=describeuser.html&login=mclasen%40redhat.com" title="Matthias Clasen <mclasen@redhat.com>"> <span class="fn">Matthias Clasen</span></a>
</span></b>
<pre>As announced a while ago, we are migrating to gitlab, and bugs that haven't
seen activity in the last year or so will be not be migrated, but closed out in
bugzilla.
If this bug is still relevant to you, you can open a new issue describing the
symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:
<a href="https://gitlab.gnome.org/GNOME/gtk/issues/new">https://gitlab.gnome.org/GNOME/gtk/issues/new</a></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>