Bug 279221 - timeout kmail2 migration
Summary: timeout kmail2 migration
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Migration (show other bugs)
Version: 4.7
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-02 22:29 UTC by Ferdinand Gassauer
Modified: 2017-01-07 22:41 UTC (History)
0 users

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 Ferdinand Gassauer 2011-08-02 22:29:54 UTC 
Version:           1.99.0 (using KDE 4.7.0) 
OS:                Linux

I had to start 
kmail-migrator --interactive
multiple times
due to (network) timeouts, seems that the system was very busy and could not reach remote imap resources

Reproducible: Sometimes

Steps to Reproduce:
after restarting the migration manually 3 times everything was fine

Actual Results:  
automatic migration failed

Expected Results:  
timeout should retry 
starting kmail-migrator --interactive manualy is expert stuff
Comment 1 Ferdinand Gassauer 2011-08-03 07:35:03 UTC 
may be or not, 
aftter migration I found a lot of "unconfigured" mail accounts

and 2 (two) "KMail Folders"
both ready, one of them pointing nowhere

had to remove them manualy
Comment 2 Christophe Marin 2011-08-03 10:16:59 UTC 
> 1.99.0 (using KDE 4.7.0) 

Something is wrong here, this is not the KMail version shipped with KDE 4.7.0
Comment 3 Ferdinand Gassauer 2011-08-03 15:33:18 UTC 
Hmm,

in OpenSuSE kmail2 is called 4.7, but this can't be entered in the bug reporting
Comment 4 Denis Kurz 2016-09-24 20:45:01 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 22:41:55 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.