I'm using An AMD64 Athlon (2.4GHz)... with 32 bit Hardy Heron.
On startup I get this bug. Stopping the e-d-s process halts the cpu maxout.
However... I've discovered that starting the e-d-s again manually (simply by typing the session command for alarm notify into a terminal: /usr/lib/evolution/2.22/evolution-alarm-notify) starts up e-d-s, but *without* the bug.
This may help to confirm that it's a race very early on in session startup.
I'm using An AMD64 Athlon (2.4GHz)... with 32 bit Hardy Heron.
On startup I get this bug. Stopping the e-d-s process halts the cpu maxout.
However... I've discovered that starting the e-d-s again manually (simply by typing the session command for alarm notify into a terminal: /usr/lib/ evolution/ 2.22/evolution- alarm-notify) starts up e-d-s, but *without* the bug.
This may help to confirm that it's a race very early on in session startup.