GNOME Bugzilla – Bug 514829
crash in Tasks: Um, just typing in the f...
Last modified: 2008-02-08 04:42:07 UTC
Version: 2.10 What were you doing when the application crashed? Um, just typing in the freakin to field 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.14-60.fc7 #1 SMP Mon Jan 14 22:14:17 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 233947136 vsize: 233947136 resident: 122675200 share: 37806080 rss: 122675200 rss_rlim: 4294967295 CPU usage: start_time: 1202246349 rtime: 3390 utime: 2719 stime: 671 cutime:0 cstime: 2 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 -1208445216 (LWP 9815)] [New Thread -1333793904 (LWP 19035)] [New Thread -1231733872 (LWP 9858)] [New Thread -1242215536 (LWP 9841)] [New Thread -1221035120 (LWP 9840)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 188325
Thread 1 (Thread -1208445216 (LWP 9815))
----------- .xsession-errors --------------------- (evolution:9815): libebook-WARNING **: invalid escape, passing it through (evolution:9815): libebook-WARNING **: invalid escape, passing it through (evolution:9815): libebook-WARNING **: invalid escape, passing it through (evolution:9815): libebook-WARNING **: invalid escape, passing it through (evolution:9815): libebook-WARNING **: invalid escape, passing it through (evolution:9815): libebook-WARNING **: invalid escape, passing it through (evolution:9815): libebook-WARNING **: invalid escape, passing it through (evolution:9815): 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 the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 458670 ***