*sigh*
I'm afraid I'm making a mess of this report, and I apologize for that.
Anyway, it turns out that I had already followed the advice of Chris
Trawick above, and turned off the Exchange Global Address List. After
turning that back on, I was able to reproduce the issue.
Evolution-running gdb
Bah. Never mind about the dbgsym not installable. I needed to remove
hardy-proposed from sources.list, and now it's installed.
However, in attempting to recreate the problem to get you a
stacktrace, I have found that I cannot reproduce it. In the interim
since I created this bug, I have run
Another workaround that seems to calm it down is to write your email,
send it, and then click the "Work Offline" button in the lower left hand
corner. Then click it again to Work Online, and your CPU usage should
be back to normal. Obviously this will be untenable if you keep an email
open all day
Public bug reported:
Binary package hint: gnome-keyring
When I use Evolution to create an email message, it interacts with the
gnome-keyring-daemon, and they both conspire to peg my CPU usage at
100%. Eventually, I need to run the "evolution --force-shutdown"
command. My messages get sent, but
I am still seeing this problem on a fresh install of Ubuntu Dapper.
Number of workspaces is not remembered across sessions, despite changing
the number of workspaces every time I login via the applet's
preferences.
Note that I have uninstalled metacity in favor of sawfish. I still have
libmetacit
