GNOME Bugzilla – Bug 509288
crash in Tasks:
Last modified: 2008-01-14 23:16:59 UTC
What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 134164480 vsize: 134164480 resident: 25030656 share: 16932864 rss: 25030656 rss_rlim: 4294967295 CPU usage: start_time: 1200291740 rtime: 137 utime: 119 stime: 18 cutime:1 cstime: 4 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 -1208953120 (LWP 2928)] [New Thread -1239368816 (LWP 2994)] [New Thread -1249858672 (LWP 2951)] [New Thread -1228862576 (LWP 2949)] (no debugging symbols found) 0x004d1402 in __kernel_vsyscall ()
+ Trace 185239
Thread 1 (Thread -1208953120 (LWP 2928))
----------- .xsession-errors (26 sec old) --------------------- (evolution:2928): evolution-mail-WARNING **: Failed to refresh folders: No such folder (evolution:2928): evolution-mail-WARNING **: Failed to refresh folders: Could not open folder (evolution:2928): evolution-mail-WARNING **: Failed to refresh folders: Could not open folder (evolution:2928): evolution-mail-WARNING **: Failed to refresh folders: Could not open folder (evolution:2928): evolution-mail-WARNING **: Failed to refresh folders: No such folder (evolution:2928): evolution-mail-WARNING **: Failed to refresh folders: Could not open folder (evolution:2928): evolution-mail-WARNING **: Failed to refresh folders: Could not open folder (evolution:2928): evolution-mail-WARNING **: Failed to refresh folders: Could not open folder --------------------------------------------------
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 431459 ***