[knotes] [Bug 334357] New: knotes migration fails if akonadi is not running

[Wolfgang Bauer]

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

            Bug ID: 334357
           Summary: knotes migration fails if akonadi is not running
    Classification: Unclassified
           Product: knotes
           Version: 4.13
          Platform: openSUSE RPMs
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: kdepim-bugs at kde.org
          Reporter: wbauer at tmo.at
                CC: myriam at kde.org

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.

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