GNOME Bugzilla – Bug 503548
crash in Tasks: hit the Send/Receive but...
Last modified: 2007-12-14 08:54:45 UTC
Version: 2.10 What were you doing when the application crashed? hit the Send/Receive button 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.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 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: 108490752 vsize: 108490752 resident: 36753408 share: 29634560 rss: 36753408 rss_rlim: 4294967295 CPU usage: start_time: 1197611623 rtime: 99 utime: 87 stime: 12 cutime:0 cstime: 0 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 -1208445216 (LWP 3093)] [New Thread -1255146608 (LWP 3127)] [New Thread -1220850800 (LWP 3101)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 181840
Thread 1 (Thread -1208445216 (LWP 3093))
----------- .xsession-errors (8 sec old) --------------------- localuser:terry being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2891 ** (gnome-session:2891): WARNING **: Host name lookup failure on localhost. error getting update info: No id element found CalDAV Eplugin starting up ... ** (evolution:3093): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3093): DEBUG: mailto URL program: evolution libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files --------------------------------------------------
*** Bug 503549 has been marked as a duplicate of this bug. ***
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 ***