If Akonadi or the computer crashes, it's very likely that the underlying MySQL database is left in a corrupt state, and Akonadi fails to start for the next time. The only solution is to delete the database, which yields a complete resync of e-mail folders, for example, that can take several hours leaving the user without e-mail access for that long. This fragile nature of the database should be addressed. Maybe by using a more robust backend, or by somehow forcing the MySQL server to keep data in a consistent state on disk. Reproducible: Sometimes Steps to Reproduce: Pull the plug from the computer (happens). Actual Results: Akonadi Server Self-Test reports 'MySQL server log contains errors' when KMail is started for the next time. Expected Results: It should tolerate errors like this.
*** This bug has been marked as a duplicate of bug 286711 ***