Open Bug 1780265 Opened 7 months ago Updated 3 days ago

Console errors on new 102 install after just setting up a gmail IMAP account - Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsIRequest.name] OAuth2.jsm:171 onStateChange resource:///modules/OAuth2.jsm:171

Categories

(Thunderbird :: Account Manager, defect)

Thunderbird 102
defect

Tracking

(Not tracked)

People

(Reporter: thomas8, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

102.0.3 (64-bit), Win10

Console looks pretty red after just setting up a gmail IMAP account on a fresh 102 install. See attachment; the most relevant listed here:


NS_ERROR_NOT_IMPLEMENTED: Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsIRequest.name] OAuth2.jsm:171
onStateChange resource:///modules/OAuth2.jsm:171


Unknown Collection "thunderbird/password-recipes" RemoteSettingsClient.jsm:143
UnknownCollectionError resource://services-settings/RemoteSettingsClient.jsm:143
sync resource://services-settings/RemoteSettingsClient.jsm:502
InterpretGeneratorResume self-hosted:1422
AsyncFunctionNext self-hosted:632
(Async: async)
_importingPromise resource://services-settings/RemoteSettingsClient.jsm:365
InterpretGeneratorResume self-hosted:1422
AsyncFunctionNext self-hosted:632
(Async: async)
get resource://services-settings/RemoteSettingsClient.jsm:371
InterpretGeneratorResume self-hosted:1422
AsyncFunctionNext self-hosted:632
(Async: async)
reset resource://gre/modules/LoginRecipes.jsm:134
LoginRecipesParent resource://gre/modules/LoginRecipes.jsm:62
get recipeParentPromise resource://gre/modules/LoginManagerParent.jsm:1450
sendLoginDataToChild resource://gre/modules/LoginManagerParent.jsm:515
receiveMessage resource://gre/modules/LoginManagerParent.jsm:290


[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 882" data: no] msgMail3PaneWindow.js:882:20
loadPostAccountWizard chrome://messenger/content/msgMail3PaneWindow.js:882
AsyncFunctionNext self-hosted:632
(Async: async)
_onMessageReceived chrome://messenger/content/msgMail3PaneWindow.js:627


[HEAD, GET, PROPFIND, PUT errors related to accounts.google.com, see attachment]


about:addressbook : Unable to run script because scripts are blocked internally. 30 (existing bug)

Blocks: tb102found

All-red console after just setting up an IMAP gmail account

Blocks: 1780271

Like bug 1780271, this is pretty much expected. And IIRC you have filed a bug about those errors before ;)

(In reply to Magnus Melin [:mkmelin] from comment #2)

Like bug 1780271, this is pretty much expected. And IIRC you have filed a bug about those errors before ;)

Thanks. I think I saw different types of errors between Gmail and GMX, hence two bugs.
I find it weird that if as Ben B. says, some of these errors are actually expected as we check out server capabilities, why we would have to spam the error console with red errors for things that work correctly. Maybe a regular console.log could suffice for analysis purposes.

Would you say that NS_ERROR_NOT_IMPLEMENTED and Unknown Collection "thunderbird/password-recipes" are also an expected error? If yes, and if it's not harmful - why does it show in red? Imho we should stop cluttering the error console with red errors when things allegedly go right - not exactly helpful even for analysis, because the real errors get lost in the noise.

See Also: → 1723981, 1723973

NS_ERROR_NOT_IMPLEMENTED and Unknown Collection "thunderbird/password-recipes" - that's bugs, which we should fix. But AFAIK they are harmless: they could be problems in certain situations but not in the cases we hit.

Severity: -- → S4

(In reply to Magnus Melin [:mkmelin] from comment #4)

NS_ERROR_NOT_IMPLEMENTED and Unknown Collection "thunderbird/password-recipes" - that's bugs, which we should fix. But AFAIK they are harmless: they could be problems in certain situations but not in the cases we hit.

Are there way to shut them up in the contexts when they are harmless?
(I know it is a trade-off between such "shutting up and making the test log less cluttered for easier analysis" vs "the time to create such fine control of error messages".
I will vote for the former. The time spent by the current and future testers to cull through the log file is immense due to the clutter while the time to implement fine control may be time consuming but it is done once.

Any would-be new first time TB programming contributor would be shocked (I was) at the number of errors / warnings in the test log.

Summary: Console errors on new 102 install after just setting up a gmail IMAP account → Console errors on new 102 install after just setting up a gmail IMAP account - Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsIRequest.name] OAuth2.jsm:171 onStateChange resource:///modules/OAuth2.jsm:171

My macOS Thunderbird updated to 102.7.0 today and I get the same error while trying to get new oauth2 credentials (I was already using oauth2 with previous version) for Office 365 (enterprise tenant), so cannot authenticate. My error message:

NS_ERROR_NOT_IMPLEMENTED: Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsIRequest.name] 8 OAuth2.jsm:168
onStateChange resource:///modules/OAuth2.jsm:168

Details on build:

Version 102.7.0
Build ID 20230112161338
OS Darwin 21.6.0 Darwin Kernel Version 21.6.0: Sun Nov 6 23:31:16 PST 2022; root:xnu-8020.240.14~1/RELEASE_X86_64

However: I tried Thunderbird Beta and it does work. I did a new profile on one system, and imported my existing profile on another system, and both were able to authenticate and process messages. The beta version I used is:

Version 110.0b1
Build ID 20230117012511

And this is using IMAP and SMTP with Office 365.

(In reply to Phil Pishioneri from comment #7)

And this is using IMAP and SMTP with Office 365.

You will want to be aware of https://www.thunderbird.net/en-US/thunderbird/102.7.0/releasenotes/#known-issues

A fix should be available soon.

(In reply to Wayne Mery (:wsmwk) from comment #8)

You will want to be aware of https://www.thunderbird.net/en-US/thunderbird/102.7.0/releasenotes/#known-issues

I had done the "Opening the "About Mozilla Thunderbird" dialog will allow an update to 102.7.0." -- I'll have to correct myself of that habit. I'll downgrade to 102.6.1 and wait for it to suggest the upgrade.

You need to log in before you can comment on or make changes to this bug.