GNOME Bugzilla – Bug 482197
crash in Tasks: Trying to open Evolution...
Last modified: 2007-11-22 07:43:39 UTC
Version: 2.10 What were you doing when the application crashed? Trying to open Evolution. 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.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: Crux Icon Theme: Crux Memory status: size: 2086047744 vsize: 2086047744 resident: 1942999040 share: 6819840 rss: 1942999040 rss_rlim: 4294967295 CPU usage: start_time: 1191248880 rtime: 15440 utime: 14553 stime: 887 cutime:1 cstime: 1 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 -1208949024 (LWP 3813)] [New Thread -1254605936 (LWP 3841)] [New Thread -1243722864 (LWP 3838)] (no debugging symbols found) 0x00308402 in __kernel_vsyscall ()
+ Trace 166861
Thread 1 (Thread -1208949024 (LWP 3813))
----------- .xsession-errors (1957 sec old) --------------------- Lost connection to Evolution Exchange backend process (evolution:3262): evolution-mail-WARNING **: Error occurred while existing dialogue active: Lost connection to Evolution Exchange backend process (evolution:3262): evolution-mail-WARNING **: Error occurred while existing dialogue active: Lost connection to Evolution Exchange backend process (evolution:3262): evolution-mail-WARNING **: Error occurred while existing dialogue active: Lost connection to Evolution Exchange backend process (evolution:3262): evolution-mail-WARNING **: Error occurred while existing dialogue active: Lost connection to Evolution Exchange backend process ...Too much output, ignoring rest... --------------------------------------------------
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 349913 ***