GNOME Bugzilla – Bug 515104
crash in Tasks: disabling an imap accoun...
Last modified: 2008-02-08 04:12:26 UTC
Version: 2.10 What were you doing when the application crashed? disabling an imap account. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.14-64.fc7 #1 SMP Sun Jan 20 23:54:08 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 213794816 vsize: 213794816 resident: 102625280 share: 36937728 rss: 102625280 rss_rlim: 4294967295 CPU usage: start_time: 1202418759 rtime: 5323 utime: 4478 stime: 845 cutime:0 cstime: 5 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 -1208404256 (LWP 13794)] [New Thread -1343226992 (LWP 14746)] [New Thread -1283044464 (LWP 14742)] [New Thread -1353716848 (LWP 14609)] [New Thread -1260786800 (LWP 13881)] [New Thread -1272136816 (LWP 13831)] [New Thread -1238287472 (LWP 13814)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 188479
Thread 1 (Thread -1208404256 (LWP 13794))
----------- .xsession-errors --------------------- (evolution:13794): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject' (evolution:13794): camel-CRITICAL **: camel_object_cast: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed (bug-buddy:14807): Gtk-WARNING **: Icon cache '/usr/share/pixmaps/hicolor/icon-theme.cache' is invalid (bug-buddy:14807): Gtk-WARNING **: Icon cache '/usr/share/pixmaps/hicolor/icon-theme.cache' is invalid (bug-buddy:14807): Gtk-WARNING **: Icon cache '/usr/share/pixmaps/hicolor/icon-theme.cache' is invalid (bug-buddy:14807): Gtk-WARNING **: Icon cache '/usr/share/pixmaps/hicolor/icon-theme.cache' is invalid --------------------------------------------------
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 324168 ***