GNOME Bugzilla – Bug 508875
crash in Tasks:
Last modified: 2008-01-12 15:41:52 UTC
Version: 2.10 What were you doing when the application crashed? 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: Enforcing Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist Memory status: size: 252612608 vsize: 252612608 resident: 141307904 share: 48156672 rss: 141307904 rss_rlim: 4294967295 CPU usage: start_time: 1200028295 rtime: 15585 utime: 14495 stime: 1090 cutime:1649 cstime: 88 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 -1208359200 (LWP 3458)] [New Thread -1253516400 (LWP 3589)] [New Thread -1306358896 (LWP 3587)] [New Thread -1241937008 (LWP 3482)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 185007
Thread 1 (Thread -1208359200 (LWP 3458))
----------- .xsession-errors (178 sec old) --------------------- (evolution:3458): libebook-WARNING **: invalid escape, passing it through (evolution:3458): libebook-WARNING **: invalid escape, passing it through (evolution:3458): libebook-WARNING **: invalid escape, passing it through (evolution:3458): libebook-WARNING **: invalid escape, passing it through (evolution:3458): libebook-WARNING **: invalid escape, passing it through (evolution:3458): libebook-WARNING **: invalid escape, passing it through (evolution:3458): libebook-WARNING **: invalid escape, passing it through (evolution:3458): libebook-WARNING **: invalid escape, passing it through --------------------------------------------------
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 447591 ***