GNOME Bugzilla – Bug 485578
crash in Tasks: Setting evolution prefer...
Last modified: 2007-10-16 05:06:25 UTC
Version: 2.10 What were you doing when the application crashed? Setting evolution preferences. 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: Darkilouche Icon Theme: crystalsvg Memory status: size: 195948544 vsize: 195948544 resident: 66596864 share: 49094656 rss: 66596864 rss_rlim: 4294967295 CPU usage: start_time: 1192062831 rtime: 2329 utime: 2052 stime: 277 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 -1208953120 (LWP 3183)] [New Thread -1319736432 (LWP 4345)] [New Thread -1331299440 (LWP 4344)] [New Thread -1248425072 (LWP 3452)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 169381
Thread 1 (Thread -1208953120 (LWP 3183))
----------- .xsession-errors (6 sec old) --------------------- (evolution:3183): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (evolution:3183): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (evolution:3183): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (evolution:3183): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (evolution:3183): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (evolution:3183): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (evolution:3183): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed warning: .dynamic section for "/usr/lib/libpopt.so.0" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 407187 ***