GNOME Bugzilla – Bug 481061
crash in Tasks:
Last modified: 2007-09-29 00:01:24 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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: gnome Memory status: size: 132284416 vsize: 132284416 resident: 39194624 share: 32591872 rss: 39194624 rss_rlim: 4294967295 CPU usage: start_time: 1190919681 rtime: 134 utime: 115 stime: 19 cutime:0 cstime: 1 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 -1208351008 (LWP 16110)] [New Thread -1281766512 (LWP 16211)] [New Thread -1260786800 (LWP 16150)] [New Thread -1210451056 (LWP 16147)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 166003
Thread 1 (Thread -1208351008 (LWP 16110))
----------- .xsession-errors (31 sec old) --------------------- CLIENT: Task: Task::done() CLIENT: Task: emitting finished CLIENT: Task: Task::done() CLIENT: Task: emitting finished _IceTransSocketUNIXConnect: Cannot connect to non-local host wrh-sf-xw034.corp.wrhambrecht.com (evolution:16110): GnomeUI-WARNING **: While connecting to session manager: Could not open network socket. CalDAV Eplugin starting up ... CLIENT: Task: Task::done() CLIENT: Task: emitting finished ** (evolution:16110): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:16110): DEBUG: mailto URL program: evolution error : unterminated entity reference Hardware error : unterminated entity reference T --------------------------------------------------
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 431459 ***