Bug#578992: reportbug crashes after sending bug report via SMTP (gtk2 frontend)
Sandro Tosi
morph at debian.org
Sat Apr 24 10:44:03 UTC 2010
Hello Tobias,
please keep all the recipients in replies, so everyone is informed of progress.
On Sat, Apr 24, 2010 at 12:13, Tobias Ramforth <tobias.ramforth at udo.edu> wrote:
> On 24.04.2010 11:32, Sandro Tosi wrote:
>> tags 578992 unreproducible
>> thanks
>>
>> Hello Tobias,
>> thanks for your report.
> Hello Sandro,
>
> thanks for looking into it!
you're welcome
>>> After transferring the bug report,
>>
>> do you mean after "Submit the bug report via email"?
> Yes, exactly. After that the bug report gets transferred but reportbug
> crashes.
>
>> Anyhow, I can't replicate your report in an unstable system.
> It crashed here after submitting a bug report for gconf2 however after
> submitting the bugreport for reportbug it did not crash.
I tried it with gconf2 too, and works fine here.
>> The gdb backtrace makes me think there is a problem with your GTK+
>> stack, and since you're using testing that might be the main cause.
>> Did you try to contact the GTK+ maintainer? I'm adding them in the
>> loop, so they can inspect it (I'll reassign to them in some days in
>> case of no reply will come).
> No, I did not contact them as I thought - inspecting the generated eror
> report - that the bug did not have anything to do with GTK2.
> Maybe I overlooked something.
Well, reporbug is in python, the traceback is for C code, inside
pango/glib/libgtk, so the problem seems to be in the libraries
reportbug uses not in reportbug itself.
Regards,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
More information about the pkg-gnome-maintainers
mailing list