Every time I start Kontact (in current Debian testing) it attempts to perform some resource migration (running KResource Migration Tool) and that process just hangs for a while and then exits. If run from the terminal, Kontact produces such errors:

Code: Select all

kres-migrator(22722): Unknown resource type:  "notes"
kontact(22718)/kresources: Akonadi migration failed!
kontact(22718)/kresources: command was:  ("kres-migrator", "--interactive-on-change", "--type", "notes", "--omit-client-bridge")
kontact(22718)/kresources: exit code:  0
kontact(22718)/kresources: stdout:  ""
kontact(22718)/kresources: stderr:  ""

Any idea what can be wrong? I didn't install kde-full in Debian, so I assume some packages can be missing for whatever reason.

UPDATE: This can be fixed by running knotes manually first (I never used it before, so some files were missing that migrating tool probably expected to exist).

Actually, I'm taking that back, I still have the same issue after restarting knotes. When running knotes from the terminal, it produces:

Code: Select all

res-migrator(2002): Unknown resource type:  "notes"                                                                                                                                         
knotes(2000)/kresources: Akonadi migration failed!                                                                                                                                           
knotes(2000)/kresources: command was:  ("kres-migrator", "--interactive-on-change", "--type", "notes", "--omit-client-bridge")                                                               
knotes(2000)/kresources: exit code:  0                                                                                                                                                       
knotes(2000)/kresources: stdout:  ""                                                                                                                                                         
knotes(2000)/kresources: stderr:  ""

It looks like it was caused by Debian testing mixing KDE 4.12 and 4.13 packages. Now after the recent update, more packages were bumped to 4.13 and this problem is gone.