What were you doing when the application crashed?
i close the window and it crash


Distribution: Fedora release 6.92 (Rawhide)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-1.3024.fc7 #1 SMP Tue Mar 27 20:29:22 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10299902
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 131977216 vsize: 131977216 resident: 29900800 share: 19705856 rss: 29900800 rss_rlim: 4294967295
CPU usage: start_time: 1175163682 rtime: 951 utime: 415 stime: 536 cutime:55 cstime: 71 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 -1208252704 (LWP 2810)]
[New Thread -1284052080 (LWP 2880)]
(no debugging symbols found)
0x00913402 in __kernel_vsyscall ()

+ Trace 123179

----------- .xsession-errors (21 sec old) ---------------------
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x360005b (Untitled1 )
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
CalDAV Eplugin starting up ...
** (evolution:2810): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:2810): DEBUG: mailto URL program: evolution
(evolution:2810): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2810): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail'
(evolution:2810): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
(evolution:2810): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
process 2810: The last reference on a connection was dropped without closing the connection. This is a bug in an application. See dbus_connection_unref() documentation for details.
Most likely, the application was supposed to call dbus_connection_close(), since this is a private connection.
  D-Bus not built with -rdynamic so unable to print a backtrace
--------------------------------------------------