[Akonadi] [Bug 336581] accidental database loss causes Akonadi / KMail to silently break correct folder assignments

bugzilla_noreply at kde.org bugzilla_noreply at kde.org
Fri Jul 1 10:14:17 BST 2022


https://bugs.kde.org/show_bug.cgi?id=336581

missoline at protonmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |missoline at protonmail.com

--- Comment #14 from missoline at protonmail.com ---
Just to confirm that the issue is still there for Kmail 5.20.2. The akonadi
database gets corrupted randomly (happened to me after a distro upgrade that
otherwise went perfectly fine) and after removing Akonadi's corrupted data
folders and syncing again, all folder associations were messed up. 

Can't way for the day when our whole company can start relying on KDE PIM's
framework. It looks very promising and the vision behind akonadi is brilliant,
but this data corruption issue is a deal breaker. I hope you manage to fix this
soon, stability and durability are so important for this kind of application. 

If a solution is known but what is lacking is manpower, please let the
community know so that we can try to organize sponsorship. This is such a
critical issue (I am referring to the data corruption. Folder assignment is
more a symptom. If data corruption wasn't there in the first place, folder
assignment mix up wouldn't be an issue. I feel it would probably be better to
fix the fragility of the storage system to make such symptoms non-issues by
removing a vast class of failure modes rather than rather than trying to come
up with global ids).

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Kdepim-bugs mailing list