rhythmbox crashed with SIGFPE in g_hash_table_lookup()

[smanofsteel76]

Binary package hint: rhythmbox

No further info.

ProblemType: Crash
Architecture: amd64
Date: Tue Mar 2 12:08:34 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: rhythmbox 0.12.7-0ubuntu3
ProcCmdline: rhythmbox
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-15.22-generic
Signal: 8
SourcePackage: rhythmbox
StacktraceTop:
 g_hash_table_lookup () from /lib/libglib-2.0.so.0
 rb_refstring_new ()
 ?? () from /usr/lib/librhythmbox-core.so.0
 ?? () from /lib/libglib-2.0.so.0
 start_thread () from /lib/libpthread.so.0
Title: rhythmbox crashed with SIGFPE in g_hash_table_lookup()
Uname: Linux 2.6.32-15-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1904): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (bluetooth-applet:1905): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed
 (gnome-power-manager:1908): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed

[Apport retracing service (apport)]

StacktraceTop:
 g_hash_table_lookup () from /lib/libglib-2.0.so.0
 rb_refstring_new (
 action_thread_main (db=0x13760f0) at rhythmdb.c:2746
 ?? () from /lib/libglib-2.0.so.0
 start_thread () from /lib/libpthread.so.0

[Pedro Villavicencio (pedro)]

Thanks for the report, this looks pretty similar to bug 284970 ; may you tell us a few easy steps in order to reproduce the crash? Thanks in advance.

[MunkyJunky (munkyjunky-deactivatedaccount)]

Got this crash when I quit Rhythmbox - it appeared to close correctly, but then the crash report.

[Vish (vish)]

Could someone facing the bug mention the steps to reproduce this bug?

[Bernd Laser (bernd-laser)]

It seemed to crash because of re-reading my music collection.

[Victor Vargas (kamus)]

smanofsteel76, any news about this issue?