GNOME Bugzilla – Bug 493269
crash in Tasks: starting up, sometimes i...
Last modified: 2007-11-05 23:35:27 UTC
Version: 2.10 What were you doing when the application crashed? starting up, sometimes it works, says can't sync. As if a possible disk error causes ian inconsistency in a file, and the system can't rescan it. 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.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 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: 175669248 vsize: 175669248 resident: 75644928 share: 26652672 rss: 75644928 rss_rlim: 4294967295 CPU usage: start_time: 1194155098 rtime: 3886 utime: 3358 stime: 528 cutime:4 cstime: 8 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 -1208219936 (LWP 3736)] [New Thread -1298564208 (LWP 3797)] [New Thread -1227478128 (LWP 3769)] [New Thread -1237967984 (LWP 3766)] [New Thread -1216988272 (LWP 3764)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 175020
Thread 5 (Thread -1216988272 (LWP 3764))
----------- .xsession-errors --------------------- (bug-buddy:3801): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (bug-buddy:3801): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (bug-buddy:3801): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (bug-buddy:3801): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x4d --------------------------------------------------
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 339602 ***