Version: 2.10

What were you doing when the application crashed?



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.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist-4dIndigo
Icon Theme: Iris

Memory status: size: 109412352 vsize: 109412352 resident: 39755776 share: 32038912 rss: 39755776 rss_rlim: 4294967295
CPU usage: start_time: 1189428237 rtime: 222 utime: 203 stime: 19 cutime:2 cstime: 3 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 -1208637728 (LWP 30799)]
[New Thread -1240470640 (LWP 30862)]
[New Thread -1229980784 (LWP 30827)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 161784

----------- .xsession-errors (1293702 sec old) ---------------------
end from FAM server connection
(mail-notification:4313): mail-notification-WARNING **: cgordon@dul1wnexmb06.vcorp.ad.vrsn.com: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
end from FAM server connection
end from FAM server connection
end from FAM server connection
(mail-notification:4313): mail-notification-WARNING **: cgordon@dul1wnexmb06.vcorp.ad.vrsn.com: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
end from FAM server connection
end from FAM server connection
end from FAM server connection
(mail-notification:4313): mail-notification-WARNING **: cgordon@dul1wnexmb06.vcorp.ad.vrsn.com: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
...Too much output, ignoring rest...
--------------------------------------------------