Bookmarks, Extensions, everything lost after Firefox upgraded to 68.3.0esr (64-Bit) without notice
Categories
(Firefox :: Untriaged, defect)
Tracking
()
People
(Reporter: stephan_thomann, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
Start Firefox, it was updated and I was not aware of it. It warned that I have to create a new profile if I did not want to loose bookmarks, I clicked "create new profile", but I cannot go back or find the old bookmarks anymore. Directories have been cleaned of everything, so nothing can be imported or recovered.
Actual results:
Everything was cleaned instead of just creating a new profile
Expected results:
Keep bookmarks (add-ons: may be ok if they are deleted but please warn before removing anything)
|
||
Comment 1•5 years ago
|
||
Stephan,
Sorry that this happened to you. By any chance, do you remember from what Firefox version was the update made from?
Can you please open the About Profiles page to see if your old profile is still there (type about:profiles into the address bar and press the Enter key)? You can find more details about how to do this, here: https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles
If you find your old profile, you can still open it by overwriting the downgrade protection. You can find more details about what the downgrade protection is and what are the steps you need to follow to open your old profile, here:
https://support.mozilla.org/en-US/kb/dedicated-profiles-firefox-installation#w_what-are-my-options
|
Reporter | |
Comment 2•5 years ago
|
||
Sorry about the late reply. I do not know the exact version but it was 67.x
I imported bookmarks from another machine. Most of the bookmarks there where the same due to an earlier import on that one. I installed the add-ons, so there is not big damage. In the meantime I got another update with another problem, but this time it kept the bookmarks and the extensions. Will be a problem for you to keep up and I suspect that the upgrade to 68 was a smooth one for most users.
|
|
||
Comment 3•5 years ago
|
||
Stephan, please file a new bug report for the problem you mentioned in the previous comment. As for this report, considering that you did not reproduce it after the update, I'm going to mark it as Resolved Worksforme. Please, feel free to reopen it if the issue is back and reproducible.
Description
•