rhythmbox crashed with SIGSEGV in rhythmdb_entry_delete()

[Scott Sweeny]

Binary package hint: rhythmbox

This bug was encountered as rhythmbox was scanning the library upon startup. The files had changed quite a bit since the last time rhythmbox had been run.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/rhythmbox
NonfreeKernelModules: nvidia
Package: rhythmbox 0.11.6svn20081008-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: rhythmbox
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/librhythmbox-core.so.0
 ?? () from /usr/lib/librhythmbox-core.so.0
 ?? () from /usr/lib/librhythmbox-core.so.0
 rhythmdb_entry_delete ()
Title: rhythmbox crashed with SIGSEGV in rhythmdb_entry_delete()
Uname: Linux 2.6.27-7-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy kvm libvirtd lpadmin netdev plugdev powerdev pulse-access scanner vboxusers video

[Apport retracing service (apport)]

StacktraceTop:?? () from /usr/lib/librhythmbox-core.so.0
?? () from /usr/lib/librhythmbox-core.so.0
?? () from /usr/lib/librhythmbox-core.so.0
rhythmdb_entry_delete () from /usr/lib/librhythmbox-core.so.0
?? () from /usr/lib/librhythmbox-core.so.0

[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.

[Pedro Villavicencio (pedro)]

may you please install the following packages: libglib2.0-0-dbgsym, rhythmbox-dbgsym, libgtk2.0-0-dbgsym, libdbus-1-3-dbgsym and libtotem-plparser12-dbgsym, and get a new trace? the one submitted previously is missing a couple of symbols that'd be nice to have, thanks in advance.

[Scott Sweeny (ssweeny)]

As you wish.

[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.