Bug 287268 - Folder labels disappeared after deleting "KMail Folders"
Summary: Folder labels disappeared after deleting "KMail Folders"
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 1.99.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-22 15:07 UTC by Unknown
Modified: 2017-01-07 22:40 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
No visible folder names in the "Local Folder" (5.97 KB, image/png)
2011-11-22 15:07 UTC, Unknown 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2011-11-22 15:07:39 UTC 
Created attachment 65939 [details]
No visible folder names in the "Local Folder"

Version:           1.99.0 (using KDE 4.7.3) 
OS:                Linux

I migrated something from KMail 1, then I deleted "KMail Folders", since it's unnecessary to have two "Local Folders".

After I deleted, I moved the pointer downwards and one-by-one all of the labels of the subfolders of the "Local Folders" are gone.

Normal account labels are not affected.

Reproducible: Didn't try



Expected Results:  
 

OS: Linux (x86_64) release 3.1.0-1.2-desktop
Compiler: gcc
Comment 1 Unknown 2011-11-22 15:11:13 UTC 
Ps.: interestingly, I cannot click on those which don't have an icon (the server icon). But when I select one the two labels with icon, on the top of the visible tabbar I see one of my two IMAP accounts' name.
Comment 2 Denis Kurz 2016-09-24 18:19:42 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 3 Denis Kurz 2017-01-07 22:40: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.