GNOME Bugzilla – Bug 503142
crash in Evolution: forwarding an email
Last modified: 2007-12-12 02:44:35 UTC
What were you doing when the application crashed? forwarding an email Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.16-2-686 #1 Fri Aug 18 19:01:49 UTC 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 80568320 vsize: 80568320 resident: 21442560 share: 10342400 rss: 21442560 rss_rlim: 4294967295 CPU usage: start_time: 1197411670 rtime: 2083 utime: 1981 stime: 102 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/evolution-exchange-storage' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xa669c6b0 (LWP 29438)] [New Thread 0xa6599b90 (LWP 30280)] [New Thread 0xa65f6b90 (LWP 29439)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 181600
Thread 2 (Thread 0xa6599b90 (LWP 30280))
----------- .xsession-errors (721 sec old) --------------------- (evolution:13098): libecal-WARNING **: e-cal.c:318: Unexpected response (evolution:13098): libecal-WARNING **: e-cal.c:318: Unexpected response (evolution:13098): libecal-WARNING **: e-cal.c:318: Unexpected response (evolution:13098): libecal-WARNING **: e-cal.c:318: Unexpected response (evolution:13098): libecal-WARNING **: e-cal.c:318: Unexpected response Shutting down evolution (Evolution Shell) Shutting down evolution-exchange-storage (Evolution Calendar Exchange backend / Evolution Addressbook Exchange backend) Shutting down evolution-data-server-1.12 (Evolution Calendar file and webcal backend / Evolution Addressbook file backend) Shutting down evolution-alarm-notify (Evolution Calendar alarm notification service) evolution-shell-Message: Killing old version of evolution-data-server... --------------------------------------------------
same one as bug 501295 *** This bug has been marked as a duplicate of 501295 ***