GNOME Bugzilla – Bug 507774
crash in Tasks:
Last modified: 2008-01-07 09:42:06 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Enabled GTK+ Theme: Bluecurve-Tangerine Icon Theme: Crux Memory status: size: 161054720 vsize: 161054720 resident: 48439296 share: 37019648 rss: 48439296 rss_rlim: 4294967295 CPU usage: start_time: 1199684853 rtime: 472 utime: 426 stime: 46 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 -1208232224 (LWP 3228)] [New Thread -1281381488 (LWP 3290)] [New Thread -1291871344 (LWP 3287)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 184350
Thread 1 (Thread -1208232224 (LWP 3228))
----------- .xsession-errors --------------------- GTK Accessibility Module initialized GTK Accessibility Module initialized GTK Accessibility Module initialized Bonobo accessibility support initialized CalDAV Eplugin starting up ... ** (evolution:3228): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3228): 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:3228): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail' GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized --------------------------------------------------
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 ***