https://bugs.kde.org/show_bug.cgi?id=333640
--- Comment #60 from Wolfgang Bauer <wba...@tmo.at> --- (In reply to comment #58) > (In reply to comment #57) > > So please check that ~/.kde/share/config/kresources/notes/stdrc exists and > > Wow great! Thanx for this magic file ... seems you know my harddrive better > than I myself. This brought me a step closer. The dialog actually promises > to convert 35 notes. Well, I stumbled over the same "problem" when trying to reproduce bug#334357 with 4.13.1. I wanted to do it with a new user to not pollute my Akonadi settings/database, so I copied over my user's ~/.kde4/share/apps/knotes/ but no notes were migrated. Then I noticed that there's no actual kresource defined (because it was a fresh account). (In reply to comment #59) > Strange, this morning, after restarting my machine I got three sets of my > old notes. I could remove two of them and keep the third. According to > akonadi they should reside in a folder .local/share/notes/11JIk70hpr/ which > didn't exist. So I created it manually. Hm. The akonotes resource should create the folder manually when syncing the notes to the disk, Akonadi is a cache between the applications (knotes in this case) and the data itself (i.e. the notes). You could try to synchronize the notes manually in akonadiconsole, right-click on the resource on the "Browser" tab. > Now, when I add new notes, they > automatically appear in that folder in a subfolder "new". But the other > converted notes somehow linger around in hyperspace and don't materialize on > my harddrive. At least I don't know where? Probably in the Akonadi database. You should be able to remove them in knotes and in akonadiconsole. And remove the unwanted resources as well, either in akonadiconsole or Systemsettings->Personal Information->Akonadi Resources Configuration. > Even if I change their content (that's why I know, they were not written > back to the old notes.ics source they came from). A few times I just got > some weird dialog asking me to keep the left or right version. That dialog appears when a conflict is detected between the cached version and the file on disk (f.e. if the file is changed by a different application). I saw that a lot in KMail in earlier versions, seems to be some timing issue. Select the version you want to keep and it should work. You could try to clean up your akonadi database with "akonadictl fsck" or even "akonadictl vacuum". But that's completely unrelated to this bug report now. If you cannot get it to work, please file a new bug about your problem(s). Or ask in the forums. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
