Closed Bug 292477 Opened 20 years ago Closed 20 years ago

Bookmarks gone- opened FF and found bookmark folder and all add-ons gone

Categories

(Firefox :: Bookmarks & History, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: peter.letson, Unassigned)

Details

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705)
Build Identifier: 

Using FF 1.0.3, opened and found add-ons gone and bookmarks empty. Program 
acted as if it was a new install, although 1.0.3 had been in use for approx 
three weeks. Cannot duplicate problem. FF accepts new bookmarks and has not 
deleted them. I use Webroot spysweeper, Ad-aware 6.0, and symantec anti-virus, 
ran all three immediately and found no problems at all.

Reproducible: Couldn't Reproduce
Please read http://kb.mozillazine.org/Profile_Manager and start your firefox
with the ProfileManager - your old profile (with all your bookmarks, etc) should
be present, and you should be able to run with it.
wfm then, since can't dupe (don't know if real profile loss or just new profile
by accident).
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME

To be honest the link in comment 1 doesn't really help. I lost my bookmarks after a update earlier today and all my bookmarks are gone. Since I am not an IT specialist it would be noce to have a step by step guide of how to ressolve my bookmarks (if they are really still there) and not a reference to a lot of text I can't figure out

(In reply to Eric from comment #3)

To be honest the link in comment 1 doesn't really help. I lost my bookmarks after a update earlier today and all my bookmarks are gone. Since I am not an IT specialist it would be noce to have a step by step guide of how to ressolve my bookmarks (if they are really still there) and not a reference to a lot of text I can't figure out

This is an old bug that was closed many years ago. Please ask for support on our support site - https://support.mozilla.org/

You need to log in before you can comment on or make changes to this bug.