GNOME Bugzilla – Bug 453709
crash in Email: Just start application
Last modified: 2007-07-11 18:40:08 UTC
What were you doing when the application crashed? Just start application 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.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 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: 94855168 vsize: 94855168 resident: 23347200 share: 14946304 rss: 23347200 rss_rlim: 4294967295 CPU usage: start_time: 1183560671 rtime: 177 utime: 153 stime: 24 cutime:0 cstime: 1 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 -1208895776 (LWP 3222)] (no debugging symbols found) 0x00afe402 in __kernel_vsyscall ()
+ Trace 145711
Thread 1 (Thread -1208895776 (LWP 3222))
----------- .xsession-errors (16 sec old) --------------------- SESSION_MANAGER=local/pasha:/tmp/.ICE-unix/2746 CalDAV Eplugin starting up ... (evolution:3086): evolution-smime-WARNING **: initializing security library without cert databases. (evolution:3086): e-data-server-DEBUG: Loaded default categories --- Hash table keys for warning below: --> file:///home/pasha (nautilus:3213): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:3213): GLib-CRITICAL **: g_hash_table_insert: assertion `hash_table != NULL' failed (nautilus:3213): GLib-CRITICAL **: g_hash_table_insert: assertion `hash_table != NULL' failed CalDAV Eplugin starting up ... --------------------------------------------------
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 425129 ***