GNOME Bugzilla – Bug 501990
crash in Tasks: I deleted email from my ...
Last modified: 2007-12-06 12:12:18 UTC
Version: 2.10 What were you doing when the application crashed? I deleted email from my inbox, then I push "arrow down" key and started to scroll throught emails. After very short while Evolution crashed (I menaged to skip maybe 5 emails). 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.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 138018816 vsize: 138018816 resident: 53354496 share: 43122688 rss: 53354496 rss_rlim: 4294967295 CPU usage: start_time: 1196929226 rtime: 1172 utime: 1046 stime: 126 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208215840 (LWP 2407)] [New Thread -1256199280 (LWP 2743)] [New Thread -1245709424 (LWP 2434)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 180933
Thread 1 (Thread -1208215840 (LWP 2407))
----------- .xsession-errors --------------------- camel-Message: -- camel-Message: -- camel-Message: -- camel-Message: -- camel-Message: -- camel-Message: -- Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. camel-Message: -- camel-Message: -- Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. camel-Message: -- camel-Message: -- camel-Message: -- --------------------------------------------------
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 364700 ***