Firefox will sometimes stop me from making a new tab and force me to update, is there a way to bypass this screen? Just to be clear I don’t want to remove auto-updates, just stop it from forcing me.
Today I was writing something and it made me update. Meaning I had to stop working on the thing I was writing so I could close the browser. Then when it updated it deleted all my toolbars whyyyyyy.
It’s a technical limitation why Firefox has to force the restart.
If you’re not on Linux (or using a build with auto-updater anyways), then the only way to stop this is to turn off auto-updates.
However, it will still notify of new updates and then you can decide when to do the update: https://support.mozilla.org/en-US/questions/1448482Then when it updated it deleted all my toolbars whyyyyyy.
Deleted your toolbars? Maybe raise a bug about that in the Firefox bug tracker.
If you mean tabs then there’s a setting to keep tabs are a restart. Makes restarting less of an issue. I have about 60 tabs open at any one time and haven’t lost one in years over multiple restarts and upgrades.
If you mean tabs then there’s a setting to keep tabs are a restart
That’s never worked for me. If I close FF and reopen its starts fresh with.noting open. If I close the OS, and restart only then does FF reopen all the tabs.
I am currently on LMDE but the same process happened when I was on Windows 10 and Linux Mint . I have the setting selected to restore previous open tabs but it’s just never worked across many years, many updates and multiple OS’s.
Strange. Works for me running Ubuntu on two different laptops. 🤷
I’m on nightly, so it doesn’t really count, but a week ago or so all addons (yes, all 20) were instantly uninstalled (including the “sad to see you go”-screens of some), and once all tabs were closed. With backups I figured out which I needed and reinstalled them, but … pretty annoying.
Firefox shouldn’t force you to restart and update like that unless something else, such as your package manager, has already replaced the executable files on your disk. In such a scenario Firefox doesn’t have any option except to inform you to restart it (well I guess it could choose to crash). But the mechanism that forced the update is the package manager.
That is the case, if you’re updating it via package manager, yes. But if you’re using the built-in auto-updater (like people tend to do on Windows and macOS), then it happens automatically in the background, unless you tell the auto-updater to not update automatically.
But if you’re using the built-in auto-updater (like people tend to do on Windows and macOS), then it happens automatically in the background, unless you tell the auto-updater to not update automatically.
Definitely does not work that way on my Windows 10 installation. When update is available, Firefox will have a “Restart to install updates” in menu button notification - but the files are not replaced on disk until you actually close (or restart) Firefox and thus Firefox continues to work normally.
What can happen though is that if you run another instance (ie. another profile) of Firefox while the first one has “staged” the update then that another instance can trigger the files to actually be replaced on disk but you would very deliberately do that.
Ah, hmm, maybe that’s just how it works on Linux and macOS then. I was wondering, because Windows doesn’t support replacing files while they’re opened in a process, so I guess makes sense that it needs the restart upfront…
One of my biggest complaints with snap
If you see that screen FF already concluded its update, the running version of FF and the installed version are different at that point.
Correct. That being said, it would be nice to build in some way of forward compatibility.
Firefox will not force an update - but it will tell you to restart to continue AFTER it has been updated… learn to control your updates, don’t use Firefox as a Snap if that’s what’s going on.
Don’t use the Snap version of Firefox
