rhythmbox crashed with SIGSEGV in g_object_notify_queue_thaw()

[Joel Welling]

Binary package hint: rhythmbox

I was playing "radio", specifically Paradise Radio, through earphones. The crash occurred when I set the volume to zero via the slider and then attempted to raise it again.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Thu Nov 5 12:30:27 2009
Disassembly: 0x0: Cannot access memory at address 0x0
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/rhythmbox
NonfreeKernelModules: fglrx
Package: rhythmbox 0.12.5-0ubuntu4
ProcCmdline: rhythmbox
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/usr/bin/tcsh
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? ()
 g_object_notify_queue_thaw (object=0x2480000,
 IA__g_object_set_valist (object=0x2480000, first_property_name=0x0,
 IA__g_object_set (_object=0x2480000,
 gst_play_sink_set_volume (playsink=0x2320100,
Title: rhythmbox crashed with SIGSEGV in g_object_notify_queue_thaw()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:2857): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:2857): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:2932): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:2991): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Apport retracing service (apport)]

StacktraceTop:?? ()
g_object_set_valist ()
g_object_set () from /usr/lib/libgobject-2.0.so.0
gst_play_sink_set_volume (playsink=0x2320100,
g_object_set_valist ()

[Pedro Villavicencio (pedro)]

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.