GNOME Bugzilla – Bug 488917
crash in Tasks: starting evolution
Last modified: 2007-10-22 21:58:29 UTC
Version: 2.10 What were you doing when the application crashed? starting evolution 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: MurrinaCappuccino Icon Theme: Neu Memory status: size: 117739520 vsize: 117739520 resident: 38367232 share: 30175232 rss: 38367232 rss_rlim: 4294967295 CPU usage: start_time: 1193042293 rtime: 114 utime: 102 stime: 12 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208711456 (LWP 3812)] [New Thread -1293743216 (LWP 3881)] [New Thread -1272763504 (LWP 3838)] [New Thread -1251783792 (LWP 3836)] 0x00110402 in __kernel_vsyscall ()
+ Trace 171877
Thread 1 (Thread -1208711456 (LWP 3812))
----------- .xsession-errors (15 sec old) --------------------- Tracker version 0.6.3 Copyright (c) 2005-2007 by Jamie McCracken (jamiemcc@gnome.org) This program is free software and comes without any warranty. It is licensed under version 2 or later of the General Public License which can be viewed at http://www.gnu.org/licenses/gpl.txt Initialising tracker... Could not set idle IO priority...attempting best effort 7 priority Throttle level is 0 ** Message: <info> You are now connected to the wireless network 'jiffernox'. CalDAV Eplugin starting up ... ** (evolution:3812): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3812): 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 ***