GNOME Bugzilla – Bug 472548
crash in Tasks: selecting a email folder...
Last modified: 2007-09-24 16:35:17 UTC
Version: 2.10 What were you doing when the application crashed? selecting a email folder to view contents 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux Memory status: size: 128110592 vsize: 128110592 resident: 48869376 share: 35622912 rss: 48869376 rss_rlim: 4294967295 CPU usage: start_time: 1188656327 rtime: 1013 utime: 898 stime: 115 cutime:3 cstime: 13 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 -1208177936 (LWP 21810)] [New Thread -1269326960 (LWP 21978)] [New Thread -1227367536 (LWP 21977)] [New Thread -1238250608 (LWP 21884)] [New Thread -1216877680 (LWP 21883)] [New Thread -1248347248 (LWP 21852)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 159632
Thread 1 (Thread -1208177936 (LWP 21810))
----------- .xsession-errors (222385 sec old) --------------------- (gnome-panel:2992): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (gnome-panel:2992): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (gnome-panel:2992): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (gnome-panel:2992): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid ...Too much output, ignoring rest... --------------------------------------------------
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 438276 ***