GNOME Bugzilla – Bug 520930
crash in Email: Ascoltavo una radio in s...
Last modified: 2008-03-10 08:12:48 UTC
Version: 2.10 What were you doing when the application crashed? Ascoltavo una radio in streaming con mplayerplug-in sotto Mozilla Firefox 2.0, e modificavo le preferenze di Evolution->Calendario... 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.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 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: 128724992 vsize: 128724992 resident: 49315840 share: 35889152 rss: 49315840 rss_rlim: 4294967295 CPU usage: start_time: 1204878080 rtime: 760 utime: 676 stime: 84 cutime:0 cstime: 1 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 -1208949024 (LWP 3066)] [New Thread -1260823664 (LWP 3139)] [New Thread -1250333808 (LWP 3098)] [New Thread -1228940400 (LWP 3095)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 191600
Thread 1 (Thread -1208949024 (LWP 3066))
----------- .xsession-errors (2021 sec old) --------------------- (gnome-keyring-ask:3043): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (gnome-keyring-ask:3043): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (gnome-keyring-ask:3043): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (gnome-keyring-ask:3043): 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 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 447591 ***