What were you doing when the application crashed?
Exit evolution by close the window.


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: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 148762624 vsize: 148762624 resident: 47927296 share: 22736896 rss: 47927296 rss_rlim: 4294967295
CPU usage: start_time: 1194926261 rtime: 3288 utime: 2955 stime: 333 cutime:129 cstime: 188 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 -1208551712 (LWP 3892)]
[New Thread -1271932016 (LWP 5422)]
[New Thread -1227846768 (LWP 4030)]
[New Thread -1326158960 (LWP 3960)]
(no debugging symbols found)
0x00b33402 in __kernel_vsyscall ()

+ Trace 177339

----------- .xsession-errors (91 sec old) ---------------------
closing
closing
(evolution:3892): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
closing
end from FAM server connection
end from FAM server connection
end from FAM server connection
(evolution:3892): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3892): camel-WARNING **: Could not find key entry for word '0x00000000': Success
(evolution:3892): camel-WARNING **: Could not find key entry for word '0x00000000': Success
(evolution:3892): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
--------------------------------------------------