GNOME Bugzilla – Bug 449810
crash in Tasks: starting evolution
Last modified: 2007-06-21 16:34:09 UTC
Version: 2.10 What were you doing when the application crashed? starting evolution Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 172351488 vsize: 172351488 resident: 48361472 share: 40628224 rss: 48361472 rss_rlim: 4294967295 CPU usage: start_time: 1182440494 rtime: 113 utime: 96 stime: 17 cutime:2 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 -1208809760 (LWP 5209)] [New Thread -1252836464 (LWP 5295)] [New Thread -1284318320 (LWP 5294)] [New Thread -1210909808 (LWP 5246)] (no debugging symbols found) 0x00e28402 in __kernel_vsyscall ()
+ Trace 142692
Thread 1 (Thread -1208809760 (LWP 5209))
----------- .xsession-errors (167 sec old) --------------------- Lost connection to Evolution Exchange backend process (evolution:4860): evolution-mail-WARNING **: Error occurred while existing dialogue active: Lost connection to Evolution Exchange backend process (evolution:4860): evolution-mail-WARNING **: Error occurred while existing dialogue active: Lost connection to Evolution Exchange backend process (evolution:4860): evolution-mail-WARNING **: Error occurred while existing dialogue active: Lost connection to Evolution Exchange backend process (evolution:4860): evolution-mail-WARNING **: Error occurred while existing dialogue active: Lost connection to Evolution Exchange backend process ...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 the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 425093 ***