1944243 - Problem with updating Firefox v135 Beta

Status: UNCONFIRMED

(Toolkit :: Application Update, defect, P3)

Description

[John Gallon]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:135.0) Gecko/20100101 Firefox/135.0

Steps to reproduce:

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:135.0) Gecko/20100101 Firefox/135.0

Pop-up showed asking me if I wanted to download the latest update. Brought down the update and went to Help > About Firefox and clicked on the button "Restart to Update Firefox".

Actual results:

Firefox closed and re-opened immediately without applying the update.

Expected results:

The closure process should give time for the program to close down completely and then re-open. This re-opening triggers the update process.

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

[Eric Chen]

Hi John, thank you for the report. I'd like to collect some update logs to further investigate the issue.

To do this, go to about:config, search for app.update.log and set it to true. Then press Ctrl+Shift+j (or use the burger menu ☰ -> More Tools -> Browser Console) and watch what happens when you open the help dialog again and try to update. Please copy the log messages that start with AUS: from there to the clipboard and paste them here. We want to capture the logs when this bug is happening.

Can you also let me know if you have any nightly or release version of Firefox running at the same time while you attempt to update beta?

Thanks!

Comment 3

[John Gallon]

I'll have to wait for the next update (current version showing as v135.0 in the help screen so may be a day or two then it will be an update to v136).

No other versions of Firefox on the system so nothing running in tandem.

Comment 4

[John Gallon]

Help > About Firefox invited me to update to v135.0. Clicked on the Update button and Firefox closed and re-opened without updating.

Extract from Console:

01:30:00.496 AUS:SVC readStatusFile - status: pending, path: C:\ProgramData\Mozilla-1de4eec8-1241-4177-a864-e594e8d1fb38\updates\308046B0AF4A39CB\updates\0\update.status
01:30:00.496 AUS:SVC UpdateService:#asyncInit - status = "pending"
01:30:00.496 AUS:SVC getCanApplyUpdates - testing write access C:\ProgramData\Mozilla-1de4eec8-1241-4177-a864-e594e8d1fb38\updates\308046B0AF4A39CB\update.test
01:30:00.496 AUS:SVC getCanApplyUpdates - bypass the write since elevation can be used on macOS and Windows
01:30:00.497 AUS:SVC UpdateService:#asyncInit - Setting update's state from the status file (="pending")
01:30:00.498 AUS:SVC UpdateService:#asyncInit - Verifying existing pending update.
01:30:00.498 AUS:SVC UpdateService:writeTimestampFile - Writing Tue Feb 04 2025 01:29:50 GMT+0000 (Greenwich Mean Time) (1738632590579)
01:30:00.733 Warning: attempting to write 13941 bytes to preference browser.uiCustomization.state. This is bad for general performance and memory usage. Such an amount of data should rather be written to an external file. 22
01:30:01.092 UTM:SVC TimerManager:registerTimer - timerID: browser-cleanup-thumbnails interval: 3600 skipFirst: false
01:30:01.465 UTM:SVC TimerManager:registerTimer - timerID: rs-experiment-loader-timer interval: 21600 skipFirst: false
01:30:01.853 Content-Security-Policy: Couldn't parse invalid host 'wasm-eval' _generated_background_page.html
01:30:01.959 UTM:SVC TimerManager:registerTimer - timerID: region-update-timer interval: 604800 skipFirst: false
01:30:01.967 UTM:SVC TimerManager:registerTimer - timerID: recipe-client-addon-run interval: 21600 skipFirst: false
01:30:02.118 AUS:SVC UpdateService.canUsuallyCheckForUpdates - able to check for updates
01:30:02.118 AUS:SVC UpdateService.canCheckForUpdates - able to check for updates
01:30:02.118 AUS:SVC CheckerService:checkForUpdates - checkType: 2
01:30:02.118 AUS:SVC CheckerService:checkForUpdates - Making new check request for check id 1.
01:30:02.127 AUS:SVC CheckerService:getUpdateURL - checkType: 2
01:30:02.147 AUS:SVC CheckerService:getUpdateURL - update URL: https://aus5.mozilla.org/update/6/Firefox/135.0/20250127201358/WINNT_x86_64-msvc-x64/en-GB/beta/Windows_NT%252010.0.0.0.19045.5371%2520(x64)/ISET%3ASSE4_2%2CMEM%3A16151/default/default/update.xml?force=1
01:30:02.147 AUS:SVC CheckerService:#updateCheck - sending request to: https://aus5.mozilla.org/update/6/Firefox/135.0/20250127201358/WINNT_x86_64-msvc-x64/en-GB/beta/Windows_NT%252010.0.0.0.19045.5371%2520(x64)/ISET%3ASSE4_2%2CMEM%3A16151/default/default/update.xml?force=1
01:30:02.214 QM_TRY failure (WARNING): 'Unavailable, storage-origin https://www.vesselfinder.com^partitionKey=%28https%2Cthegallons.co.uk%29, context dom::quota::FirstInitializationAttempt::TemporaryStorage', file dom/quota/ActorsParent.cpp:2843
01:30:02.231 Hey developer! Want to see more verbose logging? util.js:16:9
01:30:02.232 Type this into the console: let util = require('./util'); util.setDefaultLogLevel(util.VERB); util.js:17:9
01:30:02.232 Accepted levels are VERB, DBUG, INFO, NOTE and WARN, default is NOTE util.js:18:9
01:30:02.285 AUS:SVC CheckerService:#updateCheck - request got 'load' event
01:30:02.285 AUS:SVC CheckerService:#updateCheck - request completed downloading document
01:30:02.286 AUS:SVC CheckerService:#updateCheck - number of updates available: 1
01:30:02.318 AUS:SVC UpdateService.canUsuallyCheckForUpdates - able to check for updates
01:30:02.319 AUS:SVC isServiceInstalled - returning true
01:30:02.319 AUS:SVC shouldUseService - returning false
01:30:02.319 AUS:SVC getCanApplyUpdates - testing write access C:\ProgramData\Mozilla-1de4eec8-1241-4177-a864-e594e8d1fb38\updates\308046B0AF4A39CB\update.test
01:30:02.319 AUS:SVC getCanApplyUpdates - bypass the write since elevation can be used on macOS and Windows
01:30:02.320 AUS:SVC getCanUseBits - BITS can be used to download updates
01:30:02.322 AUS:SVC UpdateService.canUsuallyCheckForUpdates - able to check for updates
01:30:02.322 AUS:SVC isServiceInstalled - returning true
01:30:02.322 AUS:SVC shouldUseService - returning false
01:30:02.323 AUS:SVC getCanApplyUpdates - testing write access C:\ProgramData\Mozilla-1de4eec8-1241-4177-a864-e594e8d1fb38\updates\308046B0AF4A39CB\update.test
01:30:02.323 AUS:SVC getCanApplyUpdates - bypass the write since elevation can be used on macOS and Windows

Manually closed Firefox, checked that all Firefox entries had been removed from Task Manager, then re-opened and the update took place.

Comment 5

[Chris DuPuis]

Hi John, in the about:config page, can you please search for the setting "app.update.service.enabled", and let us know if it is true or false?

Comment 6

[John Gallon]

Currently showing as false. Sorry for the delay in replying - didn't get notification.

Comment 7

[John Gallon]

Just been prompted for another update of v135.0. Reset the app.update.service.enabled to true and clicked Restart to Update Firefox. Again it closed program and immediately restarted without updating. Now reverted app.update.service.enabled to false and manually closed and re-started Firefox to complete the update.

Comment 8

[John Gallon]

Despite Help Screen telling me it was update to v135.0 actual update was to v136.0b1.

Comment 9

[Chris DuPuis]

Thanks for trying this out, John. The issue you're experiencing seems to be related to Bug 1941931. I'll associate this bug to that one.

Comment 10

[Chris DuPuis]

Marking as P3, since we already have the parent bug as P2.

Comment 11

[John Gallon]

Looks to be the same. As per #1941931 I'll reset app.update.multiSessionInstallLockout.enabled to false and report whether the next update works as expected.

Comment 12

[John Gallon]

Just got the nudge to update to v136.0b3.

Set app.update.multiSessionInstallLockout.enabled to true, clicked on the button to update and Firefox closed and re-opened immediately without updating. Reset app.update.multiSessionInstallLockout.enabled to false, clicked on the button to update and Firefox closed then applied the update and re-opened.

Comment 13

[John Gallon]

Faultlessly updating (over 3 or 4 cycles) with app.update.multiSessionInstallLockout.enabled set to false.