GNOME Bugzilla – Bug 535317
crash in Rhythmbox Music Player: just opening it !
Last modified: 2008-05-28 23:09:33 UTC
Version: 0.11.5 What were you doing when the application crashed? just opening it ! 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: 65990656 vsize: 65990656 resident: 29421568 share: 17313792 rss: 29421568 rss_rlim: 4294967295 CPU usage: start_time: 1211985199 rtime: 83 utime: 69 stime: 14 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 0xb664f740 (LWP 8793)] [New Thread 0xb6242b90 (LWP 8797)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 198884
Thread 1 (Thread 0xb664f740 (LWP 8793))
----------- .xsession-errors --------------------- (rhythmbox:8793): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed (rhythmbox:8793): GLib-CRITICAL **: g_utf8_casefold: assertion `str != NULL' failed (rhythmbox:8793): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed (rhythmbox:8793): GLib-CRITICAL **: g_utf8_casefold: assertion `str != NULL' failed (rhythmbox:8793): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed (rhythmbox:8793): GLib-CRITICAL **: g_utf8_casefold: assertion `str != NULL' failed (rhythmbox:8793): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed (rhythmbox:8793): 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 ***