On Fri, 13 Jan 2017 at 15:18:26 -0500, Sandro Tosi wrote:
> would you be able to have a look at this? it looks like it's the
> current issue every user of the GTK interface has.
The patch from James looks correct, please apply it.
> On Mon, Jan 9, 2017 at 2:21 PM, James Clarke <jrt...@debian.org> wrote:
> > This is because, while a lot of the constructors have been overridden by
> > PyGObject to handle the deprecated form, Expander has not been
> > overridden, so the explicit form has to be used. Patch attached.
> > Unfortunately, after applying it, it now crashes with:
> >
> >> (reportbug:15278): Gtk-CRITICAL **: gtk_text_attributes_ref: assertion
> >> 'values != NULL' failed
> >>
> >> (reportbug:15278): Gtk-CRITICAL **: gtk_text_attributes_ref: assertion
> >> 'values != NULL' failed
> >>
> >> (reportbug:15278): Pango-CRITICAL **: pango_layout_new: assertion
> >> 'context != NULL' failed
> >> [1] 15278 segmentation fault reportbug src:pymongo
I don't get this error myself (with
"PYTHONPATH=. bin/reportbug -u gtk2 reportbug").
> > I would guess there are some UI
> > interactions happening not on the main UI thread.
I found a couple of places where this was done wrong. I'll send a
patch series soon.
S
_______________________________________________
Reportbug-maint mailing list
Reportbug-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
