GNOME Bugzilla – Bug 484743
crash in Tasks:
Last modified: 2007-10-08 20:46:11 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: No Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: gnome Memory status: size: 134389760 vsize: 134389760 resident: 41365504 share: 33697792 rss: 41365504 rss_rlim: 4294967295 CPU usage: start_time: 1191853462 rtime: 159 utime: 141 stime: 18 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 -1208428832 (LWP 3145)] [New Thread -1292735600 (LWP 3221)] [New Thread -1261266032 (LWP 3176)] [New Thread -1250382960 (LWP 3175)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 168787
Thread 1 (Thread -1208428832 (LWP 3145))
----------- .xsession-errors (41 sec old) --------------------- Transfer ACCEPTED by: LoginTask Transfer ACCEPTED by: LoginTask Transfer ACCEPTED by: ListTask Transfer ACCEPTED by: StatusNotifierTask Transfer ACCEPTED by: MailNotifierTask Transfer ACCEPTED by: StatusNotifierTask QGArray::find: Index 0 out of range Launched ok, pid = 3133 CalDAV Eplugin starting up ... CLIENT: Task: Task::done() CLIENT: Task: emitting finished error : unterminated entity reference Hardware error : unterminated entity reference T ** (evolution:3145): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3145): DEBUG: mailto URL program: evolution --------------------------------------------------
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 ***