Closed Bug 1707478 Opened 4 years ago Closed 4 years ago

The new nightly didn't install using a new profile as it should

Categories

(Firefox :: Foxfooding, defect, P3)

Product:
Firefox
Component:
Foxfooding
Version:
Firefox 90
Platform:
Desktop
Windows 7
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox90 --- affected

People

(Reporter: gaby2300, Unassigned)

References

Details

(Whiteboard: [foxfooding][community] [proton-foxfooding])

Windows 7, 64-bit

Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:90.0) Gecko/20100101 Firefox/90.0 Windows_NT 6.1 7601

Build 20210424155423

  1. Download from https://www.mozilla.org/firefox/channel/desktop/#nightly and install.
  2. Notice it opens in the same profile as my daily one.

Expected behavior: As per https://blog.nightly.mozilla.org/2019/01/14/moving-to-a-profile-per-install-architecture/ it should install using a new profile.

Actual behavior: It installed using the same profile as my daily one.

Note: I tried two times, one with my daily browser open, the other with my daily browser closed. Both times the new installation didn't open in a new profile.

Github profile: https://github.com/gaby2300

Whiteboard: [foxfooding][community] [proton-foxfooding]

Julien, I cannot access your link. Could you please tell me what it is about? Or please give me access if possible?

Hi Gabriela, we are using JIRA to track proton progress, this is an internal tool only accessible to Mozilla employee, you can safely disregard this link. Thanks.

Thank you Julien , I understand!
BTW, do you happen to know someone who could help me fix this bug? Thanks for your help!

Priority: -- → P1

We are triaging Proton bugs daily - our product team will be assigning priorities, and engineering will engage in order of priority. Stay tuned.

I'm resetting the priority to unset until product has the chance to look at it.

Priority: P1 → --

(In reply to Julien Chaupitre from comment #5)

We are triaging Proton bugs daily - our product team will be assigning priorities, and engineering will engage in order of priority. Stay tuned.

I'm resetting the priority to unset until product has the chance to look at it.

Right, I understand. I'll be looking forward to that! Thanks!

Can you please help clarify the channel and version of your daily Firefox installation?

Flags: needinfo?(gmontagu)
Priority: -- → P3

(In reply to Romain Testard [:RT] from comment #7)

Can you please help clarify the channel and version of your daily Firefox installation?

Sure Romain!

Nightly, 90.0a1 (2021-04-27)

Thanks for your help!

Flags: needinfo?(gmontagu)

So I think your scenario is a re-installation (similar channel, similar folder path) rather than a sepoarate installation. In this case the default profile gets picked. Thanks for validating that these are indeed the same browser instance but different Windows.

(In reply to Romain Testard [:RT] from comment #9)

So I think your scenario is a re-installation (similar channel, similar folder path) rather than a sepoarate installation. In this case the default profile gets picked. Thanks for validating that these are indeed the same browser instance but different Windows.

I am sorry but I am not sure I understand your comment.

I still don't understand why the new Nightly didn't open in a new profile as it should have.

I am sorry but If other people not so interested in QA (or Foxfooding as it's called now) as I am, found this bug and didn't know testing with an old profile was almost useless, their effort was not worthwhile. Also, if they did know, they may have left testing which is a pity.

QA is super important for us and help is much appreciated!
My assumption is that your scenario is:
1 You run Nightly (installation 1) on your default profile (profile 1)
2 You install a frsh new nightly, you follow the default installation process which installs over your old installation, which therefore remains installation 1
3 AT this point installation 1 picks profile 1

If you install a different channel or to a different folder then installation 2 will get created, your system will have 2 different installations and starting up installation 2 will create a new profile

Hope this makes sense

(In reply to Romain Testard [:RT] from comment #11)

QA is super important for us and help is much appreciated!
My assumption is that your scenario is:
1 You run Nightly (installation 1) on your default profile (profile 1)
2 You install a frsh new nightly, you follow the default installation process which installs over your old installation, which therefore remains installation 1
3 AT this point installation 1 picks profile 1

I suppose this is because I ran the stub installation that didn't let me choose the folder I want to installed it in?

If you install a different channel or to a different folder then installation 2 will get created, your system will have 2 different installations and starting up installation 2 will create a new profile

Hope this makes sense

Yes, it does! Thanks!

Maybe the testing steps could include some detail about this, or change the stub installer for the normal one telling people to install in another folder? This may help testers to have the same issue as I did?

Yes the stub installer will default to default installation settings, the full installer on https://www.mozilla.org/en-US/firefox/all/#product-desktop-nightly have more customization capabilities.
Proton did not touch profile maangement or installation process so perhaps best to use the stub installer so testers set-up are standard.
I'll close this bug for now given I think we align.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME

(In reply to Romain Testard [:RT] from comment #13)

Yes the stub installer will default to default installation settings, the full installer on https://www.mozilla.org/en-US/firefox/all/#product-desktop-nightly have more customization capabilities.
Proton did not touch profile management or installation process so perhaps best to use the stub installer so testers set-up are standard.
I'll close this bug for now given I think we align.

You say you close the bug because we align. We align because I understood what happened. But this won't keep testers having the same issue and leaving. I mean, the bug isn't fixed. I still think testers should know this before starting so they can avoid reproducing the bug.

I am sorry but I think this shouldn't be resolved as WFM because it doesn't actually work for me.

(In reply to Gabriela [:gaby2300] from comment #14)

(In reply to Romain Testard [:RT] from comment #13)

Yes the stub installer will default to default installation settings, the full installer on https://www.mozilla.org/en-US/firefox/all/#product-desktop-nightly have more customization capabilities.
Proton did not touch profile management or installation process so perhaps best to use the stub installer so testers set-up are standard.
I'll close this bug for now given I think we align.

You say you close the bug because we align. We align because I understood what happened. But this won't keep testers having the same issue and leaving. I mean, the bug isn't fixed. I still think testers should know this before starting so they can avoid reproducing the bug.

@gaby2300 as mentioned, the bug is not with Proton, it's with the instructions to the testers that they need to have a fresh profile. I will change the instructions on the community portal to make this clearer.

Thanks for the help @RT

You need to log in before you can comment on or make changes to this bug.