Bug 384717 – crash in Rhythmbox Music Player: I now know what crashed ...

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 384717 - crash in Rhythmbox Music Player: I now know what crashed ...


Summary:	crash in Rhythmbox Music Player: I now know what crashed ...


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-12-11 14:18 UTC by Carl-Erik Kopseng
Modified:	2006-12-11 14:37 UTC

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

Description Carl-Erik Kopseng 2006-12-11 14:18:02 UTC

What were you doing when the application crashed?
I now know what crashed the program. It was plugging in my IPOD Nano. This happened several times in a row. Has not been a problem previously as far as I can tell. The Ipod has been updatet with Banshee if it makes any difference. When the Ipod is unplugged, everything is back to normal (perfect!).


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

Memory status: size: 108228608 vsize: 0 resident: 108228608 share: 0 rss: 39256064 rss_rlim: 0
CPU usage: start_time: 1165846466 rtime: 0 utime: 640 stime: 0 cutime:577 cstime: 0 timeout: 63 it_real_value: 0 frequency: 8

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 -1229085008 (LWP 9719)]
[New Thread -1286603872 (LWP 9735)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 93284

Thread 1 (Thread -1229085008 (LWP 9719))

#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_object_newv
from /usr/lib/libgobject-2.0.so.0
#6 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#7 g_object_new
from /usr/lib/libgobject-2.0.so.0
#8 rb_ipod_source_new
from /usr/lib/rhythmbox/plugins/ipod/libipod.so
#9 register_rb_plugin
from /usr/lib/rhythmbox/plugins/ipod/libipod.so
#10 rb_marshal_OBJECT__OBJECT
#11 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#15 rb_removable_media_manager_queue_transfer
#16 g_cclosure_marshal_VOID__OBJECT
from /usr/lib/libgobject-2.0.so.0
#17 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#21 gnome_vfs_volume_monitor_emit_pre_unmount
from /usr/lib/libgnomevfs-2.so.0
#22 gnome_vfs_volume_monitor_client_get_type
from /usr/lib/libgnomevfs-2.so.0
#23 dbus_connection_dispatch
from /usr/lib/libdbus-1.so.3
#24 dbus_server_setup_with_g_main
from /usr/lib/libdbus-glib-1.so.2
#25 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#26 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#27 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#28 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#29 main
#0 __kernel_vsyscall

Comment 1 Alex Lancaster 2006-12-11 14: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 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 ***