GNOME Bugzilla – Bug 518030
crash in Email:
Last modified: 2008-02-23 13:13:03 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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 138584064 vsize: 138584064 resident: 47591424 share: 39571456 rss: 47591424 rss_rlim: 4294967295 CPU usage: start_time: 1194171978 rtime: 136 utime: 124 stime: 12 cutime:2 cstime: 5 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 -1209108768 (LWP 3170)] [New Thread -1256334448 (LWP 3252)] [New Thread -1224361072 (LWP 3207)] (no debugging symbols found) 0x00b1c8c1 in waitpid () from /lib/libpthread.so.0
+ Trace 190069
Thread 1 (Thread -1209108768 (LWP 3170))
----------- .xsession-errors (31 sec old) --------------------- localuser:root being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2958 Errore: errore di permessi in pam_timestamp_check CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:3170): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3170): 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 431459 ***