1489871 - Firefox nightly NOT start after internal update

Status: RESOLVED INCOMPLETE

(Toolkit :: Application Update, defect)

Description

[37313]

User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0
Build ID: 20180908220614

Steps to reproduce:

Firefox Nightly - Setting - Update now. 
Update file download and button say "restart nightly for update".
I press "restart Nightly now"


Actual results:

Its ALL - Nightly NOT start anymore, if i launch link Nightly - its NOT start, no error messages appears and no nightly in process - nothing happens at all.
Problem in profiles's folder - 
if you replace the browser itself except for the profile folder - it also does not start.
If install new version Nightly over current(which does not start)- its not start too.

if you return all Nightly folders at the time before the internal update (It has been saved) and download the new version Nightly by a separate installer, you can install it over current Nightly and the Nightly will update and start normally.

From 12 august this happend.


Expected results:

I expected that - Nightly will start after internal update.

Comment 1

[Kanchan Kumari QA]

I couldn't replicate this issue on
Version 	64.0a1
Build ID 	20180908220614
User Agent 	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0

Nightly updates and restarts fine for me. Placing this under Toolkit:Application Update, so someone can look into it. Thanks!

Comment 2

[Molly Howell (she/her) (no longer active)]

Thanks for the report. Let's see if we can figure this out.

(In reply to 37313 from comment #0)
> if you return all Nightly folders at the time before the internal update (It
> has been saved) and download the new version Nightly by a separate
> installer, you can install it over current Nightly and the Nightly will
> update and start normally.

Can you describe in more detail what you did here? From what you wrote I can't tell what's difference about this vs. just installing over the existing copy (which you said didn't help).

Comment 3

[Kanchan Kumari QA]

(In reply to Kanchan Kumari QA from comment #1)
> I couldn't replicate this issue on
> Version 	64.0a1
> Build ID 	20180908220614
> User Agent 	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:64.0)
> Gecko/20100101 Firefox/64.0
> 
> Nightly updates and restarts fine for me. Placing this under
> Toolkit:Application Update, so someone can look into it. Thanks!

Sorry I forgot to mention, I tested on following too but no luck in reproducing this bug.

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

Comment 4

[37313]

	Matt Howell
>what's difference about this vs. just installing over the existing copy

Full installing new version over the existing copy helps always.
It NO helps if you first tried an internal update.
Internal update KILL my installed Nightly an NOTHING helps after.
I create a backup of all files Hightly before attempting an internal or full update and I can try different sequence.

I tried to compare the files after an unsuccessful internal update and after a successful full update. in both cases, the browser claimed that the "latest version" was installed. But file versions are different! 
May be the Nightly is requesting incorrect files for the internal update.

If I send a program for testing this error, I will send the required report.
Or tell me which file to send for research.

Comment 5

[Molly Howell (she/her) (no longer active)]

It's unlikely that an incorrect update file is being served up, but we can tell for sure if you're willing to collect a couple of logs. Here's how to get the log that will tell us which update file is being downloaded:

1) In the address bar, type "about:config" (without the quotes) and press Enter. You'll see a warning message; click the button to continue.
2) In the search box at the top of the page, type "app.update.log" (again without the quotes). That should reduce the list to one item; double-click that line to turn it bold and change the Value to true.
3) Restart Firefox.
4) Open the Browser Console by pressing Ctrl+Shift+J (Cmd+Shift+J if you're on a Mac) or selecting the item from the Web Developer menu.
5) Open the About dialog again.
6) Look for messages in the browser console window that start with "AUS:SVC". Copy and paste those messages here.

There's also a log file that's recorded during applying the update, so it can tell us if anything out of the ordinary is happening during that process. Probably the easiest way to find it is:

1) Open "about:config" again, and this time search for and set "devtools.chrome.enabled".
2) Open the browser console again.
3) Now you should have an input box at the bottom of the window. In that box, paste in this line:

Services.dirsvc.get("UpdRootD", Ci.nsIFile).reveal()

and press enter.
4) That should have opened a file explorer window. Open the updates directory and you should see last-update.log. You might also have update.log in the "0" directory. Please attach those files if they exist.

Thanks again.

Comment 6

[37313]

Attachment: last-update.log

Comment 7

[37313]

1. "AUS:SVC" = I just replaced my username with ***:

AUS:SVC Creating UpdateService
AUS:SVC isServiceInstalled - returning true
AUS:SVC shouldUseService - returning false
AUS:SVC getCanApplyUpdates - testing write access C:\Users\***\AppData\Local\Mozilla\updates\20DEEDB25E1CD17C\update.test
AUS:SVC getCanApplyUpdates - able to apply updates
AUS:SVC getCanStageUpdates - staging updates is disabled by preference app.update.staging.enabled
AUS:SVC isServiceInstalled - returning true
UTM:SVC TimerManager:notify - notified @mozilla.org/updates/update-service;1
AUS:SVC Checker:getUpdateURL - update URL: https://aus5.mozilla.org/update/6/Firefox/64.0a1/20180918075510/WINNT_x86_64-msvc-x64/ru/nightly/Windows_NT%206.3.0.0.9600%20(x64)/ISET:SSE4_2,MEM:16348/default/default/update.xml
AUS:SVC UpdateService.canCheckForUpdates - able to check for updates
AUS:SVC Checker: checkForUpdates, force: false
AUS:SVC UpdateService.canCheckForUpdates - able to check for updates
AUS:SVC Checker:getUpdateURL - update URL: https://aus5.mozilla.org/update/6/Firefox/64.0a1/20180918075510/WINNT_x86_64-msvc-x64/ru/nightly/Windows_NT%206.3.0.0.9600%20(x64)/ISET:SSE4_2,MEM:16348/default/default/update.xml
AUS:SVC Checker:checkForUpdates - sending request to: https://aus5.mozilla.org/update/6/Firefox/64.0a1/20180918075510/WINNT_x86_64-msvc-x64/ru/nightly/Windows_NT%206.3.0.0.9600%20(x64)/ISET:SSE4_2,MEM:16348/default/default/update.xml
AUS:SVC Checker:onLoad - request completed downloading document
AUS:SVC Checker:onLoad - Getting sslStatus failed.
AUS:SVC Checker:onLoad - number of updates available: 1
AUS:SVC UpdateManager:_loadXMLFileIntoArray - XML file does not exist. path: C:\Users\***\AppData\Local\Mozilla\updates\20DEEDB25E1CD17C\active-update.xml
AUS:SVC isServiceInstalled - returning true
AUS:SVC shouldUseService - returning false
AUS:SVC getCanApplyUpdates - testing write access C:\Users\***\AppData\Local\Mozilla\updates\20DEEDB25E1CD17C\update.test
AUS:SVC getCanApplyUpdates - able to apply updates
AUS:SVC UpdateService:_selectAndInstallUpdate - prompting because silent install is disabled. Notifying observers. topic: update-available, status: show-prompt

after copy AUS:SVC im do internal update. Nightly not start after this. Then i copy and attach file:

2. Im attach last-update.log, in "0" directory only files update.mar, update.status, update.version. - no file update.log

Comment 8

[Molly Howell (she/her) (no longer active)]

Thanks for the info.

(In reply to 37313 from comment #7)

The AUS log here is completely normal, there's no problem there. Specifically, it doesn't look like we're downloading any incorrect update files.

> 2. Im attach last-update.log, in "0" directory only files update.mar,
> update.status, update.version. - no file update.log

That's the normal state when an update has been downloaded and is ready to apply, so that's fine.

(In reply to 37313 from comment #6)
> Created attachment 9010286 [details]
> last-update.log

I am a little confused about what's going on in this updater log file. The log is for a "complete" update, which means it tried to remove all the existing files and create a totally new copy. And it thinks the update succeeded with some recoverable errors, which are that the subdirectories within the Firefox directory couldn't be deleted because they weren't empty. The reason that's odd is that the log also says all the files that should have been in those directories had already been removed, so they should have been empty.

Can you attach a listing of your B:\Firefox directory? Apparently something is in there that our updater isn't expecting, and maybe that's causing some of the problems. Thanks again.

Comment 9

[Robert Strong (they/them - no direct email)]

No response to requested information in comment #8 so resolving as incomplete