GNOME Bugzilla – Bug 477444
crash in Email:
Last modified: 2007-09-24 17:41:13 UTC
Version: 2.10 What were you doing when the application crashed? 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 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: 126345216 vsize: 126345216 resident: 38232064 share: 31739904 rss: 38232064 rss_rlim: 4294967295 CPU usage: start_time: 1189939949 rtime: 73 utime: 63 stime: 10 cutime:3 cstime: 8 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 3144)] [New Thread -1237320816 (LWP 3184)] [New Thread -1225266288 (LWP 3181)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 163294
Thread 1 (Thread -1208445216 (LWP 3144))
----------- .xsession-errors --------------------- localuser:epi80 being added to access control list SESSION_MANAGER=local/host794:/tmp/.ICE-unix/2937 ** (gnome-session:2937): WARNING **: Host name lookup failure on localhost. CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:3144): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3144): 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 --------------------------------------------------
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 ***