Bug 394293 – Crash in rhythmbox after connecting ipod

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 394293 - Crash in rhythmbox after connecting ipod


Summary:	Crash in rhythmbox after connecting ipod


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-01-08 17:04 UTC by Marco Lazzeri
Modified:	2007-01-08 22:18 UTC

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

Description Marco Lazzeri 2007-01-08 17:03:24 UTC

Distribution: Debian 4.0
Package: rhythmbox
Severity: Normal
Version: GNOME2.14.3 0.9.6
Gnome-Distributor: Debian
Synopsis: Crash in rhythmbox after connecting ipod
Bugzilla-Product: rhythmbox
Bugzilla-Component: general
Bugzilla-Version: 0.9.6
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
When connecting my ipod, gnome starts rhythmbox but the application
crashes. The operating system correctly mount a part of the ipod
filesystem under /media/ipodName

Steps to reproduce the crash:
1. Plug the ipod usb cables
2. Wait for gnome to start rhythmbox or start rhythmbox manually

Expected Results:


How often does this happen?
Always I connect the ipod

Additional Information:
Does not happen on i386 architecture but only on amd64. I have a
GNU/Linux debian testing on both i386 and amd64


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 47267470018176 (LWP 8753)]
[New Thread 1074006368 (LWP 8755)]
(no debugging symbols found)
0x00002afd4c0e700f in waitpid () from /lib/libpthread.so.0

+ Trace 100473

Thread 1 (Thread 47267470018176 (LWP 8753))

#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





------- Bug created by bug-buddy at 2007-01-08 17:05 -------

Comment 1 Jonathan Matthew 2007-01-08 22:18: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.

The crash is due to a bug in versions of libgpod before 0.4.0.

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