I don't have the exact error message at hand (sorry), but here are some steps to reproduce (from memory): * Install an addon * Use something like MozillaBuild to enter the extension's directory and therefore lock it from being deleted * Upgrade the addon by installing a new version Results: * The addon is installed twice, one being in a "to-be upgraded after restart" and the other being enabled but not functioning. * Some error message about not being able to delete a file, or move it from extensions.stage to extensions or similar. While the STR may seem uncommon, I've had reports from some users that this has been happening with Lightning. I don't know how they locked their extension directory, but they at least had the same final result as I had using the above steps by coincidence. Expected would be that the addons manager can recover from this state and tries to remove the locked directory later on,
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Last Resolved: a month ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.