Created attachment 62448 [details] Corrupted config directory that when renamed, fixes the freeze Version: unspecified (using KDE 4.7.0) OS: Linux I noticed a very severe freeze that began recently. I had done a couple of things simultaneously, so it took a bit of work to triangulate akonadi as the culprit. My user account was only usable if I logged into the console due to the freeze, and it was not a GPU lockup that I know of, because I could not ssh into the machine from the network. The freeze is the whole system, all work is lost if it was not saved. I was able to fix the problem by renaming ~/.config/akonadi to something else then logout/login. Perhaps the akonadi database had become corrupted in some way that caused the machine to lock up. It is interesting because I have not used any software that connects or uses akonadi on this particular machine. I have saved the offending .config/akonadi directory and can make a tar file of it if a developer wants it to test what is happening. Reproducible: Always Steps to Reproduce: Use the corrupted config that is attached to this bug report. Actual Results: Severe freeze of the whole system, not just X. Expected Results: No freeze I have attached the offending config file.
The interesting part from your zip file is the 18 contact resources that were created and likely point to the same file
Well, I did not even use the contacts feature on this box. This machine was a clean install recently, and unless some application was creating contacts without my knowledge, I don't believe that I created those contacts. Either way, whatever the contacts did, locking the whole system is a pretty bad thing.
The agent multiplication issue has been fixed in kdepimlibs commit a9da6ca4d9823b39a81302cb1253339a3066157f a while ago.