Closed Bug 1460000 Opened 7 years ago Closed 7 years ago

bookmarks and history error message

Categories

(Toolkit :: Places, defect)

59 Branch
x86_64
Windows 10
defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 1432583

People

(Reporter: pierre, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0 Build ID: 20180427210249 Steps to reproduce: Opened firefox browser from desktop (as usual) Actual results: Top of screen red banner stating that firefox could not use history and bookmarks because other process might be using it. Followed both instructions on repairing error. 1) Stopping firefox, log out, shutdown laptop, reboot, log in, start firefox => red banner 2) removal of the places.sqlite file. Still red banner 3) Do a cleaning of firefox => red banner 4) Using ccleaner to cleanup registry => starting firefox => red banner Expected results: Bookmarks and history accessible; no red banner.
Severity: normal → major
Has STR: --- → yes
Component: Untriaged → Bookmarks & History
OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64
Component: Bookmarks & History → Places
Product: Firefox → Toolkit
(In reply to pierre from comment #0) > Top of screen red banner stating that firefox could not use history and > bookmarks because other process might be using it. > Followed both instructions on repairing error. > 1) Stopping firefox, log out, shutdown laptop, reboot, log in, start > firefox => red banner > 2) removal of the places.sqlite file. Still red banner > 3) Do a cleaning of firefox => red banner > 4) Using ccleaner to cleanup registry => starting firefox => red banner Try removing favicons.sqlite
Flags: needinfo?(pierre)
Stopped Firefox. Renamed favicons.sqlite to favicons.sqlite.OLD. Restarted Firefox. Red banner gone, Bookmarks available again. I suggest you update knowledge article on this. (Not only remove places.sqlite but also favicons.sqlite). Thx!
Flags: needinfo?(pierre)
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.