GNOME Bugzilla – Bug 539611
crash in Rhythmbox Music Player: Nothing at all. Just ope...
Last modified: 2008-06-23 20:13:34 UTC
Version: 0.11.5 What were you doing when the application crashed? Nothing at all. Just openned the app and crashed. Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (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: Overglossed Icon Theme: black-white_2-Gloss Memory status: size: 70459392 vsize: 70459392 resident: 27361280 share: 16633856 rss: 27361280 rss_rlim: 4294967295 CPU usage: start_time: 1214149998 rtime: 145 utime: 129 stime: 16 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 0xb65ef740 (LWP 21802)] [New Thread 0xb53cab90 (LWP 21810)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 201083
Thread 1 (Thread 0xb65ef740 (LWP 21802))
----------- .xsession-errors --------------------- (rhythmbox:21802): GLib-CRITICAL **: g_utf8_casefold: assertion `str != NULL' failed (rhythmbox:21802): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed (rhythmbox:21802): GLib-CRITICAL **: g_utf8_casefold: assertion `str != NULL' failed (rhythmbox:21802): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed (rhythmbox:21802): GLib-CRITICAL **: g_utf8_casefold: assertion `str != NULL' failed (rhythmbox:21802): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed (rhythmbox:21802): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion `instance != NULL && instance->g_class != NULL' failed (bug-buddy:21839): Gtk-WARNING **: Unable to locate theme engine in module_path: "ubuntulooks", --------------------------------------------------
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 ***