I have an akonadi resource "AkoNotes" pointin to .local/share/notes/ I've entered lots of books and pages into Kjots several days ago, but they do not appear in the folder .local/share/notes/, only top folders are created for books. They are, however, empty. (and no hidden folders are created). I can still access the data, but I guess it's somehow trapped in the akonadi cache? Also: In akonadiconsole, all the notes are listed as "unread".
I have similar problem, but I investigated it deeper: - when I try to rename (or to move) a book then kjots generates a message like "kjots error opening .... folder doesn't exist" - after that kjots continues work without any visible problems - BUT since that moment akonadi doesn't update kjots's appointed folder any more, any futher changes to this renamed book are kept somewhere inside akonadi, so I cannot, for example, backup them, moreover, I cannot extraxt my data from akonadi - WHAT HELPS: immediately after kjots generated mentioned above error message: --- close kontact, --- go to akonadi resources management, --- delete needed resource, --- manually check the folder, rename if necessary, ---- then newly create the same akonadi resource and start kontact ot kjots agan - it will import the folder wiithout problems, it will work and sore data untill the next rename/move The same effect happes regardless it is newly created akonadi resource during installation of kjot or my own folder pointed by new akonadi akonotes resource manually - itt seems that despite the problematic book already has a new name, kjots (or akonadi) stiil tries to reach it using wrong name.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!