Closed Bug 623672 Opened 14 years ago Closed 14 years ago

Bookmarks toolbar missing on launch

Categories

(Firefox :: Bookmarks & History, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 620723

People

(Reporter: jrmuizel, Unassigned)

Details

I lost my bookmarks toolbar one time, lots of other places related stuff didn't work. I got the following error in the error console.

Error: aUrlString is null 
Source File: resource:///modules/PlacesUIUtils.jsm
Line: 938

After, restarting the problem was fixed.
It looks like I also lost all of my history after this.
(In reply to comment #1)
> It looks like I also lost all of my history after this.
Do you have a places.sqlite.corrupt file in your profile folder?
(In reply to comment #2)
> (In reply to comment #1)
> > It looks like I also lost all of my history after this.
> Do you have a places.sqlite.corrupt file in your profile folder?

I do.
(In reply to comment #3)
> I do.
Well, that'd be why you lost your history.  As to why it got marked corrupt...

Have you been using older builds by chance?
I took a look at some more stuff:
 - my places.sqlite got shrunk down to 10MB (I can send it if needed)
 - keywords were broken
 - history recording worked, but awesome bar results would get page titles from my bookmarks instead of the history
 - I have a places.sqlite.corrupt file

I may have run an older debug build inbetween restarting my nightly of firefox.
Also, I was able to fix all of the problems by restoring my old places.sqlite from backup.
(In reply to comment #5)
> I may have run an older debug build inbetween restarting my nightly of firefox.
Do you have a date from that older build?  There was a time on trunk where we had some broken code that could not deal with some newer stuff.  Anything pre beta 8 is bad.
The build is from 20101013150517
http://hg.mozilla.org/mozilla-central/rev/0ddf0b396d15

I tried running the build again, and it again broke my places file.
Current trunk or beta profiles cannot downgrade to nightlies or betas released before 10 December, and this seems to be the case.
Btw, it's common suggestion to never use the same profile across different versions (unless it's a classic upgrade to a newer version)
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.