GNOME Bugzilla – Bug 480577
crash in Tasks: System had just booted. ...
Last modified: 2007-09-26 17:42:27 UTC
What were you doing when the application crashed? System had just booted. Hadn't done anything else Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (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: 143695872 vsize: 143695872 resident: 42590208 share: 34816000 rss: 42590208 rss_rlim: 4294967295 CPU usage: start_time: 1190809699 rtime: 91 utime: 83 stime: 8 cutime:1 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 -1208297760 (LWP 3095)] [New Thread -1243616368 (LWP 3271)] [New Thread -1233126512 (LWP 3200)] (no debugging symbols found) 0x0060a402 in __kernel_vsyscall ()
+ Trace 165635
Thread 1 (Thread -1208297760 (LWP 3095))
----------- .xsession-errors (8 sec old) --------------------- localuser:cdeniz being added to access control list SESSION_MANAGER=local/skidmark.localdomain:/tmp/.ICE-unix/2886 CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:3095): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3095): 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 ***