Nightly update doesn't actually get applied - continually prompts to apply an update after browser restart
Categories
(Toolkit :: Application Update, defect)
Tracking
()
People
(Reporter: rick3162, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Build ID: 20191023094816
The issue I'm having with Nightly for the last few days, starting from Nightly 71.0a1 10/20/2019,
is that the updates are not actually get applied and it continually prompts to apply an update after browser restart
STR
Using win10 x64 version 1903
Nightly version 72.0a1 (2019-10-23) (64-bit), fresh profile.
- either: click 'Menu' icon|Help|'About Nightly':
the browser automatically starts downloading the update (update size is 6.2 MB) - or: just click the 'Restart to update Nightly' entry prompt displayed on the Menu button
- restart browser
- notice that the update was not applied:
If I open Help|'About Nightly' it still downloads again the same/today's update (supposedly 2019-10-24),
and even if don't do anything, I I'm constantly getting the prompt to 'Restart to update Nightly' - At some point, that I can't tell what specific (sometimes it's after windows restart I relaunch Nightly, or maybe after a random UAC prompt appearance by Nightly), then the update gets applied. But even so, the issue always re-occurs with the next day's update: it has been happening to me in every single day starting from 2019/10/20 up today.
There's no entry in about:crashes nor any relevant entry in windows Event Viewer.
Possibly related bug entries:
https://bugzilla.mozilla.org/show_bug.cgi?id=1391903
https://bugzilla.mozilla.org/show_bug.cgi?id=1417609
I'd like to add that I've also tried uninstalling Nightly, removed previous profile and created a new one,
but the issue still occurs: it has been happening today, with my fresh Nightly installation being of 2019-10-25
and the 5.7 MB update doesn't get applied after multiple browser restarts. Eventually, after maybe the 5th browser restart , it downloaded a 53.9 MB update and and I got this message (see attached screenshot):
"Nightly can't update to the latest version.
Download a fresh copy of Nightly and we'll help you to install it"
Comment 3•6 years ago
|
||
Same here for some time, downloading full version does not help. Look like something corrupted in profile.
What logs I can collect to debug the issue?
Today the following occurred:
Nightly was of 2019-10-27.
I clicked: Help|'About Nightly', the browser started downloading the update (6.8 MB). Once again, after browser restart the update was not applied.
Then I clicked "Help|About Nightly", it remained(=kept on checking) at "Checking for updates", and so I closed the "About Nightly" window a few seconds later. Shortly after, I closed Nightly.
I launched Nightly again some time later, and I immediatelly got a UAC prompt (see attached photo),
I clicked "Yes" and then the update was applied ok, i.e. Nightly got updated to 2019-10-28.
Just one thing to add:
the issue only occurs with Nightly - it does not occur with my Firefox stable installation: just now it updated ok from 70.0 to 70.0.1 .
The issue still occurs for me.
Is there any info I can provide to help identify the cause of this issue?
Comment 7•6 years ago
|
||
The priority flag is not set for this bug.
:rstrong, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 8•6 years ago
|
||
I seem to be having the same issue on my Nightly on Windows 8.1, for several weeks now.
Please let me know if there's any information I can provide to help.
The issue no longer occurs, it's about 10 days now. (I hadn't changed anything in the Nighly installation, i.e. no re-installation or fresh profile creation).
Alexander Usyskin and Adrian Wielgosik, if that's also the case for you, please tell me so that I'll close this bug.
Comment 10•6 years ago
|
||
Yes, last week updates are successful, no change from my side in profiles. Go figure...
Comment 11•6 years ago
|
||
This is most likely due to the same underlying cause of bug 1596778 since this is no longer reproducible so duping
Description
•