Closed Bug 609056 Opened 14 years ago Closed 10 years ago

ERROR addons.xpi: Error creating statement getAddonsInLocation

Categories

(Toolkit :: Add-ons Manager, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: ashah, Unassigned)

References

Details

Attachments

(1 file)

I just updated my minefield to yesterdays nightly and I am getting this on the error console.

Error: ERROR addons.xpi: Error creating statement getAddonsInLocation (SELECT internal_id, id, location, version, type, internalName, updateURL, updateKey, optionsURL, aboutURL, iconURL, icon64URL, defaultLocale, visible, active, userDisabled, appDisabled, pendingUninstall, descriptor, installDate, updateDate, applyBackgroundUpdates, bootstrap, skinnable, size, sourceURI, releaseNotesURI FROM addon WHERE location=:location)


Actual result: I cannot see anything being typed into the url bar. For eg. If I try typin google.com, I can see the results in the awesome bar but I cannot see anything being typed into URL bar. Also minefield does not refresh on any content. I have to take the focus away to another window and then get the focus back n minefield again to refresh content.
Could you attach a copy of extensions.sqlite from your profile folder and tell me what the value of extensions.databaseSchema is
Attached file extensions.sqlite file
The value of extensions.databaseSchema is 3
Have you recently used an older nightly (before September) or beta (b7 or earlier) with this profile? If so did you happen to crash when you first ran that older build?
No. I have been using this profile specifically for minefield. I just update my minefield when I start it (I dont update it everyday though). My update before this was 3 days ago and that worked fine.
Have you installed or uninstalled any extensions recently or even opened the add-ons manager?
yes. I did open the addons manager to see which extensions are installed currently. I didnt install anything though
extensions.sqlite has been replaced by extensions.json in bug 853388, so this problem can no longer occur.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: