Bug 372591 – crash in Rhythmbox Music Player: plugged my ipod in

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 372591 - crash in Rhythmbox Music Player: plugged my ipod in


Summary:	crash in Rhythmbox Music Player: plugged my ipod in


Status:	RESOLVED DUPLICATE of bug 358855

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:	2006-11-08 18:46 UTC by miffy
Modified:	2006-11-09 00:11 UTC

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

Description miffy 2006-11-08 18:46:38 UTC

What were you doing when the application crashed?
plugged my ipod in


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

Memory status: size: 68202496 vsize: 0 resident: 68202496 share: 0 rss: 19996672 rss_rlim: 0
CPU usage: start_time: 1163011545 rtime: 0 utime: 272 stime: 0 cutime:256 cstime: 0 timeout: 16 it_real_value: 0 frequency: 5

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1228654928 (LWP 5738)]
[New Thread -1261556832 (LWP 5752)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 84453

Thread 1 (Thread -1228654928 (LWP 5738))

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

Comment 1 André Klapper 2006-11-09 00:11:26 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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