GNOME Bugzilla – Bug 480924
crash in Evolution:
Last modified: 2008-05-02 10:39:59 UTC
What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21-2-486 #1 Wed Jul 11 03:17:09 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: StillLifeBrushed Memory status: size: 67366912 vsize: 67366912 resident: 13852672 share: 9412608 rss: 13852672 rss_rlim: 4294967295 CPU usage: start_time: 1190743401 rtime: 56 utime: 45 stime: 11 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/evolution-exchange-storage' (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 -1234810688 (LWP 21490)] [New Thread -1254192240 (LWP 17789)] [New Thread -1236776048 (LWP 21498)] (no debugging symbols found) 0xb6dd345d in poll () from /lib/libc.so.6
+ Trace 165894
Thread 2 (Thread -1254192240 (LWP 17789))
----------- .xsession-errors (8 sec old) --------------------- (eog:17697): Gtk-WARNING **: Icon cache '/usr/share/pixmaps/hicolor/icon-theme.cache' is invalid bad image index (eog:17697): Gtk-WARNING **: Icon cache '/usr/share/pixmaps/hicolor/icon-theme.cache' is invalid bad image index (eog:17697): Gtk-WARNING **: Icon cache '/usr/share/pixmaps/hicolor/icon-theme.cache' is invalid (evolution-2.10:21469): gtkhtml-WARNING **: Cannot create spell dictionary instance (iid:OAFIID:GNOME_Spell_Dictionary:0.3) (evolution-2.10:21469): Bonobo-WARNING **: Activation exception 'Falha ao ativar 'OAFIID:GNOME_Spell_Control:0.3'' --------------------------------------------------
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 332979 ***