GNOME Bugzilla – Bug 470559
crash in Tasks: nothing
Last modified: 2007-09-24 18:29:47 UTC
Version: 2.10 What were you doing when the application crashed? nothing 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 128393216 vsize: 128393216 resident: 39215104 share: 30085120 rss: 39215104 rss_rlim: 4294967295 CPU usage: start_time: 1188174002 rtime: 290 utime: 248 stime: 42 cutime:4 cstime: 13 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 -1208359200 (LWP 3382)] [New Thread -1220949104 (LWP 3553)] [New Thread -1315378288 (LWP 3501)] [New Thread -1294398576 (LWP 3499)] [New Thread -1283515504 (LWP 3498)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 158082
Thread 1 (Thread -1208359200 (LWP 3382))
----------- .xsession-errors (307 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 CalDAV Eplugin starting up ... 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 ** (evolution:3382): WARNING **: LDAP authentication failed (0xffffffff) evolution-shell-Message: Killing old version of evolution-data-server... 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 ***