GNOME Bugzilla – Bug 508880
crash in Tasks: reading mail
Last modified: 2008-01-12 15:41:28 UTC
Version: 2.10 What were you doing when the application crashed? reading 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: Clearlooks Memory status: size: 258236416 vsize: 258236416 resident: 122359808 share: 61423616 rss: 122359808 rss_rlim: 4294967295 CPU usage: start_time: 1200061422 rtime: 4610 utime: 4243 stime: 367 cutime:164 cstime: 18 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 -1208187168 (LWP 18436)] [New Thread -1377203312 (LWP 19558)] [New Thread -1366713456 (LWP 18524)] [New Thread -1283179632 (LWP 18517)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 185011
Thread 2 (Thread -1377203312 (LWP 19558))
----------- .xsession-errors (533 sec old) --------------------- (evolution:18436): libebook-WARNING **: invalid escape, passing it through (evolution:18436): libebook-WARNING **: invalid escape, passing it through (evolution:18436): libebook-WARNING **: invalid escape, passing it through (evolution:18436): libebook-WARNING **: invalid escape, passing it through (evolution:18436): libebook-WARNING **: invalid escape, passing it through (evolution:18436): libebook-WARNING **: invalid escape, passing it through (evolution:18436): libebook-WARNING **: invalid escape, passing it through [NoScript] [NoScript] browserDOMWindow wrapped for external load interception RMD :: mismatch remembered --------------------------------------------------
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 445309 ***