Closed Bug 1523266 Opened 6 years ago Closed 6 years ago

Refresh Firefox - Keep old profile

Categories

(Firefox :: Migration, defect)

64 Branch
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: male.schmitt, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0

Steps to reproduce:

I opened a link from Telegram and Firefox crashed. I can open the link in Firefox directly without crashing, so i thing the bug is in Telegram or my system.

Actual results:

After some crashes Firefox asked me whether I would want to "Refresh Firefox" or "Start in Safe-Mode". Silly me just pressed "Refresh" and after confirming lost some of my profile. I now have to copy the profile of my other PC to avoid reconfiguring all of my plugins and UMatrix block lists.

Expected results:

I would have been nice to keep the old profile folder. Just make a new profile one import the data that is safe to import and make this the default profile without deleting my old profile. I thing there was nothing wrong with my old Profile because even on a new clean profile opening the link crashed Firefox.

Refreshing Firefox places your original profile folder in a folder called Old Firefox Data on the desktop. Did you not notice this, or did it really not happen in your case?

As for the crash, please

  1. Submit a crash report when the crash reporter window appears.
  2. Enter about:crashes into the address bar and copy the relevant crash report ID to the clipboard.
  3. File a new bug report and mention the crash report ID in the description.

Edit: Sorry, I just noticed you're on Linux. The crash reporter only works with Mozilla builds, so it won't show if you're using the Firefox version from your distro. See How to get a stacktrace for a bug report for alternatives.

Component: Untriaged → Migration
Flags: needinfo?(male.schmitt)

Thank you very much. I found the old profiles the directory you mentioned.
I will look into the crash report.

Flags: needinfo?(male.schmitt)
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.