Version: unspecified (using KDE 4.5.85) OS: Linux I have 2 IMAP accounts (without cache) in KMail. After upgrading to 4.6 beta2, after launching kmail, KMail Migration Tool starts and tries to convert my IMAP accounts. The 1st thing it said: $ /usr/bin/kmail kmail-migrator(10533)/libakonadi: Unable to obtain agent type for default resource agent configuration "/usr/share/kde4/apps/akonadi/firstrun/defaultnotebook" After that Soprano gives many errors, eg: "/usr/bin/kmail-migrator(10533)" Soprano: "org.freedesktop.DBus.Error.ServiceUnknown - The name org.kde.nepomuk.services.nepomukstorage was not provided by any .service files" "/usr/bin/kmail-migrator(10533)" Soprano: "QLocalSocket::connectToServer: Invalid name" "/usr/bin/kmail-migrator(10533)" Soprano: "org.freedesktop.DBus.Error.ServiceUnknown - The name org.kde.nepomuk.services.nepomukstorage was not provided by any .service files" "/usr/bin/kmail-migrator(10533)" Soprano: "QLocalSocket::connectToServer: Invalid name" ... And finally: "/usr/bin/kmail-migrator(10533)" Soprano: "Unsupported operation (2)": "Invalid model" kde(10530): Communication problem with "kmail2" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." " kmail-migrator(10533): "Migration of 'Piimariiul' to Akonadi resource failed: Resource 'Piimariiul' did not create any folders" Then the migration-tool goes to the next IMAP account which is GMail and gets stuck in there, ie. does nothing forever. Process 'kmail-migrator' takes minimal resources meanwhile (1% CPU, 4.2 MB RAM). Reproducible: Always Steps to Reproduce: After the 1st time I deleted .kde4/share/apps/kmail2, .kde4/share/config/kmail2rc and .kde4/share/config/kmail-migratorrc, and started again. Still the same..
So the Soprano errors were because I didn't have Nepomuk running. After enabling it, the errors are gone. And although kmail-migrator thinks that kmail crashed, it didn't. After I close the migration windows, they both (kmail and kmail-migrator) keep running.
Aha.. I logged out and back in again and now migration seemes to work. Maybe it was because I just installed kmail after upgrading (which deleted kmail because of dependencies) while already being logged into KDE :)
Closing the report since it works now for the author.