1603769 - Newly created IMAP folder via TB does not show in Thunderbird - Need to restart Thunderbird to be able to see the new folder

Status: RESOLVED DUPLICATE of bug 1543019

(Thunderbird :: Folder and Message Lists, defect)

Description

[Richard Leger]

In TB 71.0b4 (64bits) and since couple of beta version, when creating a new mail folder in IMAP mailbox, the folder is successfully created server side but does not shows up in Thunderbird till the application is restarted, after which folder appears and is usable.

The following error and debug message appear in Error Console...

TypeError: this.tree is null
calendar-task-tree-view.js:212:5
get rowCount chrome://calendar/content/calendar-task-tree-view.js:212
refresh chrome://calendar/content/calendar-task-tree.js:515
onLoad chrome://calendar/content/calendar-task-tree.js:36
notify resource://calendar/modules/utils/calDataUtils.jsm:40
notify resource://calendar/modules/utils/calDataUtils.jsm:67
onLoad jar:file:///C:/Users/richard/AppData/Roaming/Thunderbird/Profiles/cnant748.default/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}.xpi!/components/calCompositeCalendar.js:44
notify resource://calendar/modules/utils/calDataUtils.jsm:40
notify resource://calendar/modules/utils/calDataUtils.jsm:67
finalizeUpdatedItems jar:file:///C:/Users/richard/AppData/Roaming/Thunderbird/Profiles/cnant748.default/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}.xpi!/components/calDavCalendar.js:1255
onStopRequest resource://calendar/calendar-js/calDavRequestHandlers.js:820
Could not start Browser Toolbox, you need to enable it. ToolboxProcess.jsm:88:13
init resource://devtools/client/framework/ToolboxProcess.jsm:88
oncommand chrome://messenger/content/messenger.xul:1
NS_ERROR_FILE_TARGET_DOES_NOT_EXIST: Component returned failure code: 0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST) [nsIMsgSendLater.hasUnsentMessages] mail3PaneWindowCommands.js:1343
IsSendUnsentMsgsEnabled chrome://messenger/content/mail3PaneWindowCommands.js:1343
isCommandEnabled chrome://messenger/content/mail3PaneWindowCommands.js:588
isCommandEnabled chrome://messenger/content/mailTabs.js:834
isCommandEnabled chrome://messenger/content/tabmail.js:535
goUpdateCommand chrome://global/content/globalOverlay.js:84
goUpdateMailMenuItems chrome://messenger/content/mailWindowOverlay.js:159
oncommandupdate chrome://messenger/content/messenger.xul:1
file_init chrome://messenger/content/mailWindowOverlay.js:183
initAppMenuPopup chrome://messenger/content/mailWindowOverlay.js:3981
handleEvent chrome://messenger/content/customizableui/panelUI.js:343
_openPopupPromise resource:///modules/PanelMultiView.jsm:542
AsyncFunctionNext self-hosted:689
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 1343" data: no] globalOverlay.js:89
goUpdateCommand chrome://global/content/globalOverlay.js:89
goUpdateMailMenuItems chrome://messenger/content/mailWindowOverlay.js:159
oncommandupdate chrome://messenger/content/messenger.xul:1
file_init chrome://messenger/content/mailWindowOverlay.js:183
initAppMenuPopup chrome://messenger/content/mailWindowOverlay.js:3981
handleEvent chrome://messenger/content/customizableui/panelUI.js:343
_openPopupPromise resource:///modules/PanelMultiView.jsm:542
AsyncFunctionNext self-hosted:689
NS_ERROR_FILE_TARGET_DOES_NOT_EXIST: Component returned failure code: 0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST) [nsIMsgSendLater.hasUnsentMessages] mail3PaneWindowCommands.js:1343
IsSendUnsentMsgsEnabled chrome://messenger/content/mail3PaneWindowCommands.js:1343
isCommandEnabled chrome://messenger/content/mail3PaneWindowCommands.js:588
isCommandEnabled chrome://messenger/content/mailTabs.js:834
isCommandEnabled chrome://messenger/content/tabmail.js:535
goUpdateCommand chrome://global/content/globalOverlay.js:84
goUpdateMailMenuItems chrome://messenger/content/mailWindowOverlay.js:159
oncommandupdate chrome://messenger/content/messenger.xul:1
file_init chrome://messenger/content/mailWindowOverlay.js:183
initAppMenuPopup chrome://messenger/content/mailWindowOverlay.js:3981
handleEvent chrome://messenger/content/customizableui/panelUI.js:343
_openPopupPromise resource:///modules/PanelMultiView.jsm:542
AsyncFunctionNext self-hosted:689
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 1343" data: no] globalOverlay.js:89
goUpdateCommand chrome://global/content/globalOverlay.js:89
goUpdateMailMenuItems chrome://messenger/content/mailWindowOverlay.js:159
oncommandupdate chrome://messenger/content/messenger.xul:1
file_init chrome://messenger/content/mailWindowOverlay.js:183
initAppMenuPopup chrome://messenger/content/mailWindowOverlay.js:3981
handleEvent chrome://messenger/content/customizableui/panelUI.js:343
_openPopupPromise resource:///modules/PanelMultiView.jsm:542
AsyncFunctionNext self-hosted:689
NS_ERROR_FILE_TARGET_DOES_NOT_EXIST: Component returned failure code: 0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST) [nsIMsgSendLater.hasUnsentMessages] mail3PaneWindowCommands.js:1343
IsSendUnsentMsgsEnabled chrome://messenger/content/mail3PaneWindowCommands.js:1343
isCommandEnabled chrome://messenger/content/mail3PaneWindowCommands.js:588
isCommandEnabled chrome://messenger/content/mailTabs.js:834
isCommandEnabled chrome://messenger/content/tabmail.js:535
goUpdateCommand chrome://global/content/globalOverlay.js:84
goUpdateMailMenuItems chrome://messenger/content/mailWindowOverlay.js:159
oncommandupdate chrome://messenger/content/messenger.xul:1
file_init chrome://messenger/content/mailWindowOverlay.js:183
initAppMenuPopup chrome://messenger/content/mailWindowOverlay.js:3981
handleEvent chrome://messenger/content/customizableui/panelUI.js:343
_openPopupPromise resource:///modules/PanelMultiView.jsm:542
AsyncFunctionNext self-hosted:689
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 1343" data: no] globalOverlay.js:89
goUpdateCommand chrome://global/content/globalOverlay.js:89
goUpdateMailMenuItems chrome://messenger/content/mailWindowOverlay.js:159
oncommandupdate chrome://messenger/content/messenger.xul:1
file_init chrome://messenger/content/mailWindowOverlay.js:183
initAppMenuPopup chrome://messenger/content/mailWindowOverlay.js:3981
handleEvent chrome://messenger/content/customizableui/panelUI.js:343
_openPopupPromise resource:///modules/PanelMultiView.jsm:542
AsyncFunctionNext self-hosted:689

Comment 1

[Magnus Melin [:mkmelin] (away until Aug 10)]

I don't think that's related.
But anyway, new folders are checked at login (I think). There's no functionality for a server to notify Thunderbird about new folders. So nothing to do here.

Comment 2

[Richard Leger]

This bug is bot invalid and should be re-opened.

Creating a folder in Thunderbird in an IMAP mailbox shall make the folder visible in Thunderbird immediately... that has always been the case up to now... and I have observed in some unknown circumpstances that is no longer the case with recent beta's...

I start not to see the point of using beta and reporting bugs if they keep being considered invalid and not looked after by the dev team...