Since bug 1389160 landed, this warning is logged on startup of a new profile (or if the startup data is missing for any reason): Error parsing extensions state: [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [amIAddonManagerStartup.readStartupData]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" This isn't really helpful, and causes confusion when people are trying to identify real errors in automation (bug 1330227 comment 24 for example)
This is accidentally fixed by the last patch in bug 1363482, which made similar changes to bug 1389160, but handled the FILE_NOT_FOUND error correctly in the process.
Status: NEW → RESOLVED
Last Resolved: 10 months ago
Depends on: 1363482
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.