GNOME Bugzilla – Bug 479058
crash in Tasks:
Last modified: 2007-09-24 17:35:31 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 125706240 vsize: 125706240 resident: 38309888 share: 31621120 rss: 38309888 rss_rlim: 4294967295 CPU usage: start_time: 1190399870 rtime: 40 utime: 36 stime: 4 cutime:1 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (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 -1208424736 (LWP 4213)] [New Thread -1246762096 (LWP 4236)] [New Thread -1224684656 (LWP 4233)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 164486
Thread 1 (Thread -1208424736 (LWP 4213))
----------- .xsession-errors (2120 sec old) --------------------- (nero:3982): GLib-CRITICAL **: g_markup_parse_context_parse: assertion `context->state != STATE_ERROR' failed (nero:3982): GLib-CRITICAL **: g_markup_parse_context_parse: assertion `context->state != STATE_ERROR' failed (nero:3982): GLib-CRITICAL **: g_markup_parse_context_parse: assertion `context->state != STATE_ERROR' failed (nero:3982): GLib-CRITICAL **: g_markup_parse_context_parse: assertion `context->state != STATE_ERROR' failed (nero:3982): GLib-CRITICAL **: g_markup_parse_context_parse: assertion `context->state != STATE_ERROR' failed (nero:3982): GLib-CRITICAL **: g_markup_parse_context_parse: assertion `context->state != STATE_ERROR' failed (nero:3982): GLib-CRITICAL **: g_markup_parse_context_parse: assertion `context->state != STATE_ERROR' failed ...Too much output, ignoring rest... --------------------------------------------------
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 364700 ***