Closed Bug 285868 Opened 20 years ago Closed 20 years ago

Lost half of bookmarks on upgrade

Categories

(Firefox :: Bookmarks & History, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 284099

People

(Reporter: ffav, Assigned: p_ch)

Details

(Keywords: dataloss)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1 I upgraded to Firefix 1.0.1 and lost half of my bookmarks. The first 1/2 of the alphabetical list (through L) are still there, but lost everything after that. Reproducible: Always Steps to Reproduce: 1.Open Bookmarks 2. 3. Actual Results: My bookmarks are there until I scroll down to the "L's". The last entry to show is the "Legal" folder. That is the end. Expected Results: It should scroll down all the way through the alphabetical list of what used to be my bookmarks, including everything starting with a letter that comes after "L" in the alphabet. I think I've pretty well covered it.
Product: Mozilla Application Suite → Firefox
I have a very similar problem with upgrade 1.0.2 I diligently bookmarked all of the windows I had constructed as tabs, then closed out of Firefox altogether. After reboot, everything I had saved to bookmarks in the last day was gone.
when i started to download some stuff with bitcomet the comp froze and after reboot i hade lost every bookmark before 2004-08-13... and thats alot of use full bookmarks T_T.... i even tryed to search with "Magic Recovery Professional" but couldent finde them x_x
lose bookmarks on second load of 1.02 after upgrading from 1.0 I have even ran a system restore and same result.
I am unable to reproduce this under WindowsXP Service Pack 1 or Windows 2000 Service Pack 4. I recently updated them to 1.0.2 using the software update, and had no issues. Reporter: Can you please clarify the steps to reproduce? Was there anything in specific you did before, during, or after the update that could cause a different result than what I am experiencing?
Keywords: dataloss
Summary: Lost bookmarks on upgrade → Lost half of bookmarks on upgrade
I had an automatic upgrade, I >think< (since it's automatic, I haven't paid much attention to it), VERY RECENTLY to 1.0.3. Some short time after, having not opened FF for some hours, I clicked and it asked for a new profile or something, and I tried not to set up a new one, but was unsuccessful and when it finally opened the screen my very carefully saved bookmarks were reset to zero! I have lost a ton of work and time put in to these bookmarks, for a specific job. I am so ****! I have NEVER lost my favorites. Favorites are easy to find. Favorites are easy to copy. Favorites are easy to import. I am feeling totally insecure about FF at this point! Marking your browsing is the biggest issue about browsing! It sucks!
(In reply to comment #5) > I had an automatic upgrade, I >think< (since it's automatic, I haven't paid much > attention to it), VERY RECENTLY to 1.0.3. Some short time after, having not > opened FF for some hours, I clicked and it asked for a new profile or something, > and I tried not to set up a new one, but was unsuccessful and when it finally > opened the screen my very carefully saved bookmarks were reset to zero! > > I have lost a ton of work and time put in to these bookmarks, for a specific > job. I am so pissed! I have NEVER lost my favorites. Favorites are easy to find. > Favorites are easy to copy. Favorites are easy to import. I am feeling totally > insecure about FF at this point! Marking your browsing is the biggest issue > about browsing! > > It sucks! That seems to be the 'profile corruption' bug, and is unrelated to this one. There are instructions in several places online on how to fix it. It should be fixed in the next version (1.1) and is a known bug.
*** This bug has been marked as a duplicate of 284099 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.