Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

History isn't active, even though preferences are set to remember history (firefox 61.0.1; MacOS 10.12.6)

  • 4 replies
  • 1 has this problem
  • 12 views
  • Last reply by shifra

more options

Since I've updated to 61, I can't get the history to be active. (Bookmarks are fine). I made sure the settings were correct, I ran Refresh firefox; I ran Verify integrity and got this:

Task: checkIntegrity

- Unable to check database integrity > Task: invalidateCaches - The task queue was cleared by an error in another task. > Task: checkCoherence - The task queue was cleared by an error in another task. > Task: expire - The task queue was cleared by an error in another task. > Task: vacuum - The task queue was cleared by an error in another task. > Task: stats - The task queue was cleared by an error in another task. > Task: _refreshUI - The task queue was cleared by an error in another task.

I've looked up numerous help sites, and they all refer to a place.sqlite file that I don't seem to have, and a profile folder that also does not exits (I'm assuming this is a 61 thing, in my older versions I had those files and folders.

Help! I need my history!

Thanks.

Since I've updated to 61, I can't get the history to be active. (Bookmarks are fine). I made sure the settings were correct, I ran Refresh firefox; I ran Verify integrity and got this: Task: checkIntegrity - Unable to check database integrity > Task: invalidateCaches - The task queue was cleared by an error in another task. > Task: checkCoherence - The task queue was cleared by an error in another task. > Task: expire - The task queue was cleared by an error in another task. > Task: vacuum - The task queue was cleared by an error in another task. > Task: stats - The task queue was cleared by an error in another task. > Task: _refreshUI - The task queue was cleared by an error in another task. I've looked up numerous help sites, and they all refer to a place.sqlite file that I don't seem to have, and a profile folder that also does not exits (I'm assuming this is a 61 thing, in my older versions I had those files and folders. Help! I need my history! Thanks.

Chosen solution

HI, please make a new Profile : Make a new one and test ...:

If is your Profile :

If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over the problem. Never work with original files.

  • bookmarks and history: places.sqlite
  • bookmark backups: compressed .jsonlz4 JSON backups in the bookmarkbackups folder
  • cookies.sqlite for the Cookies
  • formhistory.sqlite for saved autocomplete Form Data
  • logins.json (passwords) and key4.db (58+) or key3.db (57 and older) (decryption key) for Passwords saved in the Password Manager
  • if you only have key3.db then make sure to remove an existing key4.db
  • cert9.db (58+) or cert8.db (57 and older) for (intermediate) certificates stored in the Certificate Manager
  • if you only have cert8.db then make sure to remove an existing cert9.db
  • persdict.dat for words you added to the spelling checker dictionary
  • permissions.sqlite for Permissions and possibly content-prefs.sqlite for other website specific data (Site Preferences)
  • sessionstore.jsonlz4 for open tabs and pinned tabs (see also the sessionstore-backups folder)

Please let us know if this solved your issue or if need further assistance.

Read this answer in context 👍 0

All Replies (4)

more options

Chosen Solution

HI, please make a new Profile : Make a new one and test ...:

If is your Profile :

If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over the problem. Never work with original files.

  • bookmarks and history: places.sqlite
  • bookmark backups: compressed .jsonlz4 JSON backups in the bookmarkbackups folder
  • cookies.sqlite for the Cookies
  • formhistory.sqlite for saved autocomplete Form Data
  • logins.json (passwords) and key4.db (58+) or key3.db (57 and older) (decryption key) for Passwords saved in the Password Manager
  • if you only have key3.db then make sure to remove an existing key4.db
  • cert9.db (58+) or cert8.db (57 and older) for (intermediate) certificates stored in the Certificate Manager
  • if you only have cert8.db then make sure to remove an existing cert9.db
  • persdict.dat for words you added to the spelling checker dictionary
  • permissions.sqlite for Permissions and possibly content-prefs.sqlite for other website specific data (Site Preferences)
  • sessionstore.jsonlz4 for open tabs and pinned tabs (see also the sessionstore-backups folder)

Please let us know if this solved your issue or if need further assistance.

more options

Made a new profile, and it fixed the problem, I decided not to transfer the old places.sqlite (there were some other strange things too), just the bookmarks and now it works well.

I think I also figured out why I couldn't find the profiles folder before - I went to the Library folder under / not under my user (I work with Unix regularly)

Thank you!

more options

Note that you could have tried to delete places.sqlite in your original profile to recover from this issue.

If "Verify Integrity" on the "Help -> Troubleshooting Information" (about:support) page cannot repair places.sqlite then remove all places.sqlite files in the Firefox profile folder. Firefox will rebuild places.sqlite and restore the bookmarks from a recent JSON backup in the bookmarkbackups folder.

more options

Thanks for the tip, as I wrote above, I originally didn't find the places.sqlite (it turns out I was looking in Library under / instead of under my user). When I used the mac find - it didn't find the file either (just a very old backup from a previous system) so I though it was something that had changed in the newer browsers.

I didn't realize how much I could do with the (about:support).