Closed
Bug 1438855
Opened 7 years ago
Closed 7 years ago
Updates failed
Categories
(Toolkit :: Application Update, defect)
Toolkit
Application Update
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: ekr, Unassigned)
Details
Attachments
(2 files)
I did Firefox Nightly | About Nightly and was rewarded with:
Reporter | ||
Comment 1•7 years ago
|
||
I then clicked the green arrow in the hamburger menu and got:
Reporter | ||
Comment 2•7 years ago
|
||
Another reboot and About Nightly got me a working update.
Comment 3•7 years ago
|
||
Unfortunately now that the update has gone through, there isn't anything left that we can use to debug the failed attempt.
If this happens again though, the update service log should be able to tell us what's going on. If you go ahead and turn on the app.update.log pref, then there should be some relevant logging in the browser console (messages starting with "AUS:SVC"). Thanks.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 4•7 years ago
|
||
Even *without* knowing the cause, I think having the updater just abandon attempting to update and tell me to do it manually is pretty suboptimal behavor.
![]() |
||
Comment 5•7 years ago
|
||
Post an update going through, are there any logs we can look at for clues?
I'm thinking bug 1413146 would have helped here.
Flags: needinfo?(mhowell)
Comment 6•7 years ago
|
||
Bug 1413146 would not have helped with this, unfortunately. That logging just goes to the browser console, it isn't stored anywhere, so it still has to be collected manually at the time the problem happens, and it's gone once the browser restarts (e.g. when an update does get applied). We would have to be writing those messages out to a file for them to have been useful here.
That said, I do think there's value in bug 1413146 and would advocate for doing it.
Flags: needinfo?(mhowell)
You need to log in
before you can comment on or make changes to this bug.
Description
•