When we find that extensions.sqlite is corrupt, we rebuild the data by detecting addons on disk - which makes them look like foreign installs, so we open up about:newaddon. We should be doing some heuristics to figure out whats a new install and what isn't. We can detect if an addon was already enabled (and therefore installed) before the DB corruption by looking at extensions.ini and extensions.bootstrappedAddons. I thought we were doing this already - maybe a regression?
I think my patch in bug 671894 takes care of this, I have just failed to find time to finish the last bits of it :(
Indeed, handled by bug 671894 - that's where I remembered it from!
Assignee: nobody → bmcbride
Status: NEW → ASSIGNED
Depends on: 671894
Fixed via bug 671894.
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.