New IMAP folder created does not appear in the folder tree view - Parent folder inaccessible?
Categories
(Thunderbird :: Folder and Message Lists, defect)
Tracking
(Not tracked)
People
(Reporter: richard.leger, Unassigned)
References
Details
Attachments
(1 file)
|
3.88 KB,
image/png
|
Details |
Unable to open the summary file.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0
Steps to reproduce:
Create a new folder name 'zero files' in a subfolder of my IMAP mailbox. Folder is successfully created server side (Cyrus IMAP server) and appears as subscribed folder in TB when checking for subscribed folder.
Actual results:
New created folder does not always appear in the folder tree view (left column) in TB upon successful creation/subscription server side. No error message appears.
Expected results:
The folder shall appear automatically and immediately in the view of folder so msg can be moved into it. This is the usual behaviour of TB.
|
Reporter | |
Comment 1•7 years ago
|
||
No error appearing in Activity Manager, last error seen in the console is as follow but may not be relevant to this bug...
An error occurred updating the cmd_sendUnsentMsgs command: [Exception... "Component returned failure code: 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsIMsgSendLater.hasUnsentMessages]" nsresult: "0xc1f30001 (NS_ERROR_NOT_INITIALIZED)" location: "JS frame :: chrome://messenger/content/mail3PaneWindowCommands.js :: IsSendUnsentMsgsEnabled :: line 1195" data: no] globalOverlay.js:71
goUpdateCommand chrome://global/content/globalOverlay.js:71
goUpdateMailMenuItems chrome://messenger/content/mailWindowOverlay.js:114
oncommandupdate chrome://messenger/content/messenger.xul:1
file_init chrome://messenger/content/mailWindowOverlay.js:134
initAppMenuPopup chrome://messenger/content/mailWindowOverlay.js:3472
onpopupshowing chrome://messenger/content/messenger.xul:1
|
|
Reporter | |
Comment 2•7 years ago
|
||
This is a random issue, sometime it works sometime it does not... I would say 50%/50% chances... Restarting TB is usually a way to fix the view issue in most cases... but not always convenient. Also going to check subscribed folder and then folding /unfolding mailbox tree root node does help trigger update of folder list view and fix the issue sometime but not always... it is like the folder list view refresh got 'stuck' somehow...
Also noticed in recent betas, the error message like "file path too long" appearing some time to time when trying to access some subfolders that seems not accessible for a temporary period of time. Not sure if it is linked to this bug but thought to mention it... if you retry accessing the same folder, msg disappear and folder access finally works. Wondering if it is linked to recent change in using UNC path for all file path accesses... which may increase the full length of most path and may end up to become above the 255 character limit of windows for file path... if \?\ is not used instead to prepend file path and over come the 255 file path limit of Windows.
|
|
Reporter | |
Comment 3•7 years ago
|
||
Currently happening on TB 67.0b1
|
|
Reporter | |
Comment 4•7 years ago
|
||
Was also happening in few previous beta version...
|
|
Reporter | |
Comment 5•7 years ago
|
||
It happened to me now again. When trying to access the parent folder of the 'zero files' newly created folder I get the attached alert message and cannot access the folder.
|
|
Reporter | |
Comment 6•7 years ago
|
||
Those are the last error message appearing in the console if that can be of any help...
NS_ERROR_FILE_TARGET_DOES_NOT_EXIST: Component returned failure code: 0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST) [nsIMsgFolder.updateFolder] DBViewWrapper.jsm:83
updateFolderAndNotifyOnLoad resource:///modules/DBViewWrapper.jsm:83
open resource:///modules/DBViewWrapper.jsm:775
show chrome://messenger/content/folderDisplay.js:787
FolderPaneSelectionChange chrome://messenger/content/commandglue.js:328
onselect chrome://messenger/content/messenger.xul:1
MozTreeChildren chrome://global/content/elements/tree.js:56
An error occurred updating the cmd_sendUnsentMsgs command: [Exception... "Component returned failure code: 0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST) [nsIMsgSendLater.hasUnsentMessages]" nsresult: "0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST)" location: "JS frame :: chrome://messenger/content/mail3PaneWindowCommands.js :: IsSendUnsentMsgsEnabled :: line 1195" data: no] globalOverlay.js:71
goUpdateCommand chrome://global/content/globalOverlay.js:71
goUpdateMailMenuItems chrome://messenger/content/mailWindowOverlay.js:114
oncommandupdate chrome://messenger/content/messenger.xul:1
file_init chrome://messenger/content/mailWindowOverlay.js:134
initAppMenuPopup chrome://messenger/content/mailWindowOverlay.js:3472
onpopupshowing chrome://messenger/content/messenger.xul:1
|
|
Reporter | |
Updated•7 years ago
|
|
|
Reporter | |
Comment 7•7 years ago
|
||
It seems the folder access issue is now happening with all the sub-folders. I can still access by Inbox, but as soon as I try to access a sub-folder (e.g first level folder under my Inbox), the same error message appears and the blue circle appears around the mouse arrow and as tab title prefix... like it is stuck in some sort of loop... I can still switch back to Inbox folder...
|
|
Reporter | |
Comment 8•7 years ago
|
||
Somehow it is now working again fine to access folders and sub-folders without having done anything in particular. Could it be then due to some maintenance task running in the background of TB blocking temporarily access to some files (lock?) required to access folders and sub-folders?
But I still cannot see my newly created folder in TB folder tree view... very strange all this :-)
|
||
Comment 9•7 years ago
|
||
(In reply to Richard Leger from comment #8)
Somehow it is now working again fine to access folders and sub-folders without having done anything in particular. Could it be then due to some maintenance task running in the background of TB blocking temporarily access to some files (lock?) required to access folders and sub-folders?
I don't think so
But I still cannot see my newly created folder in TB folder tree view... very strange all this :-)
|
|
Reporter | |
Comment 10•7 years ago
|
||
FYI still having the issue in 67.0b3 (64-bit)
|
|
Reporter | |
Comment 11•7 years ago
|
||
I still get the same error message when clicking on parent folder (as per Comment 5)
|
|
Reporter | |
Comment 12•7 years ago
|
||
The only way out of the situation is to close and restart Thunderbird application...
FYI, no errors appeared when creating the new folder and it was successfully created server side...
|
||
Comment 13•6 years ago
|
||
I don't think this is a problem we can solve in TB. Something's (very) wrong in your setup. Does this happen on a new profile?
|
|
Reporter | |
Comment 14•6 years ago
|
||
(In reply to Jorg K (GMT+2) from comment #13)
I don't think this is a problem we can solve in TB.
Let me disagree on this. The issue only occurs in TB. Even if not caused by TB it should be able to handle the situation and raise an error indicating what the issue is... not just freeze and stop access to the parent folder...
While difficult to nailed down due to random appearance making it difficult to reproduce, I don’t think it should be ignored. The very strange think is that it is random. Most of the time it works fine.
I haven’t noticed any issues to create new folder on windows nor in my mailbox via other email clients. This suddenly started to happen in TB following an upgrade... I have upgraded again to see if that help “fix” issue...
Last time I had it folder was properly created server side... so it may not be an IMAP issue (though not excluded considering the already numerous IMAP issues due to TB code), I now need to check client side... maybe indexing issue or view refresh issue... or some action stuck in a function loop somewhere... restarting TB fix it so it is not a system or configuration issue...
Something's (very) wrong in your setup.
Let me disagree. Same setup and profile used as before no change except TB version... (and Windows updates applied automatically).
Does this happen on a new profile?
I don’t see how that would help fix the issue. The issue shall not happen in my current profile in the first place...
Maybe next time I need to create a folder I’ll start a performance recording just before, so if issue occurs it may help identify where (in which function)... as console logs are of no help here...
The alternative would be to modify TB code involved in creation of new IMAP folders and refresh of the view... so to log in console every steps to identify which step is causing the issue... it could be that the pointer object to parent folder is destroy somehow in the process preventing access to it in the view... or something... or path to folder not properly escape or set in TB folder object... preventing further access...
|
|
||
Comment 15•6 years ago
•
|
||
(In reply to Richard Leger from comment #14)
Does this happen on a new profile?
I don’t see how that would help fix the issue. The issue shall not happen in my current profile in the first place...
We can only fix it if it is reproducible. So please try it on a new profile and let us know.
|
|
Reporter | |
Comment 17•6 years ago
|
||
This issue only happens randomly after a long usage of TB very difficult to reproduce as once it happens the only way to fix is to reboot TB after which it works fine for a while...
Still happening on TB 71.x branch... as per Bug 1603769 .
I have gathered error and debut logs from Error Console in Bug 1603769 Description...
Would that be of any help?
|
||
Comment 18•6 years ago
|
||
Reporter Richard,
Maybe you mentioned above but can you tell me the type of imap server you see this on most typically? I have created many imap folders in tb testing and debugging tb problems and don't think I have seen one fail to appear. (I have noticed one issue that when I delete a folder usually it stays in the list until I collapse/expand the full tree, then it goes away.)
Thanks.
|
|
||
Comment 19•5 years ago
|
||
(In reply to gene smith from comment #18)
Reporter Richard,
Maybe you mentioned above but can you tell me the type of imap server you see this on most typically? I have created many imap folders in tb testing and debugging tb problems and don't think I have seen one fail to appear. (I have noticed one issue that when I delete a folder usually it stays in the list until I collapse/expand the full tree, then it goes away.)
Thanks.
|
|
Reporter | |
Comment 20•5 years ago
|
||
(In reply to Wayne Mery (:wsmwk) from comment #19)
(In reply to gene smith from comment #18)
Reporter Richard,
Maybe you mentioned above but can you tell me the type of imap server you see this on most typically? I have created many imap folders in tb testing and debugging tb problems and don't think I have seen one fail to appear. (I have noticed one issue that when I delete a folder usually it stays in the list until I collapse/expand the full tree, then it goes away.)
Thanks.
I use Cyrus IMAP server.
I am now on branch 80.x beta and haven't seen the issue yet but I haven't created much folders lately either... and I have restarted TB a lot recently to test other perf issues that shall now be fixed in theory... so yet to be confirm if issue sorted or not after longer usage/testing/usage without much restart...
|
|
||
Comment 21•5 years ago
|
||
Please reopen if you still see this with curren tbeta.
Description
•