GNOME Bugzilla – Bug 498993
crash in Email: Inviando email
Last modified: 2007-11-22 20:02:10 UTC
Version: 2.10 What were you doing when the application crashed? Inviando email Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: RPanther2 Icon Theme: OSX Memory status: size: 171151360 vsize: 171151360 resident: 82059264 share: 43261952 rss: 82059264 rss_rlim: 4294967295 CPU usage: start_time: 1195716237 rtime: 8873 utime: 8347 stime: 526 cutime:21 cstime: 11 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 -1208621344 (LWP 19800)] [New Thread -1288139888 (LWP 22291)] [New Thread -1223545968 (LWP 20034)] [New Thread -1310413936 (LWP 19820)] [New Thread -1245713520 (LWP 19810)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 179258
Thread 2 (Thread -1288139888 (LWP 22291))
----------- .xsession-errors (6 sec old) --------------------- restoring draft flag 'text/plain' in emp_apps_open_in Increasing itip formatter search count to 1 Increasing itip formatter search count to 2 Decreasing itip formatter search count to 1 Decreasing itip formatter search count to 0 in emp_apps_open_in in emp_apps_open_in calendar selection changed in emp_apps_open_in Increasing itip formatter search count to 1 Increasing itip formatter search count to 2 Decreasing itip formatter search count to 1 Decreasing itip formatter search count to 0 Xlib: unexpected async reply (sequence 0x19b875)! --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 339602 ***