Firefox Beta couldn't update automatically 109.0 -> 110.0b1
Categories
(Toolkit :: Application Update, defect, P3)
Tracking
()
People
(Reporter: bugzilla, Unassigned)
Details
Attachments
(3 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/110.0
Steps to reproduce:
Autoupdate from 109.0 to 110.0b1 using autoupdate
Actual results:
Upon restarting Firefox advised:
Update available
Firefox couldn't update automatically. Download the new version — you won't lose saved information or customizations.
Instead of pressing Download I pressed Dismiss, then attempted the autoupdate a second time. This time it was successful.
Expected results:
Autoupdate normally takes only the one time.
Comment 1•2 years ago
|
||
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•2 years ago
|
||
Since an update has succeeded, all of the useful logs are probably already be gone. If this happens again, before attempting another update, please send us your update logs:
- Navigate to
about:support
- Find the "Update Folder" entry and click "Open Folder".
- Open the
updates
directory. - Inside, you should find files named
last-update.log
andbackup-update.log
. Attach both of these files to this bug.
Reporter | ||
Comment 3•2 years ago
|
||
This one is definitely after the successful update.
Reporter | ||
Comment 4•2 years ago
|
||
I think this one might be timestamped before the successful update, but quite possibly was immediately after the successful update.
Reporter | ||
Comment 5•2 years ago
|
||
Thanks, Kirk. I'll take the suggested actions before reattempting the update next time!
Comment 6•2 years ago
|
||
It looks to me like backup-update.log
is from the successful update, and last-update.log
is from an even newer one that has been downloaded and staged but not actually installed yet (these logs are created both during staging and installation).
There are some other logs that could potentially be helpful too, depending on what sort of problem you are encountering. The fact that you saw the manual update prompt "Upon restarting Firefox", the highest likelihood is that there was some kind of error during installation, in which case the relevant error would be in the log files that I already described.
But you may want to navigate to about:config
and set app.update.log
to true
, just in case. If the error is actually coming from the download or staging phases of update, I'll need a log collected from within Firefox by turning that preference on before the failure and then opening the Browser Console (either with the hotkey Control+Shift+J, or via Hamburger Menu->More Tools->Browser Console), setting the filter to AUS:
and attaching the resulting log messages to this bug.
Reporter | ||
Comment 7•2 years ago
|
||
Haven't replicated this applying the b1->b2 or b2->b3 updates. Will see if it reoccurs when doing 110.0->111.0b1 and if not I will close this one.
Updated•2 years ago
|
Reporter | ||
Comment 8•2 years ago
|
||
Could not replicate this applying the update to 111.0b1 so closing this.
Description
•