Bugzilla

(In reply to Daniel Holbert [:dholbert] from comment #9)
> (In reply to Bogdan Maris, Desktop QA from comment #0)
> > **Steps to reproduce**
> > 1. Start Firefox 124.0 beta with a new profile and change the value of a pref (browser.search.region for example from RO to US for me)
> > 2. Close the browser
> > 3. Open Firefox 123.0 RC with the same profile created when starting 124
> 
> Do we know if this affects newer browser versions as well, or does the 'older version' here have to be 123-or-older?
> 
> If this is specific to older-versions 123-or-lower, then this might become less relevant as those versions get further out of support range and less-conceivably-things-that-users-might-run.
> 
> (Having said that: version 115esr is still supported of course; so if this affects current-version-to-115esr downgrades, then that's an important data point.)

What I meant by older is that you need to use a 2 Firefox builds one that is older than the other, or different versions, lets say Nightly 128 and Beta 127. Create a profile on Nightly 128 and than use the same profile on Beta 127.

For example I just reproduced using todays Nightly 128.0a1 and an older Nightly 127.0a1 so that the prompt saying "You've launched an older version of Firefox" will appear. In this case the prompt will NOT appear and so the process is stuck at 100%. 

I tried using the latest ESR 115.11 and an older one 115.0 but the prompt is not triggered since they have the same version. I did used an older ESR 102.15 but the prompt will pe prompted and so the process is not stuck so this issue is not reproducible on ESR.

The workaround is to use the --allow-downgrade variable when starting the "older" Firefox (Nightly 127.0a1 in the above case) with the profile created with the "newer" Firefox (Nightly 128.0a1 in the above case).

Let me know if more clarification is needed, or more testing, happy to help

(In reply to Daniel Holbert [:dholbert] from comment #9)
> (In reply to Bogdan Maris, Desktop QA from comment #0)
> > **Steps to reproduce**
> > 1. Start Firefox 124.0 beta with a new profile and change the value of a pref (browser.search.region for example from RO to US for me)
> > 2. Close the browser
> > 3. Open Firefox 123.0 RC with the same profile created when starting 124
> 
> Do we know if this affects newer browser versions as well, or does the 'older version' here have to be 123-or-older?
> 
> If this is specific to older-versions 123-or-lower, then this might become less relevant as those versions get further out of support range and less-conceivably-things-that-users-might-run.
> 
> (Having said that: version 115esr is still supported of course; so if this affects current-version-to-115esr downgrades, then that's an important data point.)

What I meant by older is that you need to use 2 Firefox builds, one that is older than the other, or different versions, lets say Nightly 128 and Beta 127. Create a profile on Nightly 128 and use the same profile on Beta 127.

For example I just reproduced using todays Nightly 128.0a1 and an older Nightly 127.0a1 so that the prompt saying "You've launched an older version of Firefox" will appear. In this case the prompt will NOT appear and so the process is stuck at 100%. 

I tried using the latest ESR 115.11 and an older one 115.0 but the prompt is not triggered since they have the same version. I did used an older ESR 102.15 but the prompt will pe prompted and so the process is not stuck so this issue is not reproducible on ESR.

The workaround is to use the --allow-downgrade variable when starting the "older" Firefox (Nightly 127.0a1 in the above case) with the profile created with the "newer" Firefox (Nightly 128.0a1 in the above case).

Let me know if more clarification is needed, or more testing, happy to help.