rhythmbox crashed with SIGSEGV in g_type_create_instance()

[Nicholas Marquez]

Binary package hint: rhythmbox

*sigh* Another GObject failure. Anyway, this came about when I returned after an hour to my computer. It was running a screensaver. These factors are likely not involved in this crash at all.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Thu Feb 28 17:41:44 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/rhythmbox
NonfreeKernelModules: nvidia
Package: rhythmbox 0.11.4-0ubuntu6 [modified: usr/lib/rhythmbox/rhythmbox-metadata usr/lib/librhythmbox-core.so.0.0.0 usr/bin/rhythmbox usr/bin/rhythmbox-client]
PackageArchitecture: amd64
ProcCmdline: rhythmbox
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 g_type_create_instance ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_object_newv () from /usr/lib/libgobject-2.0.so.0
 g_object_new_valist ()
 g_object_new () from /usr/lib/libgobject-2.0.so.0
Title: rhythmbox crashed with SIGSEGV in g_type_create_instance()
Uname: Linux 2.6.24-10-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse games gdm lpadmin plugdev pulse pulse-access pulse-rt sambashare scanner sudo tape users video voice

[Apport retracing service (apport)]

StacktraceTop:g_object_constructor (type=1, n_construct_properties=0,
IA__g_object_newv (object_type=37652768, n_parameters=0,
IA__g_object_new_valist (object_type=37652768, first_property_name=0x0,
IA__g_object_new (object_type=37652768, first_property_name=0x0)
?? ()

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Kjell Braden (afflux)]

I'll mark this bug as a duplicate of bug 199319, as it contains a valid stacktrace and a testcase. Please note that any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

Thanks,