1948829 - FF Beta 136 dont update

Status: RESOLVED DUPLICATE of bug 1941931

(Toolkit :: Application Update, defect)

Description

[ensarisik]

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

Steps to reproduce:

Check update: Menu>Help>About
then a update ready> update download > when i was click restart to update
FF beta restart but dont update
Try troubleshoot mode but still continue

Actual results:

FF beta restart but dont update

Comment 1

[BugBot [:suhaib / :marco]]

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

[Nick Rishel [:nrishel]]

:ensarisik Could you get the updater logs for us?

Gets logs for the updater tool in Firefox

1. Navigate to about:config.
2. Set app.update.log to true.
3. Open the Browser Console either with the hotkey Control+Shift+J (Command+Shift+J on macOS), or via Hamburger Menu->More Tools->Browser Console
4. In the Filter textbox at the top, enter AUS:SVC to filter out everything except the update messages.
5. Navigate to the "Update" section of about:preferences. It should automatically check for an update.
6. Once the update check has completed, copy the messages out of the Browser Console and attach them to this bug.

Get logs from updater binary that actually applies the updates

1. Navigate to about:support
2. Find the "Update Folder" entry and click "Open Folder".
3. Open the updates directory.
4. Inside, you should find files named last-update.log and backup-update.log. Attach these files to this bug.

Comment 3

[ensarisik]

Attachment: backup-update.log

Comment 4

[ensarisik]

Attachment: last-update.log

Comment 5

[ensarisik]

hi :nrishel
its logs.

(In reply to Nick Rishel [:nrishel] from comment #2)

Comment 6

[Nick Rishel [:nrishel]]

:bytesized I think this might be a dupe of Bug 1941931? 2025-02-21 12:46:37+0300: updateLockFileHandle==INVALID_HANDLE_VALUE

Comment 7

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

(In reply to Nick Rishel [:nrishel] from comment #6)

:bytesized I think this might be a dupe of Bug 1941931?

It's possible. There isn't really enough information here to tell.

2025-02-21 12:46:37+0300: updateLockFileHandle==INVALID_HANDLE_VALUE

That's normal. Inability to open that lock is how we know we need elevation.

---

Does the problem still happen if you set app.update.multiSessionInstallLockout.enabled to false?

Comment 8

[ensarisik]

hi :bytesized

i tried 136b9 to 136 update, use app.update.multiSessionInstallLockout.enabled to false
no problem. update successful. its ok.