transmission crashed with SIGSEGV in g_closure_invoke()

[scamper]

Binary package hint: transmission

i was trying to get upnp to work with transmission on my wrt54g router.
while transmission was running, i disabled upnp on the router (with the intention of restarting it).
As soon as I did that, transmission crashed.

The auto bug report tool collected information about the crash and sent it in.

ProblemType: Crash
Architecture: amd64
Date: Tue Feb 26 02:24:52 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/transmission
NonfreeKernelModules: nvidia
Package: transmission-gtk 1.05-0ubuntu1
PackageArchitecture: amd64
ProcCmdline: transmission
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: transmission
StacktraceTop:
 ?? () from /usr/lib/gtk-2.0/modules/libgail.so
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
Title: transmission crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.24-8-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev scanner vboxusers video

[Apport retracing service (apport)]

StacktraceTop:IA__g_closure_invoke (closure=0xc8c7c0, return_value=0x0, n_param_values=4,
signal_emit_unlocked_R (node=0x7f0540, detail=0, instance=0x761480,
IA__g_signal_emit_valist (instance=0x761480, signal_id=<value optimized out>,
IA__g_signal_emit (instance=0x7fffe5493700, signal_id=7125744, detail=32)
msgwin_update () at msgwin.c:117

[Charles Kerr (charlesk)]

This looks like it's a crash in the message log GtkTextView widget... the message log's been rewritten for 1.10 and now uses a GtkTreeView. Could you try the same steps with your router while running 1.10b1 to see if the problem persists?

[scamper (scamper-22)]

Well I could not repo this bug on 1.10b1...but I also could not repo on 1.06 now.

But if the trace indicates the logger bug and that's been fixed in 1.10b1...i think we can dupe this one.

[Charles Kerr (charlesk)]

I've tied this to the upstream ticket that prompted the message window rewrite.

[Kevin (kevin64-deactivatedaccount)]

Fix released in Intrepid