Bug 603405 – Rhythmbox crashes when new CD inserted

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 603405 - Rhythmbox crashes when new CD inserted


Summary:	Rhythmbox crashes when new CD inserted


Status:	RESOLVED DUPLICATE of bug 597706

Product:	rhythmbox
Classification:	Other
Component:	general
Version:	0.12.x
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	RhythmBox Maintainers
QA Contact:	RhythmBox Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-11-30 19:34 UTC by Pedro Villavicencio
Modified:	2009-12-01 09:45 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Pedro Villavicencio 2009-11-30 19:34:12 UTC

this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/rhythmbox/+bug/475074

"Rhythym box seems to work fine until I eject a CD (by left clicking on the Eject button) and insert a new one. It will display the new CD title and track info, but crashes when I try to play or rip."

rhythmbox version is: 0.12.5-0ubuntu4

".

+ Trace 219380

Thread 1 (process 6652)

#0 g_object_get
from /usr/lib/libgobject-2.0.so.0
#1 get_db_for_source
at rb-audiocd-source.c line 151
#2 rb_audiocd_source_cmd_reload_metadata
at rb-audiocd-source.c line 586
#3 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#4 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#5 ??
from /usr/lib/libgobject-2.0.so.0
#6 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#7 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#8 _gtk_action_emit_activate
at /build/buildd/gtk+2.0-2.18.3/gtk/gtkaction.c line 727
#9 IA__gtk_action_activate
at /build/buildd/gtk+2.0-2.18.3/gtk/gtkaction.c line 757
#10 button_clicked
at /build/buildd/gtk+2.0-2.18.3/gtk/gtktoolbutton.c line 705
#11 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#12 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#13 ??
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#16 IA__gtk_button_clicked
at /build/buildd/gtk+2.0-2.18.3/gtk/gtkbutton.c line 1111
#17 gtk_real_button_released
at /build/buildd/gtk+2.0-2.18.3/gtk/gtkbutton.c line 1707
#18 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#19 ??
from /usr/lib/libgobject-2.0.so.0
#20 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#21 ??
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#24 IA__gtk_button_released
at /build/buildd/gtk+2.0-2.18.3/gtk/gtkbutton.c line 1103
#25 gtk_button_button_release
at /build/buildd/gtk+2.0-2.18.3/gtk/gtkbutton.c line 1599
#26 _gtk_marshal_BOOLEAN__BOXED
at /build/buildd/gtk+2.0-2.18.3/gtk/gtkmarshalers.c line 84
#27 ??
from /usr/lib/libgobject-2.0.so.0
#28 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#29 ??
from /usr/lib/libgobject-2.0.so.0
#30 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#31 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#32 gtk_widget_event_internal
at /build/buildd/gtk+2.0-2.18.3/gtk/gtkwidget.c line 4767
#33 IA__gtk_propagate_event
at /build/buildd/gtk+2.0-2.18.3/gtk/gtkmain.c line 2417
#34 IA__gtk_main_do_event
at /build/buildd/gtk+2.0-2.18.3/gtk/gtkmain.c line 1622
#35 gdk_event_dispatch
at /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkevents-x11.c line 2369
#36 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#37 ??
from /lib/libglib-2.0.so.0
#38 g_main_loop_run
from /lib/libglib-2.0.so.0
#39 IA__gtk_main
at /build/buildd/gtk+2.0-2.18.3/gtk/gtkmain.c line 1218
#40 main
at main.c line 332

Comment 1 Jonathan Matthew 2009-12-01 09:45:24 UTC

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.

*** This bug has been marked as a duplicate of bug 597706 ***