Bug#836426: Caused by libgtk-3-0 3.21

[Josh Triplett]

On Thu, Sep 08, 2016 at 02:24:37AM +0200, Michael Biebl wrote:
> On Wed, 7 Sep 2016 09:21:55 -0700 Josh Triplett <josh at joshtriplett.org>
> wrote:
> > Control: reassign -1 libgtk-3-0 3.21.5-3
> > Control: affects -1 gnome-boxes
> > Control: severity -1 serious
> > Control: forcemerge -1 832077
> 
> To me those two issues look not like they are related.
> 
> After all, this one was file for 3.20, the other one for 3.21.

Both bugs were filed for libgtk-3-0 3.21.  (836426 was originally filed
on gnome-boxes 3.20 but running with libgtk-3-0 3.21, and I can confirm
that the issue disappears when downgrading to libgtk-3-0 3.20 and
reappears when upgrading to libgtk-3-0 3.21.  All three mails in 832077
specifically mentioned libgtk-3-0 3.21.)  None of the reports apply to
libgtk-3-0 3.20.

I changed the applicable version number when reassigning to libgtk-3-0,
and as far as I can tell that did update the BTS metadata correctly.

> The severity seems overinflated as well.

It seems appropriate for an issue that causes window contents to fail to
render, making gnome-boxes unusable with that version of GTK+.  It also
seems appropriate for what looks like a backwards-compatibility issue in
GTK+.  "serious" seems appropriate for "this shouldn't get released in
the next stable release".