I'm using the kubuntu-backports of KDE 4.9 [https://launchpad.net/~kubuntu-ppa/+archive/backports] for Ubuntu 12.04 (precise) amd64. After the upgrade from 4:4.9.0 to 4:4.9.1 a few days ago, akonadi is running mad after login if not stop within a few seconds be typing akonadictl stop in a (hopefully quick opening konsole). To be very sure, I normally also 'kill -9' all processes listed by 'ps ax | grep akona'. Running mad in this case means that the system eats up all cpu-time, effectively making the system unusable within around 1 minute. Reproducible: Always Steps to Reproduce: 1. Just log in. Actual Results: Akonadi running mad, requiring a reboot after around 1 minute. Expected Results: Akonadi working in the background (or better not at all). For example, why are the akonadi processes not run as a low-priority nice value or in a process group that limit their cpu-usage?
I finally get around this by removing all files beginning with 'akona*' in the ~/.kde, ~/.local, and ~/.config directory structures. I still would suggest limiting the resource usage of the akonadi framework...
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.