GNOME Bugzilla – Bug 535316
crash in Rhythmbox Music Player:
Last modified: 2008-05-28 23:09:33 UTC
Version: 0.11.5 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Amaranth Memory status: size: 65949696 vsize: 65949696 resident: 29433856 share: 17313792 rss: 29433856 rss_rlim: 4294967295 CPU usage: start_time: 1211985172 rtime: 83 utime: 70 stime: 13 cutime:0 cstime: 2 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 0xb66c0740 (LWP 8773)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 198883
Thread 1 (Thread 0xb66c0740 (LWP 8773))
----------- .xsession-errors --------------------- (rhythmbox:8773): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed (rhythmbox:8773): GLib-CRITICAL **: g_utf8_casefold: assertion `str != NULL' failed (rhythmbox:8773): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed (rhythmbox:8773): GLib-CRITICAL **: g_utf8_casefold: assertion `str != NULL' failed (rhythmbox:8773): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed (rhythmbox:8773): GLib-CRITICAL **: g_utf8_casefold: assertion `str != NULL' failed (rhythmbox:8773): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed (rhythmbox:8773): 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 ***