GNOME Bugzilla – Bug 482778
crash in Tasks:
Last modified: 2008-03-20 13:36:25 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 252604416 vsize: 252604416 resident: 84226048 share: 45408256 rss: 84226048 rss_rlim: 4294967295 CPU usage: start_time: 1191365201 rtime: 3376 utime: 3082 stime: 294 cutime:322 cstime: 33 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 -1208404256 (LWP 3360)] [New Thread -1310696560 (LWP 3377)] [New Thread -1342575728 (LWP 3373)] [New Thread -1248781424 (LWP 3364)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 167270
Thread 1 (Thread -1208404256 (LWP 3360))
----------- .xsession-errors (100 sec old) --------------------- (evolution:3360): libebook-WARNING **: invalid escape, passing it through (evolution:3360): libebook-WARNING **: invalid escape, passing it through (evolution:3360): libebook-WARNING **: invalid escape, passing it through (evolution:3360): libebook-WARNING **: invalid escape, passing it through (evolution:3360): libebook-WARNING **: invalid escape, passing it through (evolution:3360): libebook-WARNING **: invalid escape, passing it through JACK tmpdir identified as [/dev/shm] (evolution:3360): 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 426807 ***