GNOME Bugzilla – Bug 490654
crash in Tasks:
Last modified: 2007-10-26 23:11:14 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: Clearlooks Icon Theme: Echo Memory status: size: 223465472 vsize: 223465472 resident: 76976128 share: 65179648 rss: 76976128 rss_rlim: 4294967295 CPU usage: start_time: 1193429448 rtime: 321 utime: 274 stime: 47 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 -1209219360 (LWP 17735)] [New Thread -1314923632 (LWP 19725)] [New Thread -1293943920 (LWP 17780)] [New Thread -1281156208 (LWP 17779)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 173127
Thread 1 (Thread -1209219360 (LWP 17735))
----------- .xsession-errors (3749 sec old) --------------------- 16:08:24 : Setup Yum : Base setup completed 16:08:24 : Building Package Lists 16:08:27 : Building Package Lists Completed 16:08:27 : Building Groups Lists 16:08:28 : Building Group Lists Completed 16:08:28 : Getting packages : installed 16:08:28 : Found 10 installed packages 16:08:28 : Getting packages : available 16:08:28 : Found 52 available packages 16:08:28 : Sorting packages 16:08:28 : Population view with packages 16:08:28 : Population Completed CalDAV Eplugin starting up ... ** (evolution:17735): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:17735): 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 ***