GNOME Bugzilla – Bug 450977
crash in Tasks: parametrage evolution
Last modified: 2007-06-26 17:10:34 UTC
Version: 2.10 What were you doing when the application crashed? parametrage evolution Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 116555776 vsize: 116555776 resident: 45916160 share: 32997376 rss: 45916160 rss_rlim: 4294967295 CPU usage: start_time: 1182790488 rtime: 1671 utime: 1536 stime: 135 cutime:3 cstime: 10 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 -1208625440 (LWP 2438)] [New Thread -1240347760 (LWP 2630)] [New Thread -1229857904 (LWP 2529)] (no debugging symbols found) 0x00a9c402 in __kernel_vsyscall ()
+ Trace 143628
Thread 1 (Thread -1208625440 (LWP 2438))
----------- .xsession-errors (29 sec old) --------------------- (evolution:2438): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (evolution:2438): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (evolution:2438): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (evolution:2438): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (evolution:2438): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (evolution:2438): e-data-server-CRITICAL **: e_source_get_uri: assertion `E_IS_SOURCE (source)' failed (evolution:2438): GConf-CRITICAL **: gconf_client_set_string: assertion `val != NULL' failed (evolution:2438): e-data-server-ui-WARNING **: Le fichier de clés n'a pas de groupe « Passwords-Mail » --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 426227 ***