Bug 243632 - Akonadi migrator: run each time KMail is started
Summary: Akonadi migrator: run each time KMail is started
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Migration (show other bugs)
Version: 4.5
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Volker Krause
URL:
Keywords: akonadi-ports-regression
Depends on:
Blocks: 223438
  Show dependency tree / graph
 
Reported: 2010-07-05 10:21 UTC by Olivier Trichet
Modified: 2017-01-07 22:48 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Olivier Trichet 2010-07-05 10:21:06 UTC 
Version:           unspecified
OS:                Linux

Whenever I try to start kmail, the akonadi migrator is launched again.
I have:
  - the usual local folders.
  - A dimap account. This might be the cause of issue: the capability "UIDPLUS" is not present on my IMAP server (dovecot 1.0rc15) and I get an error message.


Reproducible: Always
Comment 1 Laurent Montel 2010-07-05 15:33:38 UTC 
If you obtains an error, kmail-migrator is canceled.
=> kmail will relauch it all the time.

Perhaps you can report this imap issue to imap composant

Regards
Comment 2 Olivier Trichet 2010-07-05 16:33:54 UTC 
1) Then at least, it should not import the messages that are cached locally again and again. Creating a new maildir resource in akonadi each time!

2) There is no point in copying these message into Akonadi if KMail is usuable afterward (KMail won't start).
Comment 3 Denis Kurz 2016-09-24 20:32:48 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 4 Denis Kurz 2017-01-07 22:48:03 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.