rhythmbox crashed with SIGSEGV in soup_connection_disconnect()

[kyleabaker]

Binary package hint: rhythmbox

This bug is the same error given for #181054, #133044 and #179629. I'm reporting this as a new bug since they were concluded invalid and incomplete.

At the time of the crash, Rhythmbox was playing straight down the list of my songs. I'm not sure what song it was on when it crashed, my screensavers had already cut off and the monitors were in sleep mode. My library is ~20,000 songs. Not sure if that has anything to do with it or not.

ProblemType: Crash
Architecture: amd64
Date: Fri Jan 11 08:02:18 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/rhythmbox
NonfreeKernelModules: nvidia
Package: rhythmbox 0.11.4-0ubuntu2
PackageArchitecture: amd64
ProcCmdline: rhythmbox
ProcCwd: /home/kyleabaker
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=C
 SHELL=/bin/bash
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 soup_connection_disconnect ()
 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: rhythmbox crashed with SIGSEGV in soup_connection_disconnect()
Uname: Linux kyleabaker-desktop 2.6.24-2-generic #1 SMP Thu Dec 20 17:58:55 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:soup_connection_disconnect (conn=0x1ca6420) at soup-connection.c:703
IA__g_closure_invoke (closure=0xc30b80, return_value=0x0, n_param_values=1,
signal_emit_unlocked_R (node=0x1cee740, detail=0, instance=0x1fd6e30,
IA__g_signal_emit_valist (instance=0x1fd6e30, signal_id=<value optimized out>,
IA__g_signal_emit (instance=0x2ba46f26dd68, signal_id=0, detail=1743485352)

[Pedro Villavicencio (pedro)]

Thanks for your report, that's known upstream you can track it here: http://bugzilla.gnome.org/show_bug.cgi?id=506552

[Wouter Stomp (wouterstomp-deactivatedaccount)]

This has been fixed upstream in svn.

[Timo Aaltonen (tjaalton)]

Fixed in 2.4.1-1.