1. The following error is reported each time the mouse is clicked on a local folder: 1.1.. "Local Folder: Maildir "for collection" is invalid". Reproducible: Always Steps to Reproduce: 1. Click a mouse on a mail directory contained in the Local Folder. Actual Results: 1. The following error is reported each time the mouse is clicked on a local folder: 1.1.. "Local Folder: Maildir "for collection" is invalid". Expected Results: 1. There should be no such error message. 1, The mail directory bearing the name "for collection" was not created by the user. 2. It is not clear from where the Kmail module of KDE Kontact is getting this directory name.
1. The aforementioned error message is reported twice for each click on a local mail directory.
what do you do before it ? Removed folder ? etc.
I did nothing unusual before it. I did not delete, move, or create a folder before clicking on a folder with the mouse. I just clicked the mouse randomly on a folder in Kmail and it results in an error message. I did it just now to verify it before I responded to your query by clicking on various folders. The error message is displayed for each click on a different folder. On 9 May 2012 08:12, Laurent Montel <montel@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=299653 > > Laurent Montel <montel@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |montel@kde.org > > --- Comment #2 from Laurent Montel <montel@kde.org> --- > what do you do before it ? > Removed folder ? etc. > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug. >
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.
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.