1846764 - Firefox automatic background update problem

Status: RESOLVED WORKSFORME

(Toolkit :: Application Update, defect)

Description

[sunyix]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36

Steps to reproduce:

Checked the following:

• We installed the Firefox with installer. From the Installer, we created an Intune package and distributed for the devices.
• I checked the Mozilla Maintenance Service and it is in "manual" status. I think, it means, that if necessary the firefox can start it.
• Users already have profiles
• We enable the option to choose any language, so some devices maybe use different, but for example on my device is English is the default and the background update is not working (only if I start the Firefox browser)
  -Firefox connection settings configured to use the system proxy - I've checked.
  -Firefox schedule task is available

Actual results:

Hi,
We have problems with Firefox automatic update function. 1000 devices updated successfull to 115.0.3, but there are 4000 devices which stuck on 115.0.1 version. By default the "Use a background service to install updates" setting is enable and the scheduled task for the background update is exist.

• We installed the Firefox with installer. From the Installer, we created an Intune package and distributed for the devices.
• I checked the Mozilla Maintenance Service and it is in "manual" status. I think, it means, that if necessary the firefox can start it.
• Users already have profiles
• We enable the option to choose any language, so some devices maybe use different, but for example on my device is English is the default and the background update is not working (only if I start the Firefox browser)
  -Firefox connection settings configured to use the system proxy - I've checked.
  -Firefox schedule task is available

Could you please help me, why the Firefox automatic background update is not working on 4k devices?

Expected results:

The Firefox should be updated in the background without user interaction, because of security reasons.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Toolkit::Application Update' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Robin Steuber (she/her) [:bytesized]]

It sounds to me like we are talking specifically about updating Firefox when it is not running, is that correct? That feature currently will not work if your default profile has langpacks installed. You mention running in English, so I am guessing that you are aware of this. We can investigate why that machine is not using the Background Update Agent, but you should be aware (for the other devices) that there is currently no configuration that allows the Background Update Agent to run if langpacks are being used.

Please collect the following logs on the device using English where background updates are not working:

1. Navigate to about:config and set app.update.background.loglevel to debug.
2. Open the Hamburger Menu in the top left of the browser and click Exit. Wait for Firefox to exit completely.
3. Re-open Firefox.
4. Open the Browser Console either with the hotkey Control+Shift+J, or via Hamburger Menu->More Tools->Browser Console
5. In the Filter Output box at the top, type BackgroundUpdate.
6. Attach the resulting log messages to this bug.

Comment 3

[sunyix]

Hi,
Thank you for your fast response.

So, We have 4000 devices where the automatic update is not working.
Not only the background update, but also the automatic update when the users use the Firefox browser.

I will collect the logs about the background update as you requested.
Thank You

Comment 4

[sunyix]

Hi,

I have created the requested log on 2 test devices and attached the logs to this ticket.

1. • Device1
     -Installed with installer file (Intune package)
     -No language pack install
     -Firefox proxy not configured
     -Firefox Scheduled task available

but the Background update was not working. (I restarted the device several times, Started the scheduled task manually several times and it was running without problem, but the Firefox version was not updated. I did not open the browser, only check the C:\Program Files\Mozilla Firefox\firefox.exe - right click - properties - Details - Product Version or checked via powershell)
When I opened the Firefox browser the version was updated immediately to 116.0

So, is it possible, that after the successful background update needs a browser start for apply the new version?
Or should be work in the background without browser start?

2. • Device2
     -Installed with installer file (Intune package)
     -Hungarian language pack installed
     -Firefox proxy not configured
     -Firefox Scheduled task not available

I know that in this case the background update is not possible because of the language pack, but I send you the logs maybe there is any relevant information in.

If my coll started the Firefox browser, some times ago the browser version was updated from 115.0.1 to 115.0.3.

Thank You

Comment 5

[sunyix]

Attachment: Device1.txt

Comment 6

[sunyix]

Attachment: Device2.txt

Comment 7

[Robin Steuber (she/her) [:bytesized]]

(In reply to sunyix from comment #4)

but the Background update was not working. (I restarted the device several times, Started the scheduled task manually several times and it was running without problem, but the Firefox version was not updated. I did not open the browser, only check the C:\Program Files\Mozilla Firefox\firefox.exe - right click - properties - Details - Product Version or checked via powershell)
When I opened the Firefox browser the version was updated immediately to 116.0
So, is it possible, that after the successful background update needs a browser start for apply the new version?
Or should be work in the background without browser start?

The background task is not capable of updating Firefox "all at once". The first time it runs, it searches for updates and, if it finds one, it requests that Windows download the update file for it and then exits. The next time that it runs (assuming that the update download has completed), it prepares the update for installation. Then the next time after that it actually installs the update. We are working on combining those last two steps in Bug 1704855, which I expect will probably be ready in Firefox 118. But for the time being, it requires a minimum of three runs of the Background Update Agent to completely install an update, more if the download hadn't completed when it ran the second time.

Another factor in updates taking some time is that when we first release an update, we typically throttle it; not every client gets the update all at once. It's not currently clear to me if this is part of the reason that some clients haven't updated yet, but it's a possibility.

In any event, I don't think that there is any problem with this device as Firefox does seem to be successfully installing updates.

2. • Device2
     -Installed with installer file (Intune package)
     -Hungarian language pack installed
     -Firefox proxy not configured
     -Firefox Scheduled task not available

I took a look at the logs for this device and the only reason that it can't use the Background Update Agent is because of the installed langpack.

---

If there are other devices that aren't updating as expected, please provide the same logs requested in Comment 2 for one of those devices.

Comment 8

[sunyix]

Hi,

So, If the Background task completed successfully (after 3 or more run), than the Firefox version will changed from 115.0.1 to 116.0 and for this version change the Firefox browser start is not necessary, if I understand correctly.

• In the case if the users installed any language pack, this background update will not working, but is the automatic update function working? So, If the user start the Firefox and working in the browser some hours the automatic update will find the new update and install it? And this installed new update will apply immediately or browser restart will necessary for the apply? Is there any chance to force this restart with policy? because some users use their devices without restart, so the opened browser will stay on the old version and the security team will alert us immediately because of the outdated browser.

Thank You

Comment 9

[Robin Steuber (she/her) [:bytesized]]

(In reply to sunyix from comment #8)

So, If the Background task completed successfully (after 3 or more run), than the Firefox version will changed from 115.0.1 to 116.0 and for this version change the Firefox browser start is not necessary, if I understand correctly.

Correct.

• In the case if the users installed any language pack, this background update will not working, but is the automatic update function working? So, If the user start the Firefox and working in the browser some hours the automatic update will find the new update and install it?

Yes. Firefox will check for updates every 12 hours on the Release channel. If the 12 hour timer would have expired when Firefox was not open, it will check for update shortly after it is next started. Because of update throttling though, it may take longer than this would suggest to actually find and install the update. You can bypass the timer and update throttling by manually checking for an update in either the "Update" section of about:preferences or the About dialog.

And this installed new update will apply immediately or browser restart will necessary for the apply?

The update will apply after a browser restart.

Is there any chance to force this restart with policy? because some users use their devices without restart, so the opened browser will stay on the old version and the security team will alert us immediately because of the outdated browser.

After some time has passed, we will prompt the user to restart, but will not force them to. We are actually working on a policy that would allow the administrator to force a restart after update. But it's still in the planning stages and I couldn't give an accurate estimate as to when it will be available.

---

It sounds like update is working as expected, so I am going to go ahead and close this bug.