GNOME Bugzilla – Bug 477287
crash in Email:
Last modified: 2007-09-24 17:41:33 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 137379840 vsize: 137379840 resident: 40013824 share: 33210368 rss: 40013824 rss_rlim: 4294967295 CPU usage: start_time: 1189883517 rtime: 83 utime: 74 stime: 9 cutime:2 cstime: 4 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 -1208297760 (LWP 3378)] [New Thread -1253053552 (LWP 3405)] [New Thread -1230386288 (LWP 3402)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 163162
Thread 1 (Thread -1208297760 (LWP 3378))
----------- .xsession-errors (25 sec old) --------------------- localuser:francesco being added to access control list SESSION_MANAGER=local/LupoSolitario.localdomain:/tmp/.ICE-unix/3156 Initializing nautilus-open-terminal extension CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:3378): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3378): 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 ***