GNOME Bugzilla – Bug 563148
crash in Evolution Mail and Calendar: Starting evolution
Last modified: 2008-12-03 18:49:21 UTC
What were you doing when the application crashed? Starting 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.27.5-41.fc9.i686 #1 SMP Thu Nov 13 20:52:14 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10502000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora Memory status: size: 96444416 vsize: 96444416 resident: 24932352 share: 10338304 rss: 24932352 rss_rlim: 4294967295 CPU usage: start_time: 1228328620 rtime: 91 utime: 67 stime: 24 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 0xb7fcb760 (LWP 4754)] [New Thread 0xb79ffb90 (LWP 4924)] [New Thread 0xb7be4b90 (LWP 4755)] 0x00110416 in __kernel_vsyscall ()
+ Trace 210452
Thread 1 (Thread 0xb7fcb760 (LWP 4754))
----------- .xsession-errors (6 sec old) --------------------- CalDAV Eplugin starting up ... ** (evolution:4739): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:4739): DEBUG: mailto URL program: evolution (evolution:4739): evolution-mail-WARNING **: Failed to refresh folders: No such folder Public Folders/Hidden (evolution:4739): evolution-mail-WARNING **: Failed to refresh folders: Could not open folder (evolution:4739): evolution-mail-WARNING **: Failed to refresh folders: Error communicating with Evolution Exchange backend process: No such file or directory (evolution:4739): camel-exchange-provider-CRITICAL **: camel-stub.c:472: Uncaught case (54) (evolution:4739): camel-exchange-provider-CRITICAL **: camel-stub.c:472: Uncaught case (1039882112) (evolution:4739): evolution-mail-WARNING **: Failed to refresh folders: Could not open folder --------------------------------------------------
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 558380 ***