GNOME Bugzilla – Bug 558380
crash in Evolution Mail and Calendar: Opening evolution
Last modified: 2008-12-11 18:02:32 UTC
What were you doing when the application crashed? Opening evolution Distribution: Fedora release 9 (Sulphur) Gnome Release: 2.22.3 2008-07-01 (Red Hat, Inc) BugBuddy Version: 2.22.0 System: Linux 2.6.26.6-79.fc9.i686 #1 SMP Fri Oct 17 14:52:14 EDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10500000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora Memory status: size: 80822272 vsize: 80822272 resident: 20144128 share: 10330112 rss: 20144128 rss_rlim: 4294967295 CPU usage: start_time: 1225280071 rtime: 123 utime: 92 stime: 31 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/evolution-exchange-storage' [Thread debugging using libthread_db enabled] [New Thread 0xb802c760 (LWP 25567)] [New Thread 0xb66ffb90 (LWP 25892)] [New Thread 0xb7c45b90 (LWP 25568)] 0x00110416 in __kernel_vsyscall ()
+ Trace 208870
Thread 1 (Thread 0xb802c760 (LWP 25567))
----------- .xsession-errors --------------------- (evolution:25497): evolution-mail-WARNING **: Failed to refresh folders: No such folder Public Folders/Hidden (evolution:25497): camel-exchange-provider-CRITICAL **: camel-stub.c:472: Uncaught case (54) (evolution:25497): camel-exchange-provider-CRITICAL **: camel-stub.c:472: Uncaught case (1039882112) (evolution:25497): camel-exchange-provider-CRITICAL **: camel-stub.c:472: Uncaught case (54) (evolution:25497): camel-exchange-provider-CRITICAL **: camel-stub.c:472: Uncaught case (1039882112) (evolution:25497): camel-exchange-provider-CRITICAL **: camel-stub.c:472: Uncaught case (54) (evolution:25497): camel-exchange-provider-CRITICAL **: camel-stub.c:472: Uncaught case (1039882112) (evolution:25497): evolution-mail-WARNING **: Failed to refresh folders: Could not open folder --------------------------------------------------
*** Bug 559417 has been marked as a duplicate of this bug. ***
*** Bug 563148 has been marked as a duplicate of this bug. ***
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 506838 ***