Obviously the GUI assistant to create an akonadi ressource does create folder structures on the harddrive before user confirmation by clicking on "ok". Aborting leaves the folder structure on the harddrive... Reproducible: Always Steps to Reproduce: 1. cange local mail folder ressource location to something other than ~/.local/share/local-mail 2. start creating an akonote or another maildir ressource with the akonadi assistant or akonadi console 3. Abort the creation by hitting "abort" Actual Results: a new folder local-mail is created though the user never asked the system to do so. ON the contrary demanded aborting the process... Expected Results: don't create folders until the user hits "ok- I confirm" this seems to be a minor complaint but I belive it is not. the newly created folders interfer with users trying to reset to default, as fodlers are still in place, it's confusing and in the case of knotes creating the "local-mail"-folder it is plain wrong.
After two years not even a comment... why does everybody always tell users to contribute by reporting bugs? This clearly doesn't get any attention at all. I am done with it.
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!