GNOME Bugzilla – Bug 480565
crash in Tasks: I just hit the send / re...
Last modified: 2007-09-26 17:59:22 UTC
Version: 2.10 What were you doing when the application crashed? I just hit the send / receive button. 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: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 106254336 vsize: 106254336 resident: 36282368 share: 29163520 rss: 36282368 rss_rlim: 4294967295 CPU usage: start_time: 1190807729 rtime: 94 utime: 84 stime: 10 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 -1208457504 (LWP 2748)] [New Thread -1252488304 (LWP 2801)] [New Thread -1219626096 (LWP 2770)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 165626
Thread 1 (Thread -1208457504 (LWP 2748))
----------- .xsession-errors (83 sec old) --------------------- localuser:eric being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2523 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:2748): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2748): 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 ***