GNOME Bugzilla – Bug 483202
crash in Tasks: Nothing
Last modified: 2007-10-05 10:06:19 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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango Memory status: size: 164425728 vsize: 164425728 resident: 50438144 share: 39968768 rss: 50438144 rss_rlim: 4294967295 CPU usage: start_time: 1191470819 rtime: 278 utime: 235 stime: 43 cutime:0 cstime: 0 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 -1208469792 (LWP 29959)] [New Thread -1269884016 (LWP 30035)] [New Thread -1290863728 (LWP 29979)] [New Thread -1301353584 (LWP 29977)] [New Thread -1221059696 (LWP 29970)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 167591
Thread 1 (Thread -1208469792 (LWP 29959))
----------- .xsession-errors (314 sec old) --------------------- ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) Plugger: Unable to find pluggerrc file! CalDAV Eplugin starting up ... ** (evolution:29959): WARNING **: LDAP authentication failed (0xffffffff) 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 ***