Bug 281732 - on conversion the account "cache of old Kmail disconnect IMAP mails" is added to favourites
Summary: on conversion the account "cache of old Kmail disconnect IMAP mails" is added...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Migration (show other bugs)
Version: 4.7
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-10 06:33 UTC by m.wege
Modified: 2017-01-07 22:50 UTC (History)
0 users

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 m.wege 2011-09-10 06:33:43 UTC 
Version:           1.99.0 (using KDE 4.7.0) 
OS:                Linux

On conversion the account "cache of old Kmail disconnect IMAP mails" is added to favourites.

Reproducible: Didn't try

Steps to Reproduce:
Convert Kmail1-account with disconnect IMAP account (may be it is also necessary to have other favourite folders there)

Actual Results:  
The account "cache of old Kmail disconnect IMAP mails" is added to favourites. This account can not be removed, renamed (a silly long name which takes much space there) and finally does not make any sense there, since when you click on it, nothing is shown (since it is the account, it does not contain any mails).

Expected Results:  
The "cache of old Kmail disconnect IMAP mails" should not be added to favourite on conversion.

OS: Linux (x86_64) release 3.0.0-10-generic
Compiler: gcc
Comment 1 m.wege 2012-03-07 13:54:50 UTC 
Can not tell, if still valid because I do not have an account to convert anymore.
Comment 2 Denis Kurz 2016-09-24 20:41:43 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 3 Denis Kurz 2017-01-07 22:50:43 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.