Bug 363915 – crash in Rhythmbox Music Player: Just finished booting up...

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 363915 - crash in Rhythmbox Music Player: Just finished booting up...


Summary:	crash in Rhythmbox Music Player: Just finished booting up...


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-10-21 13:10 UTC by taricorp
Modified:	2006-10-21 13:44 UTC

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

Description taricorp 2006-10-21 13:10:31 UTC

What were you doing when the application crashed?
Just finished booting up, plugged in a 1 GB iPod shuffle. (Rythmbox loaded itself because of saved sessions)


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

Memory status: size: 174870528 vsize: 174870528 resident: 21512192 share: 13099008 rss: 21512192 rss_rlim: -1
CPU usage: start_time: 1161436079 rtime: 108 utime: 97 stime: 11 cutime:7 cstime: 0 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 47493090423776 (LWP 4695)]
[New Thread 1090525520 (LWP 4781)]
(no debugging symbols found)
0x00002b31d3ebaeef in waitpid () from /lib/libpthread.so.0

+ Trace 77483

Thread 1 (Thread 47493090423776 (LWP 4695))

#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 Christian Kirbach 2006-10-21 13:44:36 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 ***