GNOME Bugzilla – Bug 491091
crash in Email: ricezione mail da tiscal...
Last modified: 2007-11-05 17:51:39 UTC
Version: 2.10 What were you doing when the application crashed? ricezione mail da tiscali 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: Glider Icon Theme: gnome Memory status: size: 133042176 vsize: 133042176 resident: 43843584 share: 30715904 rss: 43843584 rss_rlim: 4294967295 CPU usage: start_time: 1193604557 rtime: 1154 utime: 982 stime: 172 cutime:92 cstime: 23 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 -1208284432 (LWP 2838)] [New Thread -1328641136 (LWP 3010)] [New Thread -1217553520 (LWP 2904)] [New Thread -1275925616 (LWP 2852)] [New Thread -1228043376 (LWP 2848)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 173450
Thread 1 (Thread -1208284432 (LWP 2838))
----------- .xsession-errors --------------------- (system-config-securitylevel:3025): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (system-config-securitylevel:3025): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (system-config-securitylevel:3025): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (system-config-securitylevel:3025): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid ...Too much output, ignoring rest... --------------------------------------------------
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 456367 ***
*** Bug 493748 has been marked as a duplicate of this bug. ***