GNOME Bugzilla – Bug 477630
crash in Tasks: starting up
Last modified: 2007-09-24 17:39:43 UTC
Version: 2.10 What were you doing when the application crashed? starting up 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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 114114560 vsize: 114114560 resident: 34930688 share: 28221440 rss: 34930688 rss_rlim: 4294967295 CPU usage: start_time: 1189994661 rtime: 54 utime: 48 stime: 6 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 -1208396064 (LWP 2817)] [New Thread -1241519216 (LWP 2869)] [New Thread -1231029360 (LWP 2840)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 163438
Thread 1 (Thread -1208396064 (LWP 2817))
----------- .xsession-errors --------------------- localuser:charlie being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2617 Unable to open desktop file /usr/share/applications/openoffice.org-1.9-writer.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/openoffice.org-1.9-impress.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/openoffice.org-1.9-calc.desktop for panel launcher: No such file or directory CalDAV Eplugin starting up ... ** (evolution:2817): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2817): 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 ***