Comment 115 for bug 175233

On a whole bunch of identical Ubuntu desktops with identical configurations, this problem is only affecting one user. Even when this user logs into a different desktop, the problem seems to follow them.

The evolution process gets stuck in futex_wait and after killing evolution and restarting, it will freeze again immediately. The only way to unfreeze and restart evolution is to kill evolution-data-server as well. This occurs about 2 to 4 times a day.

The problem only started after the user first tried to use the calender, however even after clearing out all evolution data and configuration the problem remained. The only common factor to all of this is the addressbook.db file. We will remove this and start a new addressbook.db file from scratch... lets hope this fixes the problem.