GNOME Bugzilla – Bug 486198
crash in Tasks:
Last modified: 2007-10-14 13:13:58 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: 115953664 vsize: 115953664 resident: 36782080 share: 29081600 rss: 36782080 rss_rlim: 4294967295 CPU usage: start_time: 1192235289 rtime: 150 utime: 135 stime: 15 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 -1208523040 (LWP 3519)] [New Thread -1263105136 (LWP 3580)] [New Thread -1219634288 (LWP 3543)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 169863
Thread 1 (Thread -1208523040 (LWP 3519))
----------- .xsession-errors (50 sec old) --------------------- Tracker version 0.6.0 Copyright (c) 2005-2006 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... winscard_clnt.c:3349:SCardCheckDaemonAvailability() PCSC Not Running seahorse nautilus module initialized throttle level is 0 Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4d specified for 0xc001f2 (). CalDAV Eplugin starting up ... ** (evolution:3519): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3519): 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 364700 ***