Closed
Bug 1401371
Opened 7 years ago
Closed 7 years ago
AddonManager doesn't start if Firefox is launched directly from a disk image
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1339100
Tracking | Status | |
---|---|---|
firefox57 | --- | fix-optional |
People
(Reporter: mkaply, Unassigned)
Details
If you launch Firefox directly from a disk image, the AddonManager doesn't startup correctly: 1505858874807 addons.manager ERROR startup failed: [Exception... "Component returned failure code: 0x80520013 (NS_ERROR_FILE_READ_ONLY) [nsIFile.create]" nsresult: "0x80520013 (NS_ERROR_FILE_READ_ONLY)" location: "JS frame :: resource://gre/modules/FileUtils.jsm :: FileUtils_getDir :: line 70" data: no] Stack trace: FileUtils_getDir()@resource://gre/modules/FileUtils.jsm:70 < FileUtils_getFile()@resource://gre/modules/FileUtils.jsm:42 < validateBlocklist()@resource://gre/modules/AddonManager.jsm:656 < startup()@resource://gre/modules/AddonManager.jsm:816 < startup()@resource://gre/modules/AddonManager.jsm:3122 < observe()@jar:file:///var/folders/rc/qcgp5b4s6nxf1s0rd1pp6gqr0000gn/T/AppTranslocation/5914512C-3577-410E-B60C-BA656CFB5A5F/d/Firefox.app/Contents/Resources/omni.ja!/components/addonManager.js:65 And things are pretty broken from then on. Even after restart, things don't work correctly (random errors in extensions). This definitely used to work (we use it to test distributions)
Updated•7 years ago
|
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•