GNOME Bugzilla – Bug 472800
crash in Tasks: Switched to Inbox
Last modified: 2007-09-03 13:08:50 UTC
Version: 2.10 What were you doing when the application crashed? Switched to Inbox 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: 126980096 vsize: 126980096 resident: 39526400 share: 32710656 rss: 39526400 rss_rlim: 4294967295 CPU usage: start_time: 1188735593 rtime: 118 utime: 107 stime: 11 cutime:2 cstime: 9 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 -1208543520 (LWP 2893)] [New Thread -1294410864 (LWP 2952)] [New Thread -1230169200 (LWP 2927)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 159807
Thread 1 (Thread -1208543520 (LWP 2893))
----------- .xsession-errors (7 sec old) --------------------- localuser:rheldmann being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2411 Unable to open desktop file /usr/share/applications/openoffice.org-1.9-impress.desktop for panel launcher: No such file or directory CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:2893): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2893): 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 ***