GNOME Bugzilla – Bug 483067
crash in Tasks: Send/Recieve
Last modified: 2007-10-05 10:06:01 UTC
Version: 2.10 What were you doing when the application crashed? Send/Recieve 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 106639360 vsize: 106639360 resident: 38395904 share: 27697152 rss: 38395904 rss_rlim: 4294967295 CPU usage: start_time: 1191439720 rtime: 80 utime: 71 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 -1208940832 (LWP 3630)] [New Thread -1292035184 (LWP 3682)] [New Thread -1242567792 (LWP 3654)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 167493
Thread 1 (Thread -1208940832 (LWP 3630))
----------- .xsession-errors (8 sec old) --------------------- localuser:skunk being added to access control list SESSION_MANAGER=local/Mars:/tmp/.ICE-unix/2459 Kan ikke åbne skrivebordsfilen /usr/share/applications/openoffice.org-1.9-writer.desktop til panelgenveje: Ingen sådan fil eller filkatalog Kan ikke åbne skrivebordsfilen /usr/share/applications/openoffice.org-1.9-impress.desktop til panelgenveje: Ingen sådan fil eller filkatalog Kan ikke åbne skrivebordsfilen /usr/share/applications/openoffice.org-1.9-calc.desktop til panelgenveje: Ingen sådan fil eller filkatalog CalDAV Eplugin starting up ... ** (evolution:3630): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3630): 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 ***