After renaming a maildir local folder, every time it or anything inside it (messages or subfolders) is clicked, a message like the following appearas in the systray notification area: "Local folders: The Maildir '/home/username/.local/share/local-mail/.inbox.directory/teste in the collection 'test' is invalid." In this case, a folder named "teste" was renamed to "test". The message is translated from portuguese, so it may not be exactly that in english. Please see the attached screenshot. To solve this, I have to rename the problematic folder temporarily to any other name, create another folder with the name I want, move the contents from the problematic folder to this new one I have just created and then remove the old folder. Reproducible: Always Steps to Reproduce: 1. Create a local maildir folder 2. Rename the folder you have just created 3. Click on another folder and then go back to the folder you have created Actual Results: Error messages like the one mentioned in the bug description pop up in the notification area. One message pops up for each item stored in the renamed folder. Expected Results: No error message should be issued when the rename folder is accessed.
Created attachment 74540 [details] An example of notification pop up that I get after a folder is renamed
I can confirm this bug. It is happing on my system too. I can not fix it.
Is the problem still present if you "logout" and new-"loging" after "rename" (2) and before (3)?
The problem is still present in 4.10. What do you mean by "logout" and new-"logging"? Logout KDE? Close KMail and reopen it? Close KMail, restart Akonadi and reopen KMail?
I mean: Logout from KDE. And login again. This is necessary to get some daemons re-startet.
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.