I struggled for quite a while analyzing a silly bug. Kmail2 worked but always said 'Die Ressource "XXXX" funktioniert nicht' on start and on entering arbitrary subfolders of XXXX (say /var/spool/mail/oscar) because I am using maildir format. At the end of the day it showed that this message (not very helpful, indeed) was caused by the fact that subdirectories were missing. So, there was a directory "trash", but the directories "trash/new", "trash/cur" and "trash/tmp" were missing. Why aren't they auto - generated - I cannot imagine anything harmful from them, but an error message (that actually does not give a pointer to the problem) is misleading and serves for nothing in this case. So, I'd suggest to auto-generate those folders if they are missing - and kmail ought to know what is actually causing the error message so it should be possible to add the folders at the right position. Thank you for looking into this take care Dieter Jurzitza Reproducible: Always Actual Results: Error message "Die resource XXXX funktioniert nicht" though it works. Expected Results: Auto - generation of missing subdirectories tmp, cur, new.
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!
Ok, the problem is still there - but the root cause is a different one. I am still using the above mentioned path structure and I still get the "die ressource "XXXX" funktioniert nicht" (ressource unavailable I think is the right translation ...) message every other time. However this happens even with the above mentioned directories being there. So, problem persists but the root cause I pointed to in this bug is not correct. Should I close this one and open a new one? What is the best way to treat the issue? Thank you take care Dieter Jurzitza
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!