GNOME Bugzilla – Bug 482549
crash in Tasks: I just opened this e-mai...
Last modified: 2007-10-05 09:45:20 UTC
Version: 2.10 What were you doing when the application crashed? I just opened this e-mail program. The crash was immediate. 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: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 122101760 vsize: 122101760 resident: 38506496 share: 28610560 rss: 38506496 rss_rlim: 4294967295 CPU usage: start_time: 1191327132 rtime: 78 utime: 69 stime: 9 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 -1208346912 (LWP 2746)] [New Thread -1230414960 (LWP 2791)] [New Thread -1219515504 (LWP 2768)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 167100
Thread 1 (Thread -1208346912 (LWP 2746))
----------- .xsession-errors --------------------- localuser:eric being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2527 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:2746): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2746): 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 ***