https://bugs.kde.org/show_bug.cgi?id=320529
Tim Eberhardt <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Tim Eberhardt <[email protected]> --- I have a similar problem that could be related using KDE 4.11.2. After many months of use and several KDE upgrades akonadi became more and more unstabel (not starting at all, producing very high disk i/o, unresponsive, local mail folders in Kmail unaccessible/offline, not able to manage resources because akonadi would crash....). I then decided to make a new KDE profile and delete ~/.kde, ~/.config and ~/.local. After this I configured my mail/dav accounts (2 IMAP with several thousand mails, and one cal/carddav over owncloud). After everything was in sync again problems started again. This time mostly the maildir_resource for the local Kmail folders was causing problems and was offline. Akonadi then tried to create maildir agent after maildir agents and I had almost 15 of them in the end. Additionally after login akonadi produced high disk i/o and sometimes failed to start. I then decided to try a local mysql server instance instead of the embedded server. I deleted akonadi config and data again and setup mysql server with a database. It looked fine yesterday and everything was a bit faster. Today problems start again and the local maildir resource is offline again. WHAT in the world one could do to to get a stable Kmail with akonadi!? My akonadiserver.error is full of lines like these: "Cannot connect to agent instance with identifier 'akonadi_maildir_resource_0', error message: 'Could not get owner of name 'org.freedesktop.Akonadi.Resource.akonadi_maildir_resource_0': no such name'" "Cannot connect to agent instance with identifier 'akonadi_akonotes_resource_0', error message: 'Could not get owner of name 'org.freedesktop.Akonadi.Resource.akonadi_akonotes_resource_0': no such name'" -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list [email protected] https://mail.kde.org/mailman/listinfo/kdepim-bugs
