New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

56.0.x refreshment of a non-default profile used data from the wrong profile (from the default profile) #386

grahamperrin opened this Issue Jan 16, 2018 · 4 comments


2 participants

grahamperrin commented Jan 16, 2018

Yesterday whilst running Waterfox 56.0.2_1 or 56.0.3 (I'm not sure which, probably the latter) with a profile root /home/grahamperrin/.mozilla/firefox/tuk42vu2.minimal everyday-1508231281798 (not the default profile) I opted to refresh the profile.


Refreshment based on the only profile that was in use when the refresh began.

Actual result

Refreshment based on a different profile, the default profile.



$ uname -v
FreeBSD 12.0-CURRENT #0 r320869: Mon Jul 10 13:57:55 UTC 2017 


  • quit Waterfox
  • remove the unwanted data
  • put back in place the old data (from the desktop).

This comment has been minimized.


MrAlex94 commented Jan 17, 2018

There was a bug discussing this. Only the default profile gets set, as you can see discussed in this bug. Usually the button is hidden, but Waterfox exposes it otherwise it never appears.

I will try patch this bug for Mozilla as well when I re-do the migration code, as this is where the code for this feature lies.


This comment has been minimized.


grahamperrin commented Jan 17, 2018


(Previously, I wondered whether the ~/.mozilla/firefox/ origin of the profile was a factor.)

For me: not a priority.

(If I need to refresh a non-default profile, I guess that I can work around the bug by temporarily making the profile the default.)


This comment has been minimized.


grahamperrin commented Feb 18, 2018


This comment has been minimized.


grahamperrin commented May 15, 2018

Probably fixed. If not, we can open another issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment