Description of problem: Starting evolution with an exchange account configured causes massive CPU useage by evolution-exchange as soon as a message composition window is opened (even if not associated with the exchange account). CPU useage remains high until evolution itself is closed. Version-Release number of selected component (if applicable): $ rpm -qa | grep evolution evolution-data-server-2.22.2-1.fc9.x86_64 evolution-webcal-2.21.92-1.fc9.x86_64 evolution-exchange-2.22.2-1.fc9.x86_64 evolution-2.22.2-2.fc9.x86_64 How reproducible: Always Steps to Reproduce: 1.Configure an exchange server account 2.Compose a new message 3.Fry an egg on the CPU.
Aha, seems also to be seen on Ubuntu: https://bugs.launchpad.net/ubuntu/+source/evolution-exchange/+bug/110073 I can confirm that I do not have a GAL server entry when I see this bug.
Does the gnome-keyring-daemon process start freaking out too?
Yes, it does.
In /var/log/messages I see a lot of: Jun 8 18:21:29 localhost gnome-keyring-daemon[2734]: couldn't read 4 bytes from client: And actually, just now evolution just totally hung, as described in BZ #354041
Give evolution-data-server-2.22.3-2.fc9 a try. I think that might help. Should be landing in F9 updates-testing shortly.
evolution-data-server-2.22.3-2.fc9 has been submitted as an update for Fedora 9
evolution-data-server-2.22.3-2.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update evolution-data-server'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-6218
evolution-data-server-2.22.3-2.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.