GNOME Bugzilla – Bug 512646
crash in Tasks: Forwarding an e-mail
Last modified: 2008-01-29 18:20:20 UTC
Version: 2.10 What were you doing when the application crashed? Forwarding an e-mail 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.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 514887680 vsize: 514887680 resident: 421412864 share: 45887488 rss: 421412864 rss_rlim: 4294967295 CPU usage: start_time: 1201010806 rtime: 73485 utime: 69197 stime: 4288 cutime:60 cstime: 150 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 -1208822048 (LWP 4220)] [New Thread -1326449776 (LWP 16674)] [New Thread -1255548016 (LWP 4258)] [New Thread -1245058160 (LWP 4256)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 187105
Thread 1 (Thread -1208822048 (LWP 4220))
----------- .xsession-errors (10 sec old) --------------------- Increasing itip formatter search count to 2 Decreasing itip formatter search count to 1 Decreasing itip formatter search count to 0 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 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 Increasing itip formatter search count to 1 Increasing itip formatter search count to 2 Decreasing itip format (evolution:4220): gtkhtml-WARNING **: No such file or directory --------------------------------------------------
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 501900 ***