GNOME Bugzilla – Bug 492432
crash in Tasks:
Last modified: 2007-11-02 02:42:20 UTC
Version: 2.10 What were you doing when the application crashed? 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.20-2936.fc7xen #1 SMP Fri Sep 21 12:07:35 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: 108220416 vsize: 108220416 resident: 37257216 share: 26210304 rss: 37257216 rss_rlim: 4294967295 CPU usage: start_time: 1193927522 rtime: 350 utime: 308 stime: 42 cutime:2 cstime: 2 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209121056 (LWP 3571)] [New Thread -1276658800 (LWP 3676)] (no debugging symbols found) 0x00977402 in __kernel_vsyscall ()
+ Trace 174412
Thread 2 (Thread -1276658800 (LWP 3676))
----------- .xsession-errors (22 sec old) --------------------- (evolution:3571): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (evolution:3571): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (evolution:3571): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (evolution:3571): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (evolution:3571): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed 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:3571): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail' (evolution:3571): e-data-server-WARNING **: Could not open converter for 'Latin-1' to 'UTF-8' charset --------------------------------------------------
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 445309 ***