GNOME Bugzilla – Bug 543050
crash in Rhythmbox Music Player: I have just logged on an...
Last modified: 2008-07-21 06:24:32 UTC
Version: 0.11.5 What were you doing when the application crashed? I have just logged on and have done nothing... Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24.4 #2 SMP PREEMPT Mon Apr 7 16:41:34 CEST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Industrial Icon Theme: gnome Memory status: size: 71942144 vsize: 71942144 resident: 35147776 share: 16920576 rss: 35147776 rss_rlim: 4294967295 CPU usage: start_time: 1216108143 rtime: 86 utime: 69 stime: 17 cutime:0 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 "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb65f2a80 (LWP 4201)] (no debugging symbols found) 0xb7f1a410 in __kernel_vsyscall ()
+ Trace 202862
Thread 1 (Thread 0xb65f2a80 (LWP 4201))
----------- .xsession-errors --------------------- (rhythmbox:4201): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed (rhythmbox:4201): GLib-CRITICAL **: g_utf8_casefold: assertion `str != NULL' failed (rhythmbox:4201): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed (rhythmbox:4201): GLib-CRITICAL **: g_utf8_casefold: assertion `str != NULL' failed (rhythmbox:4201): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed (rhythmbox:4201): GLib-CRITICAL **: g_utf8_casefold: assertion `str != NULL' failed (rhythmbox:4201): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed (rhythmbox:4201): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion `instance != NULL && instance->g_class != NULL' failed --------------------------------------------------
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 ***