GNOME Bugzilla – Bug 481402
crash in Tasks: Opening the evolution se...
Last modified: 2007-09-29 00:02:59 UTC
Version: 2.10 What were you doing when the application crashed? Opening the evolution session 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.7-85.fc7 #1 SMP Fri Sep 21 19:59:51 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: glass-icons Memory status: size: 556072960 vsize: 556072960 resident: 37351424 share: 27234304 rss: 37351424 rss_rlim: 18446744073709551615 CPU usage: start_time: 1191008237 rtime: 321 utime: 194 stime: 127 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496406672 (LWP 5799)] [New Thread 1105209680 (LWP 5811)] [New Thread 1084229968 (LWP 5808)] (no debugging symbols found) 0x000000332b20d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 166256
Thread 1 (Thread 46912496406672 (LWP 5799))
----------- .xsession-errors --------------------- (bug-buddy:5821): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (bug-buddy:5821): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (bug-buddy:5821): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (bug-buddy:5821): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 160 Minor opcode: 6 Resource id: 0x56 --------------------------------------------------
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 431459 ***