Bug 363976 - kmail moans 'die ressource "XXXX" funktioniert nicht' because subdirectories tmp, new and cur are missing
Summary: kmail moans 'die ressource "XXXX" funktioniert nicht' because subdirectories ...
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.14.10
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-05 11:22 UTC by Dieter Jurzitza
Modified: 2022-11-22 05:13 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dieter Jurzitza 2016-06-05 11:22:47 UTC
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.
Comment 1 Justin Zobel 2022-10-21 00:17:42 UTC
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!
Comment 2 Dieter Jurzitza 2022-10-23 08:39:44 UTC
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
Comment 3 Bug Janitor Service 2022-11-07 05:09:17 UTC
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!
Comment 4 Bug Janitor Service 2022-11-22 05:13:05 UTC
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!