Closed Bug 260163 Opened 21 years ago Closed 21 years ago

When browser is closed and reopened all bookmarks are gone. bookmarks not saving.

Categories

(Firefox :: Bookmarks & History, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 260553

People

(Reporter: Timekeeper80, Assigned: vlad)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; rv:1.7.3) Gecko/20040913 Firefox/0.10 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; rv:1.7.3) Gecko/20040913 Firefox/0.10 When I chose the option "Bookmark this page" the webpage in question is bookmarked, but only as long as the browser is open. When the browser is closed and then reopened, all existing bookmarks are gone. This happens for all webpages, not just a specific one. Reproducible: Always Steps to Reproduce: 1. Save bookmark. 2. Close browser. 3. Reopen browser. 4. Bookmark is gone. Actual Results: The bookmarks are all gone. They do not save. Expected Results: I should have seen the bookmarks I had saved in the previous session. Instead, there was nothing there.
Can confirm using FF 1.0 PR on Linux. Bugs 260553 and 260591 may be dupes of this one! Severe data loss!
Flags: blocking-aviary1.0?
Original Poster: Do you know if your bookmarks.html file exists in your profile? If it does not, I would guess that this is a result of bug 260591, where Firefox fails to create bookmarks.html when it does not exist. If it *does* exist, is it set to be read-only? That would be bug 109377. And it could be caused by bug 260163.
I can't confirm this one. If the bookmarks.html file exists, bookmarks are saved as expected. but marking this a dupe of 260553. it's the same bug. *** This bug has been marked as a duplicate of 260553 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Flags: blocking-aviary1.0?
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.