GNOME Bugzilla – Bug 513880
crash in Tasks: I just started evolution...
Last modified: 2008-02-03 00:14:27 UTC
Version: 2.10 What were you doing when the application crashed? I just started evolution. 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.14-64.fc7 #1 SMP Sun Jan 20 23:54:08 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 118132736 vsize: 118132736 resident: 35360768 share: 29179904 rss: 35360768 rss_rlim: 4294967295 CPU usage: start_time: 1201957497 rtime: 80 utime: 69 stime: 11 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 -1208453408 (LWP 3410)] [New Thread -1254945904 (LWP 3457)] [New Thread -1221031024 (LWP 3432)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 187835
Thread 1 (Thread -1208453408 (LWP 3410))
----------- .xsession-errors --------------------- localuser:MF being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/3083 /usr/share/system-config-selinux/system-config-selinux.py:71: Warning: IA__g_object_get_valist: object class `GnomeProgram' has no property named `default-icon' xml = gtk.glade.XML ("/usr/share/system-config-selinux/system-config-selinux.glade", domain=PROGNAME) CalDAV Eplugin starting up ... ** (evolution:3410): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3410): 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 ***