[kdepim-users] kmail2 migration with 4.8RC - still not there

[Andras Mantia]

Martin Koller wrote:

> Hi,
> 
> I'm trying to migrate my kmail1 setup to kmail2 - for testing before
> really using it, I copied everything (~/Mail ~/.local ~/.config ~/.kde4)
> into a virtual machine (vbox) running openSuse 12.1/32bit.
> 
> I upgraded KDE to the packages from KDE trunk (e.g.
> kdepim4-4.7.80-1.2.i586, although the Help menu still tells me that this
> is KDE 4.7.3 ...)

Known "issue", as kdelibs is still 4.7.x.

> Then I simply started "kmail-migrator --interactive" on the commandline.
> I saw that it created the mySQL db, etc. and showed the migration dialog,
> which ended in "success". Perfect, I thought ... but:

All the rest indicates that migration didn't go well. As don't know that 
code, I can't comment in detail. Let's hope Kevin shows up (he reads this 
list from time to time) and can help you. What you did looks helpful though, 
it could help him to identify some more bugs inside the migration, 
especially if you can reliabily reproduce the described behavior.
If you want to test how KMail works when you import the data manually, 
follow the userbase article: 
http://userbase.kde.org/index.php?title=KMail/FAQs_Hints_and_Tips#Clean_start_after_a_failed_migration

> In the konsole where I started the migration I now get continuously 3
> times per second the following message:
> 
> akonadi_maildispatcher_agent(12469)/libakonadi: Resource id's don't match:
>  "akonadi_maildir_resource_0" "akonadi_mixedmaildir_resource_0"
> 
> What does that mean ?

Most probably inconsistent database created by the migrator.

> Also, mysqld, akonadiserver and akonadi_mixedmaildir_resource are sharing
> the CPU, which is at 100% for some time already. Question: is there some
> experience with how long this (I assume) initial filling of the DB takes ?
> (find Mail/|wc -l results in 99210)

Hard to judge, but should be less than an hour IMO. 

> Sometimes (about every 30 messages from above) I also get this output:
> 
> akonadi_nepomuk_feeder(12468) ItemQueue::removeDataResult: "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."

Sorry, no idea.

> My mail setup has only local mbox and maildir files, 

Are they mixed (like in KMail1) or separate maildir and mbox files? 

> no IMAP etc.
> The migration created the following mail related resources:
> - 2 POP3 resources (which can't download data as I disabled the network to
> be sure not to download my real mails) 
> - "Local Folders" maildir
> - 2 local mbox file resource
> - "Kmail Folders"
The last is your imported "old" KMail folder.

> Interesting is also: I now started "kmail" in a second konsole session,
> and kmail pops up the "Do you want to migrate now?" dialog ... why that ?
> I already ran it by myself ... ?

Maybe this goes away once everything is done (CPU usage goes down in the 
akonadi resources)? Just a wild guess. If not, it means the config file was 
not properly updated after the migration run.

> That's ok, but why does kmail try to run it then ?

Seems like a bug, report this (as you wrote down here), for KMail2 and 
migration.

> Then kmail terminates and konsole shows:
> 
> kmail2(12622)/libakonadi Akonadi::GetLockJob::Private::timeout: Timeout
> trying to get lock. Check who has acquired the name
> "org.kde.pim.SpecialCollections" on DBus, using qdbus or qdbusviewer.
> kmail2(12622)/libakonadi
> Akonadi::SpecialCollectionsRequestJobPrivate::lockResult: Failed to get
> lock: "Zeitüberschreitung beim Erhalten der Sperre." kmail2(12622)
> MailCommon::Kernel::emergencyExit: "In KMail ist ein schwerwiegender
> Fehler aufgetreten. Das Programm wird beendet.

This also looks some messing up with the migration. KMail need some special 
folders to run (Inbox, Outbox, etc) and seems it can't access them.
> 
> ... which I assume is due to mysqld, akonadiserver and
> akonadi_mixedmaildir_resource still filling the DB. Is that correct ?

Might be.

> Note: I tried this already yesterday with KDE 4.7.2 and let the system run
> over night, but 12 hours later the CPU was still at 100% so I stopped this
> test.

That is definitely worrying.

I suggest:
- please keep your non-migrated data somewhere, so you can reproduce the 
problems and help the developer fix them
- try a clean import instead of migrating to see if this gives you an usable 
KMail (it should).

Andras
_______________________________________________
KDE PIM users mailing list
Subscription management: https://mail.kde.org/mailman/listinfo/kdepim-users