GNOME Bugzilla – Bug 472719
crash in Tasks: Launching after a packag...
Last modified: 2007-09-24 17:59:47 UTC
Version: 2.10 What were you doing when the application crashed? Launching after a package update - first time 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 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: 116248576 vsize: 116248576 resident: 36163584 share: 28819456 rss: 36163584 rss_rlim: 4294967295 CPU usage: start_time: 1188700205 rtime: 84 utime: 77 stime: 7 cutime:3 cstime: 6 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 -1208887584 (LWP 3097)] [New Thread -1242567792 (LWP 3133)] [New Thread -1219552368 (LWP 3130)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 159745
Thread 1 (Thread -1208887584 (LWP 3097))
----------- .xsession-errors --------------------- localuser:phil being added to access control list if: Improper then. SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2861 CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:2971): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2971): DEBUG: mailto URL program: evolution CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:3097): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3097): 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 ***