GNOME Bugzilla – Bug 512999
crash in Tasks: First time trying to use
Last modified: 2008-01-30 10:04:08 UTC
What were you doing when the application crashed? First time trying to use 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 130301952 vsize: 130301952 resident: 27623424 share: 18456576 rss: 27623424 rss_rlim: 4294967295 CPU usage: start_time: 1201668600 rtime: 218 utime: 197 stime: 21 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 -1209186592 (LWP 3306)] [New Thread -1286284400 (LWP 3380)] [New Thread -1272329328 (LWP 3377)] (no debugging symbols found) 0x004f8402 in __kernel_vsyscall ()
+ Trace 187310
Thread 1 (Thread -1209186592 (LWP 3306))
----------- .xsession-errors (11 sec old) --------------------- localuser:root being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/3010 CalDAV Eplugin starting up ... ** (evolution:3306): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3306): 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 (evolution:3306): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (evolution:3306): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail' (evolution:3306): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 --------------------------------------------------
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 ***