When starting knotes 4.13 the first time, you are asked whether your notes should be migrated to Akonadi. If akonadi doesn't run already, this migration reliably fails here. The akonadi server does get started automatically, but apparently there's a timeout. I got the following messages in the knotes-migrator window that appeared: Beginning KNotes migration... Creating instance of type akonadi_akonodes_resource Migration failed: Failed to create resource: Agent instance creation timed out. KNotes migration finished. The resource does get created, but knotes asks to do the migration again on next start of course. Reproducible: Always Steps to Reproduce: 1. Shut down Akonadi server 2. Remove knotes-migratorrc to force a migration 3. run knotes 4. in the dialog that appears, click on "Migrate now" Actual Results: Akonadi server gets started, but the migration fails. The resource gets created, but no notes are migrated. Expected Results: Successful migration. I guess this is more a general problem in Akonadi, so please reassign if necessary. Sometimes I get this instead: Beginning KNotes migration... Creating instance of type akonadi_akonotes_resource Instance "akonadi_akonotes_resource_8" synchronized Received root collections Could not find root collection for resource "akonadi_akonotes_resource_8" KNotes migration finished (and it fails as well) This is with Akonadi 1.12.1 and an external MariaDB database running on localhost. The setup works fine otherwise.
PS: I now even got the timeout (the first one) with akonadi running already. I had to retry 3 times to finally get my notes migrated again. This hasn't happened before.
(In reply to comment #1) > PS: I now even got the timeout (the first one) with akonadi running already. > I had to retry 3 times to finally get my notes migrated again. Please ignore this last comment, this was apparently caused by some left-over (hanging) akonadi_agent_launcher processes, that kept running even after stopping akonadi. (and I had a knotes process as well that I couldn't even kill) After a reboot it works again now when akonadi is running. I still get the timeouts when akonadi is not running, i.e. the original bug report is still valid.
Laurent promised the migration should be fixed in 4.13.1 http://www.aegiap.eu/kdeblog/2014/03/whats-new-in-kdepim-4-13-knotes/comment-page-1/#comment-12105
This is definitely fixed in the 4.13.1 version, you should upgrade.
(In reply to comment #4) > This is definitely fixed in the 4.13.1 version, you should upgrade. This indeed seems to be fixed in 4.13.1, I cannot reproduce it any more. To be clear though, this bug report was about the migration timing out when Akonadi was not running already. The migration not working at all is Bug#333640.