FF autoupdated regardless of autoupdate being off
Categories
(Toolkit :: Application Update, defect)
Tracking
()
People
(Reporter: zkaleta, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:83.0) Gecko/20100101 Firefox/83.0
Steps to reproduce:
- Changed app.update.auto to false
- Used FF for some time (a week)
- Opened FF in the morning, switched to another tab
Actual results:
The "We just need to do just one small thing" page opened - restart needed after update.
Expected results:
I don't want FF to install the updates automatically. When I work using FF I don't want it to just need restarting because it has updated without permission. As far as I remember it is my computer, not Mozilla's, thus I should be the one in charge.
|
||
Comment 1•5 years ago
|
||
I tried to reproduce this issue on the latest version of Firefox Nightly 85.0a1 (2020-11-24) using the given preference and after restart Firefox did not update.
Setting a component for this issue in order to get the dev team involved.
If you feel it's an incorrect one please feel free to change it to a more appropriate one.
|
||
Comment 2•5 years ago
|
||
(In reply to zkaleta from comment #0)
The "We just need to do just one small thing" page opened - restart needed after update.
The page you are describing is not the "we want to install an update" notification, it is actually the "an update was externally installed while we were running and now the binary on disk doesn't match the binary that's currently running, so we can't start a new child process" prompt. It's possible that another instance of Firefox updated the installation while you were using it. Since you appear to be on Linux, however, it is quite likely that you are using a package manager, which is updating Firefox while it is running, causing this problem.
Do either of those explanations sound accurate to you? Are there other instances of Firefox running (possibly as other users)? Is Firefox updated via a package manager?
(In reply to Kirk Steuber (he/him) [:bytesized] from comment #2)
(In reply to zkaleta from comment #0)
The "We just need to do just one small thing" page opened - restart needed after update.
The page you are describing is not the "we want to install an update" notification, it is actually the "an update was externally installed while we were running and now the binary on disk doesn't match the binary that's currently running, so we can't start a new child process" prompt. It's possible that another instance of Firefox updated the installation while you were using it. Since you appear to be on Linux, however, it is quite likely that you are using a package manager, which is updating Firefox while it is running, causing this problem.
Do either of those explanations sound accurate to you? Are there other instances of Firefox running (possibly as other users)? Is Firefox updated via a package manager?
I know it's after the update.
Only I use this computer and there wasn't another window of Firefox opened.
Firefox could have been updated by system update manager. In such a case I would owe you an apology. I will pay extra attention to that the next time I get prompted to install updates (or FF gets updated).
Do I understand correctly: If Firefox updates via autoupdate, said page should NOT appear?
|
|
||
Comment 4•5 years ago
|
||
(In reply to zkaleta from comment #3)
Do I understand correctly: If Firefox updates via autoupdate, said page should NOT appear?
That is correct. That page is the result of us not being able to create a new process because the binary was updated when we didn't expect it to be. With Firefox automatic updates, we don't install them in such a way. We install updates when Firefox restarts. We do eventually prompt you to restart when an update is ready to be installed, but it is displayed and phrased differently and you can easily dismiss the notification and choose to restart whenever you like. If you are getting the "We just need to do just one small thing" page, it is not Firefox automatic update working as expected; it is Firefox reacting to an update being thrust upon it when it wasn't ready.
|
||
Comment 5•5 years ago
|
||
The severity field is not set for this bug.
:mhowell, could you have a look please?
For more information, please visit auto_nag documentation.
|
||
Comment 6•5 years ago
|
||
All indications are that this is being triggered by package manager updates, and that's a known problem, so I'm marking this bug as a duplicate. Do feel free to reopen it if that isn't he case though.
Unless the package manager is updating FF without any indication about it, this is not the reason for this problem.
Today the package manager suggested an update of some packages, but I clicked "Remind me later". Still some time later (about an hour, but I didn't open any new tab during that time) the Oops-page appeared.
Do you know a way to check if it really is an update manager messing with FF?
The problem occurred several times in the past but usually after package manager updated something (not FF itself, but maybe some libraries). Today it shouldn't have updated anything.
The system is Xubuntu 20.04, FF is 86.0.1 (64bit).
|
|
||
Comment 8•5 years ago
|
||
(In reply to zkaleta from comment #7)
Do you know a way to check if it really is an update manager messing with FF?
I don't know which package manager you are using and, even if I did, I probably can't provide support for it. You would probably have to consult with their documentation/support. But I can tell you how to check if Firefox is installing the updates. If you navigate to the Settings page (about:preferences), in the Update section you should find a button labelled "Show Update History". If Firefox is installing updates, they should end up in that history. If something else (like a package manager) is installing updates, those updates will not show up in that history.
So, I would recommend checking that history when you see this problem. If the "Installed on" date and the version match the update that was just installed, then the update was installed by Firefox. If the last update listed in that history is not the update that was just installed, something outside of Firefox is most likely updating it.
Description
•