Re: All Akonadi agents at 100% CPU -- solved

2011-05-27 Thread Michael Schuerig
On Friday 27 May 2011, Michael Schuerig wrote: [...] Well, I finally got things in working order again by removing ~/.config/akonadi and recreating the respective agents. Google calendar and contacts resources (akonadi-kde-resource-googledata) still don't work; both write the same message to ~/

Re: All Akonadi agents at 100% CPU

2011-05-27 Thread Michael Schuerig
Also, I noticed that the akonadi_* processes are eating memory like mad. I've just killed a bunch of them at over 1GB (as shown in KDE's System Monitor). I've limited these processes to 10% CPU (using cpulimit) and after their automatic restart, each of them has already consumed 0:20 CPU time

All Akonadi agents at 100% CPU

2011-05-27 Thread Michael Schuerig
This morning I upgraded to the new 4.6.3 packages as they became available in unstable. The upgrade itself went smoothly, but when I rebooted and started a new KDE session, each of the five running Akonadi agents was at 100% CPU. After some unsuccessful manual attempts at downgrading things, I r