Closed Bug 260243 Opened 21 years ago Closed 21 years ago

bookmarks deleted after a bad shutdown

Categories

(Firefox :: Bookmarks & History, defect)

1.0 Branch
x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 193749

People

(Reporter: mega2, Unassigned)

References

Details

(Keywords: dataloss)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10 after a power failure my bookmarks were deleted, and my toolbar customization was set back Reproducible: Couldn't Reproduce Steps to Reproduce: i do not know, if it happens every time, but 2. start firefox 1 pr 3. and then shutdown the power
Look for C:\Documents and Settings\USERNAME\Application Data\Mozilla\Firefox\Profiles\..\bookmarks.html and delete it. than rename the file bookmarks.bak -> bookmarks.html
You shouldn't have to copy that stuff over manually; if you can reproduce this, can you check the size of the bookmarks.html in your profile? Is it 0, or greater than 0? Also check the size of bookmarks.bak. Firefox should use bookmarks.bak if boomarks.html doesn't exist or its size is 0.
Keywords: dataloss
It happened several times to me too, basically each time Firefox crashes seriously (which occurs rather seldom). I remember to have checked that boomarks.html was existing and of nonzero size (size was indicated as 1Kb), but it was empty.
Summary: after a power failure my bookmarks were deleted → bookmarks deleted after a bad shutdown
*** Bug 265700 has been marked as a duplicate of this bug. ***
Assignee: vladimir → vladimir+bm
*** This bug has been marked as a duplicate of 193749 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Version: unspecified → 1.0 Branch
Assignee: vladimir+bm → nobody
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → bookmarks
You need to log in before you can comment on or make changes to this bug.