Bug 414183 – crash in Rhythmbox Music Player: Plugged in my ipod shuff...

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 414183 - crash in Rhythmbox Music Player: Plugged in my ipod shuff...


Summary:	crash in Rhythmbox Music Player: Plugged in my ipod shuff...


Status:	RESOLVED DUPLICATE of bug 352972

Product:	rhythmbox
Classification:	Other
Component:	general
Version:	0.9.6
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-03-03 11:09 UTC by krusher
Modified:	2007-03-03 11:37 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description krusher 2007-03-03 11:09:36 UTC

What were you doing when the application crashed?
Plugged in my ipod shuffle with rythmbox already loaded and it crashed.			


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 197144576 vsize: 197144576 resident: 24432640 share: 14270464 rss: 24432640 rss_rlim: -1
CPU usage: start_time: 1172920061 rtime: 453 utime: 415 stime: 38 cutime:9 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/rhythmbox'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47005489644512 (LWP 11638)]
[New Thread 1090525520 (LWP 11649)]
(no debugging symbols found)
0x00002ac04ca63eef in waitpid () from /lib/libpthread.so.0

+ Trace 115432

Thread 1 (Thread 47005489644512 (LWP 11638))

#0 waitpid
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 rb_ipod_source_register_type
from /usr/lib/rhythmbox/plugins/ipod/libipod.so
#4 g_closure_invoke
from /usr/lib64/libgobject-2.0.so.0
#5 g_signal_chain_from_overridden
from /usr/lib64/libgobject-2.0.so.0
#6 g_signal_emit_valist
from /usr/lib64/libgobject-2.0.so.0
#7 g_signal_emit
from /usr/lib64/libgobject-2.0.so.0
#8 g_object_class_override_property
from /usr/lib64/libgobject-2.0.so.0
#9 g_object_newv
from /usr/lib64/libgobject-2.0.so.0
#10 g_object_new_valist
from /usr/lib64/libgobject-2.0.so.0
#11 g_object_new
from /usr/lib64/libgobject-2.0.so.0
#12 rb_ipod_source_new
from /usr/lib/rhythmbox/plugins/ipod/libipod.so
#13 register_rb_plugin
from /usr/lib/rhythmbox/plugins/ipod/libipod.so
#14 rb_marshal_OBJECT__OBJECT
#15 g_closure_invoke
from /usr/lib64/libgobject-2.0.so.0
#16 g_signal_chain_from_overridden
from /usr/lib64/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /usr/lib64/libgobject-2.0.so.0
#18 g_signal_emit
from /usr/lib64/libgobject-2.0.so.0
#19 rb_removable_media_manager_queue_transfer
#20 g_closure_invoke
from /usr/lib64/libgobject-2.0.so.0
#21 g_signal_chain_from_overridden
from /usr/lib64/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /usr/lib64/libgobject-2.0.so.0
#23 g_signal_emit
from /usr/lib64/libgobject-2.0.so.0
#24 gnome_vfs_volume_monitor_client_get_type
from /usr/lib64/libgnomevfs-2.so.0
#25 dbus_connection_dispatch
from /usr/lib64/libdbus-1.so.3
#26 dbus_server_setup_with_g_main
from /usr/lib64/libdbus-glib-1.so.2
#27 g_main_context_dispatch
from /usr/lib64/libglib-2.0.so.0
#28 g_main_context_check
from /usr/lib64/libglib-2.0.so.0
#29 g_main_loop_run
from /usr/lib64/libglib-2.0.so.0
#30 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#31 main
#0 waitpid
from /lib/libpthread.so.0

Comment 1 James "Doc" Livingston 2007-03-03 11:37:34 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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