GNOME Bugzilla – Bug 504032
crash in Tasks: send/recieve
Last modified: 2007-12-17 16:54:26 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-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.1-33.fc7 #1 SMP Mon Jul 23 17:33:07 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: 110694400 vsize: 110694400 resident: 37781504 share: 30101504 rss: 37781504 rss_rlim: 4294967295 CPU usage: start_time: 1197893417 rtime: 86 utime: 77 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 -1208854816 (LWP 2888)] [New Thread -1266938992 (LWP 2913)] [New Thread -1221887088 (LWP 2906)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 182111
Thread 1 (Thread -1208854816 (LWP 2888))
----------- .xsession-errors (11 sec old) --------------------- localuser:tedwelter being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2422 ** (gnome-session:2422): WARNING **: Host name lookup failure on localhost. Initializing nautilus-open-terminal extension Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. ** Message: <info> You are now connected to the wireless network 'teddles'. CalDAV Eplugin starting up ... ** (evolution:2826): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2826): DEBUG: mailto URL program: evolution CalDAV Eplugin starting up ... ** (evolution:2888): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2888): 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 ***