Bug 257319 - KMail2 cannot import the old KMail maildirs / folders from ~/.Mail/
Summary: KMail2 cannot import the old KMail maildirs / folders from ~/.Mail/
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Migration (show other bugs)
Version: 1.0.0
Platform: Mandriva RPMs Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-19 14:00 UTC by Shlomi Fish
Modified: 2017-01-07 21:29 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Shlomi Fish 2010-11-19 14:00:15 UTC 
Version:           2.0.89 (using Devel) 
OS:                Linux

KMail2 cannot import the old KMail maildirs  / folders from ~/.Mail. kmail-migrator gets stuck after emitting:

kmail-migrator(14567) AbstractCollectionMigrator::Private::resourceStatusChanged: resource= "akonadi_mixedmaildir_resource_7" oldStatus= 2 message= "No usable storage location configured." newStatus 1 message= "Synchronizing email folders"

It does not consume any CPU or I/O. Furthermore, I tried adding the ~/.Mail/ as a KMail folder directly in the KMail settings dialog and it's stuck at "Synchronizing email folders (0%)" (without consuming any CPU or I/O.).

As a result of all that I have no access to all my old folders.

I'm using the KDE svn snapshot on Mandriva Linux Cooker from the Cooker RPMs.

Reproducible: Always
Comment 1 Laurent Montel 2010-11-29 13:33:47 UTC 
I tested kmail-migrator yesterday and it worked fine to import local messages.
Do you have more infos ?
Comment 2 Shlomi Fish 2010-11-29 13:40:16 UTC 
(In reply to comment #1)
> I tested kmail-migrator yesterday and it worked fine to import local messages.
> Do you have more infos ?

Which info do you want?

In the meanwhile, I've compiled and installed an old version of KMail under /opt because KMail2 does not run at all. This KMail from kdepim-4.4.x runs fine after I reset the Akonadi configuration, and did some other tweaks.

Regards,

-- Shlomi Fish
Comment 3 S. Burmeister 2011-03-15 13:33:05 UTC 
This might be the same issue as bug 267864.
Comment 4 Denis Kurz 2016-09-24 20:37:40 UTC 
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 5 Denis Kurz 2017-01-07 21:29:18 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.