Bug 539215 – crash in Rhythmbox Music Player: eu estava tentando impor...

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 539215 - crash in Rhythmbox Music Player: eu estava tentando impor...


Summary:	crash in Rhythmbox Music Player: eu estava tentando impor...


Status:	RESOLVED DUPLICATE of bug 524985

Product:	rhythmbox
Classification:	Other
Component:	general
Version:	0.11.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-06-20 02:05 UTC by pcmonteiro
Modified:	2008-06-22 13:05 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description pcmonteiro 2008-06-20 02:05:10 UTC

Version: 0.11.5

What were you doing when the application crashed?
eu estava tentando importar as musicas do meu ipod


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 602206208 vsize: 602206208 resident: 72687616 share: 24440832 rss: 72687616 rss_rlim: 18446744073709551615
CPU usage: start_time: 1213927185 rtime: 3656 utime: 3435 stime: 221 cutime:1 cstime: 13 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 0x2b4e2b85c2a0 (LWP 6428)]
[New Thread 0x41802950 (LWP 6456)]
(no debugging symbols found)
0x00002b4e1e1ebedf in waitpid () from /lib/libpthread.so.0

+ Trace 200894

Thread 1 (Thread 0x2b4e2b85c2a0 (LWP 6428))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 rb_ipod_db_set_ipod_name
from /usr/lib/rhythmbox/plugins/ipod/libipod.so
#6 ??
from /usr/lib/rhythmbox/plugins/ipod/libipod.so
#7 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#8 ??
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#11 ??
from /usr/lib/libgobject-2.0.so.0
#12 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#13 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#14 g_object_new
from /usr/lib/libgobject-2.0.so.0
#15 rb_ipod_source_new
from /usr/lib/rhythmbox/plugins/ipod/libipod.so
#16 ??
from /usr/lib/rhythmbox/plugins/ipod/libipod.so
#17 rb_marshal_OBJECT__OBJECT
from /usr/lib/librhythmbox-core.so.0
#18 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#19 ??
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#22 ??
#23 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#24 ??
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#27 ??
from /usr/lib/libgnomevfs-2.so.0
#28 dbus_connection_dispatch
from /usr/lib/libdbus-1.so.3
#29 ??
from /usr/lib/libdbus-glib-1.so.2
#30 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#31 ??
from /usr/lib/libglib-2.0.so.0
#32 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#33 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#34 main
#0 waitpid
from /lib/libpthread.so.0

Comment 1 Susana 2008-06-22 13:05:05 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 524985 ***