https://bugs.kde.org/show_bug.cgi?id=389607
--- Comment #6 from Nick <ndor...@gmail.com> --- Similar issues . akonadi fsck / vacuum reports many issues/messages but did not give to the user any hints on how to solve them . What about having an option akonadictl fix [ noRID | dirtyRID ...etc ] ? Such tool will reduce the number of bugs reported by akonadictl fsck Also, what about telling the users : 1) procedures of fixing issues 2) procedures of getting rid on unnnecessary messages and/or 3) procedures of cleaning up the akonadi db of "dead" records and above all 4) how the user should access akonadi mysql db which is handled [ start/stp] by akonadi . See bug 406856 recently opened Thanks . Nick -- You are receiving this mail because: You are the assignee for the bug.
