Another update 135.0.1 FAILS!

[RexMortis]

Once again Mozilla updates and websites start racking up ERROR 500's

If you cant get straight STOP making updates!

[siffemcon]

Can you provide some examples where that happens?

[bsfinkel]

I am running 135.0 (64-bit)  I got a notice this morning that an update was available, so I  downloaded it.  It was not until a few minutes ago that I had time to install it.  The Help --> About Firefox pop-up windows tells me to "Restart to Update Firefox".  I have done this three times now, and nothing gets updated.  The Iobit Uninstall monitor does not tell me that Firefox has been updated, and, after Firefox has restarted, I see the same "Restart" message in the Help pop-up window.

[siffemcon]

Bug - https://bugzilla.mozilla.org/show_bug.cgi?id=1941931.

Workaround: in about:config, set

app.update.multiSessionInstallLockout.enabled

to false.

[Tisteph]

Ok, I will try this because since the release 135 I have to close and restart Firefox to get the update applied.

[Agentvirtuel]

Hello

https://support.mozilla.org/en-US/questions/1500167
https://www.camp-firefox.de/forum/thema/139165-ff-update-problem

Today, 137.0 as far as i'm concerned, i can confirm this bug, i had the malfunction. about:config, app.update.multiSessionInstallLockout.enabled is true by default, i changed nothing and I'm waiting for the next updates.

[bsfinkel]

I posted earlier in this thread that I had the same problem.  With subsequent Firefox updates I have had to change this setting from true to false before the update and then setting it back after the update (EXCEPT 138.0.1 to 138.0.3 on 5/14/2025).  Today (5/27) I changed the value from true to false.  After the update, when I went to reset the value back to true, the interface had changed, and I was unsure how to change it back.  The interface no longer has a "switch from T to F or vice versa".  I am not sure how to set this setting back to "true", and I am not sure if I will have problems if I do not set this variable back to "true".

[siffemcon]

The bug, although not marked as fixed, is as of v138. And the app.update.multiSessionInstallLockout.enabled pref has been deprecated which is why it no longer appears. So everything should be OK from now on.

[bsfinkel]

When I tried to update to update to 139.0 today (from 138.0.4), my first attempt did not succeed.  Then I changed the parameter app.update.multiSessionInstallLockout.enabled:  true-->false and the update succeeded.  Does this imply that the bug was not fixed in 138.0.4 but MAY be fixed in 139.0?    I won't know until I get the first update to 139.0.  And since this parameter has been deprecated, I do not know if it is gone entirely or is now set to false, as I cannot change it back to true.

[siffemcon]

I'm not sure what's going on - the update to 139 shouldn't have had that problem. The pref has no effect any more. If there is a trash can icon for it, click it. If this happens again with 139.0.1 when it comes, report it as a possible bug (https://bugzilla.mozilla.org/enter_bug.cgi/). If you end up doing that, please post the link to it here.

[siffemcon]

BTW, closing FF > restarting was another workaround to get the update to take.

[siffemcon]

This problem is fixed with v139.01. It wasn't an actual bug, just a problem with versioning.

[Agentvirtuel]

Hello

https://connect.mozilla.org/t5/discussions/firefox-would-not-update-with-restart/m-p/94674
Feedback, as far as i'm concerned.
Windows 139.0, Restart to update Firefox, no problem. https://www.youtube.com/embed/TolVkkIqUFA
Linux 139.0, Restart to update Firefox, no problem.