Bug 435983 – Bug: Rhythmbox crashes if mac-formatted iPod is connected

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 435983 - Bug: Rhythmbox crashes if mac-formatted iPod is connected


Summary:	Bug: Rhythmbox crashes if mac-formatted iPod is connected


Status:	RESOLVED DUPLICATE of bug 352972

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-05-04 22:47 UTC by hannes.scharmann
Modified:	2007-06-03 10:19 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description hannes.scharmann 2007-05-04 22:47:40 UTC

From:  <>
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.14.0
Subject: Rhythmbox crashes if mac-formatted iPod is connected

Distribution: Debian lenny/sid
Package: rhythmbox
Severity: Normal
Version: GNOME2.14.3 0.9.6
Gnome-Distributor: Debian
Synopsis: Rhythmbox crashes if mac-formatted iPod is connected
Bugzilla-Product: rhythmbox
Bugzilla-Component: general
Bugzilla-Version: 0.9.6
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
Rhythmbox crashes if Mac-formatted iPod is connected

Steps to reproduce the crash:
1. Connect a mac-formatted iPod
2. Start the rhythmbox

Expected Results:
Rhythmbox crashes

How often does this happen?

Additional Information:

Debugging Information:

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 47652207122000 (LWP 23960)]
[New Thread 1074006368 (LWP 23962)]
(no debugging symbols found)
0x00002b56e02bd00f in waitpid () from /lib/libpthread.so.0

+ Trace 132452

Thread 1 (Thread 47652207122000 (LWP 23960))

#0 waitpid
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 strlen
from /lib/libc.so.6
#4 g_strdup
from /usr/lib/libglib-2.0.so.0
#5 itdb_device_list_devices
from /usr/lib/libgpod.so.0
#6 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#7 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#8 g_object_new
from /usr/lib/libgobject-2.0.so.0
#9 itdb_device_new
from /usr/lib/libgpod.so.0
#10 itdb_set_mountpoint
from /usr/lib/libgpod.so.0
#11 itdb_parse
from /usr/lib/libgpod.so.0
#12 rb_ipod_source_register_type
from /usr/lib/rhythmbox/plugins/ipod/libipod.so
#13 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#14 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#15 g_object_new
from /usr/lib/libgobject-2.0.so.0
#16 rb_ipod_source_new
from /usr/lib/rhythmbox/plugins/ipod/libipod.so
#17 register_rb_plugin
from /usr/lib/rhythmbox/plugins/ipod/libipod.so
#18 rb_marshal_OBJECT__OBJECT
#19 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#23 rb_removable_media_manager_queue_transfer
#24 rb_removable_media_manager_scan
#25 rb_shell_new
#26 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#27 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#28 g_object_new
from /usr/lib/libgobject-2.0.so.0
#29 rb_shell_new
#30 main
#0 waitpid
from /lib/libpthread.so.0




-- 
pub 0x13C446E1 2005-10-23 Hannes Scharmann <hannes.scharmann@wattweb.de>
Key fingerprint = F5B6 9965 D9A8 61BF C8CD 844B 9C9C 3730 13C4 46E1




------- Bug created by bug-buddy at 2007-05-04 22:47 -------

Comment 1 Philip Withnall 2007-06-03 10:19:37 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 ***