Open Bug 1723973 Opened 3 years ago Updated 2 years ago

Console error NS_ERROR_FILE_NOT_FOUND etc. on virgin install after closing Account Setup tab for the first time (without creating an account)

Categories

(Thunderbird :: Account Manager, defect)

Unspecified
Windows
defect

Tracking

(Not tracked)

People

(Reporter: thomas8, Unassigned)

References

(Blocks 1 open bug)

Details

+++ This bug was initially created as a clone of Bug #1665421 +++

STR

  1. install 91.0b6 (32-bit) (seen on Win10)
    --> Account Setup tab appears.
  2. Switch to Home tab (Account Central, no folder list)
  3. open Error console (Ctrl+Shift+J)
  4. close Account Setup tab

Note: For each new install, this reproduces only for the very first time of closing the Account Tab without accounts. Subsequent attempts will no longer create the error. To reproduce again, you need to reinstall.

I have seen this on the 2nd or nth installed instance of beta channel in a new folder, but I don't think that matters.

Actual result

  • Console error NS_ERROR_FILE_NOT_FOUND involving loadPostAccountWizard (see below)
  • Seems to check for ical calendars (but we don't have anything to check for because no account data have been entered)
  • NS_ERROR_NOT_AVAILABLE (without further info)

Expected result

  • no console errors
[Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIMsgAccountManager.loadVirtualFolders]"  nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)"  location: "JS frame :: chrome://messenger/content/msgMail3PaneWindow.js :: loadPostAccountWizard :: line 914"  data: no] msgMail3PaneWindow.js:914:20
    loadPostAccountWizard chrome://messenger/content/msgMail3PaneWindow.js:914
    AsyncFunctionNext self-hosted:692
    (Async: async)
    _onMessageReceived chrome://messenger/content/msgMail3PaneWindow.js:719
mPlatform is: winnt calendar-migration.js:60:13
Checking for ical data calendar-migration.js:165:13
NS_ERROR_NOT_AVAILABLE
Blocks: 1723981
You need to log in before you can comment on or make changes to this bug.