Closed
Bug 1376870
Opened 7 years ago
Closed 7 years ago
In 56 Nightly Awesome bar history are not populating
Categories
(Toolkit :: Places, defect)
Toolkit
Places
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: carnold, Unassigned)
Details
Attachments
(2 files)
History suggestions which tend to show up in release channel versions of Firefox are not showing up in current trunk release (56.0a1).
Reporter | ||
Comment 1•7 years ago
|
||
It appears that the reason the search suggestions aren't coming up is that my history is actually inaccessible to Nightly. Here is a screenshot that shows my history file appearing empty in 56.0a1, even though I have a 5+ year old profile.
Reporter | ||
Comment 2•7 years ago
|
||
Comment 3•7 years ago
|
||
You seem to have a corruption problem in places.sqlite or in general in your profile. Mind to check if any add-on is involved by disabling all of them? I'd also suggest trying with Places Maintenance https://addons.mozilla.org/en-US/firefox/addon/places-maintenance/, after a profile backup, just in case.
Updated•7 years ago
|
Component: Search → Places
Product: Firefox → Toolkit
Reporter | ||
Comment 4•7 years ago
|
||
Thank you Marco. Bug still happens when all addons are disabled. Places Maintenance did find some issues and repaired them. However the bug persists when I run Nightly. It works fine in 54.
Comment 5•7 years ago
|
||
Maybe this could help: https://developer.mozilla.org/en-US/docs/Mozilla/Tech/Places/places.sqlite_Database_Troubleshooting#How_to_(try_to)_recover_from_a_corrupt_places.sqlite it contains some manual steps to do something similar to Places Maintenance, but in a manual way, so one may check where the process fails. I assume you used this same profile across different versions? There's a possible backwards incompatibility between 54 and 55 (documented in 55 release notes). In particular, a database created in V55, cannot be downgraded to 54. But this doesn't seem the case, since your bug happens in 56.
Reporter | ||
Comment 6•7 years ago
|
||
Thanks Marco. As this bug seems to be unique to my legacy-profile. I think I should close it out. I did use this profile across multiple versions. It happens to be a 5+ year old profile.
Reporter | ||
Comment 7•7 years ago
|
||
Can't replicate bug with a new profile.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Resolution: FIXED → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•