Bug 279127 - duplicate account folders
Summary: duplicate account folders
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-02 06:29 UTC by Silver Salonen
Modified: 2017-01-07 22:48 UTC (History)
1 user (show)

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

Attachments
Duplicate account folder for GMail (25.56 KB, image/png)
2011-08-02 07:44 UTC, Silver Salonen 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Silver Salonen 2011-08-02 06:29:37 UTC 
Version:           unspecified (using KDE 4.7.0) 
OS:                Linux

I have 3 IMAP-accounts set up in KMail (eg. 'GMail'). In the folder list two of these accounts have duplicate top-level folders aka account folders (eg. two accounts named 'GMail').

Reproducible: Always

Steps to Reproduce:
Run KMail

Actual Results:  
2 of my 3 IMAP-accounts have duplicate account folders

Expected Results:  
To not have the duplicates
Comment 1 Christophe Marin 2011-08-02 07:38:22 UTC 
Can you attach a screenshot please
Comment 2 Silver Salonen 2011-08-02 07:44:40 UTC 
Created attachment 62455 [details]
Duplicate account folder for GMail
Comment 3 Laurent Montel 2011-08-05 07:12:34 UTC 
Do you create them or import from kmail1 ?
Comment 4 Silver Salonen 2011-08-06 16:49:59 UTC 
I'm not sure, but I guess I imported them from KMail1.
Comment 5 Denis Kurz 2016-09-24 18:02:01 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 6 Denis Kurz 2017-01-07 22:48:35 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.