Comment 10 for bug 125653

The only thing that comes to my mind right now is that something is hosed under the ~/.evolution directory. You can try two things:

1. rm -rf ~/.evolution/calendar (since it is the calendar init that is failing)

or

2. rm -rf ~.evolution (since this user has not really used Evo so far).

Then run Evo again. I would start with (1) above -- less drastic, and go to (2) if (1) did not do the trick.