[Reportbug-maint] Bug#850733: Bug#850733: Crashes with "TypeError: GObject.__init__() takes exactly 0 arguments (1 given)"
Sandro Tosi
morph at debian.org
Fri Jan 13 20:18:26 UTC 2017
Hey Simon,
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. thanks in advance!
On Mon, Jan 9, 2017 at 2:21 PM, James Clarke <jrtc27 at debian.org> wrote:
> Package: reportbug
> Version: 7.1.2
> Tags: patch
> Severity: important
>
> When I try to use the GTK3 backend to report a bug, I get the following
> stack trace:
>
>> Traceback (most recent call last):
>> File "/usr/bin/reportbug", line 2233, in <module>
>> main()
>> File "/usr/bin/reportbug", line 1107, in main
>> return iface.user_interface()
>> File "/usr/bin/reportbug", line 2149, in user_interface
>> package, severity, mode, charset=charset, tags=tags)
>> File "/usr/bin/reportbug", line 182, in handle_editing
>> editor, charset)
>> File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 1561, in func
>> op = klass(parent)
>> File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 539, in __init__
>> self.widget = self.create_widget()
>> File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 1173, in create_widget
>> expander = Gtk.Expander("Other system information")
>> TypeError: GObject.__init__() takes exactly 0 arguments (1 given)
>
> 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
>
> Putting in prints doesn't seem to help; the exact location is
> non-deterministic from what I can tell. I would guess there are some UI
> interactions happening not on the main UI thread.
>
> Regards,
> James
>
> _______________________________________________
> Reportbug-maint mailing list
> Reportbug-maint at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi
More information about the Reportbug-maint
mailing list