Version: 2.10

What were you doing when the application crashed?
Quitting Evolution. As before, I had not been using Tasks. This time I think I had the debuginfo packages running.


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: Enforcing
Accessibility: Disabled
GTK+ Theme: Tangoish
Icon Theme: Tango

Memory status: size: 118419456 vsize: 118419456 resident: 47665152 share: 32043008 rss: 47665152 rss_rlim: 4294967295
CPU usage: start_time: 1183156808 rtime: 2548 utime: 2354 stime: 194 cutime:3 cstime: 13 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1209084192 (LWP 3521)]
[New Thread -1253049456 (LWP 9245)]
[New Thread -1229743216 (LWP 3610)]
[New Thread -1230435440 (LWP 3557)]
0x006ba402 in __kernel_vsyscall ()

+ Trace 144814

----------- .xsession-errors (14700 sec old) ---------------------
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1400003 (Top Panel)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(evolution:3521): camel-WARNING **: Search returned an invalid result type
(evolution:3521): camel-WARNING **: Search returned an invalid result type
(evolution:3521): camel-WARNING **: Search returned an invalid result type
(evolution:3521): camel-WARNING **: Search returned an invalid result type
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4c025df (Messages -)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: last_focus_time (2063979921) is greater than comparison timestamp (2063979919).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _N
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4c025df (Messages -)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------