Bug 368940 – crash in Rhythmbox Music Player: Connecting an HFS+-forma...

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 368940 - crash in Rhythmbox Music Player: Connecting an HFS+-forma...


Summary:	crash in Rhythmbox Music Player: Connecting an HFS+-forma...


Status:	RESOLVED DUPLICATE of bug 352972

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-01 16:49 UTC by Michel Alexandre Salim
Modified:	2006-11-01 18:14 UTC

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

Description Michel Alexandre Salim 2006-11-01 16:49:26 UTC

What were you doing when the application crashed?
Connecting an HFS+-formatted iPod nano. This is on FC6 x86_64


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 422244352 vsize: 422244352 resident: 44273664 share: 18857984 rss: 44273664 rss_rlim: -1
CPU usage: start_time: 1162399028 rtime: 396 utime: 353 stime: 43 cutime:6 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912506537456 (LWP 27781)]
[New Thread 1115699520 (LWP 27789)]
(no debugging symbols found)
0x000000307900d96f in waitpid () from /lib64/libpthread.so.0

+ Trace 81498

Thread 1 (Thread 46912506537456 (LWP 27781))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 strlen
from /lib64/libc.so.6
#4 g_strdup
from /lib64/libglib-2.0.so.0
#5 itdb_device_list_devices
from /usr/lib64/libgpod.so.0
#6 g_object_newv
from /lib64/libgobject-2.0.so.0
#7 g_object_new_valist
from /lib64/libgobject-2.0.so.0
#8 g_object_new
from /lib64/libgobject-2.0.so.0
#9 itdb_device_new
from /usr/lib64/libgpod.so.0
#10 itdb_set_mountpoint
from /usr/lib64/libgpod.so.0
#11 itdb_parse
from /usr/lib64/libgpod.so.0
#12 rb_ipod_source_register_type
from /usr/lib64/rhythmbox/plugins/libipod.so
#13 g_object_newv
from /lib64/libgobject-2.0.so.0
#14 g_object_new_valist
from /lib64/libgobject-2.0.so.0
#15 g_object_new
from /lib64/libgobject-2.0.so.0
#16 rb_ipod_source_new
from /usr/lib64/rhythmbox/plugins/libipod.so
#17 register_rb_plugin
from /usr/lib64/rhythmbox/plugins/libipod.so
#18 rb_marshal_OBJECT__OBJECT
#19 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#20 g_signal_override_class_closure
from /lib64/libgobject-2.0.so.0
#21 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#22 g_signal_emit
from /lib64/libgobject-2.0.so.0
#23 rb_removable_media_manager_get_type
#24 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#25 g_signal_override_class_closure
from /lib64/libgobject-2.0.so.0
#26 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#27 g_signal_emit
from /lib64/libgobject-2.0.so.0
#28 gnome_vfs_volume_monitor_emit_pre_unmount
from /usr/lib64/libgnomevfs-2.so.0
#29 gnome_vfs_volume_monitor_client_shutdown_private
from /usr/lib64/libgnomevfs-2.so.0
#30 dbus_connection_dispatch
from /lib64/libdbus-1.so.3
#31 dbus_server_setup_with_g_main
from /usr/lib64/libdbus-glib-1.so.2
#32 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#33 g_main_context_check
from /lib64/libglib-2.0.so.0
#34 g_main_loop_run
from /lib64/libglib-2.0.so.0
#35 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#36 main
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Karsten Bräckelmann 2006-11-01 18:14:30 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 352972 ***