Bug 542732 – crash in Rhythmbox Music Player: scanning my iPod error ...

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 542732 - crash in Rhythmbox Music Player: scanning my iPod error ...


Summary:	crash in Rhythmbox Music Player: scanning my iPod error ...


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-07-13 02:30 UTC by kenny.ide
Modified:	2008-07-13 10:12 UTC

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

Description kenny.ide 2008-07-13 02:30:47 UTC

Version: 0.11.5

What were you doing when the application crashed?
scanning my iPod

error said;
(rhythmbox:3480): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion `instance != NULL && instance->g_class != NULL' failed

(bug-buddy:3484): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion `g_utf8_validate (text, len, NULL)' failed

I guess iPod uses FAT that conflicts utf8.


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (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: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 452284416 vsize: 452284416 resident: 44597248 share: 21712896 rss: 44597248 rss_rlim: 18446744073709551615
CPU usage: start_time: 1215916139 rtime: 76 utime: 70 stime: 6 cutime:0 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 0x2b989e3fbda0 (LWP 3480)]
[New Thread 0x40800950 (LWP 3482)]
(no debugging symbols found)
0x00002b98902ebedf in waitpid () from /lib/libpthread.so.0

+ Trace 202672

Thread 1 (Thread 0x2b989e3fbda0 (LWP 3480))

#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 rb_removable_media_manager_scan
#24 ??
#25 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#26 ??
from /usr/lib/libglib-2.0.so.0
#27 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#28 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#29 main
#0 waitpid
from /lib/libpthread.so.0

Comment 1 Christophe Fergeau 2008-07-13 10:12:34 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 ***