GNOME Bugzilla – Bug 473531
crash in Tasks: Start the app. press f9
Last modified: 2007-10-11 17:04:58 UTC
Version: 2.10 What were you doing when the application crashed? Start the app. press f9 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 21:50:50 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Bluecurve Memory status: size: 664788992 vsize: 664788992 resident: 64172032 share: 53420032 rss: 64172032 rss_rlim: 18446744073709551615 CPU usage: start_time: 1188905030 rtime: 103 utime: 88 stime: 15 cutime:2 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912500601264 (LWP 2877)] [New Thread 1147169104 (LWP 2970)] [New Thread 1157658960 (LWP 2969)] [New Thread 1126189392 (LWP 2968)] [New Thread 1136679248 (LWP 2921)] [New Thread 1115699536 (LWP 2917)] [New Thread 1084229968 (LWP 2914)] (no debugging symbols found) 0x0000003e4ea0d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 160361
Thread 1 (Thread 46912500601264 (LWP 2877))
----------- .xsession-errors (9 sec old) --------------------- localuser:bos01 being added to access control list SESSION_MANAGER=local/wos01.msys.dom:/tmp/.ICE-unix/2695 CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:2877): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2877): 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 ***