1035400 - "restart to update" button not working. Prevents users from manually updating when the full update ui needs to be displayed (e.g. incompatible add-ons).

Status: RESOLVED FIXED

(Firefox :: General, defect)

Description

[Brian Warner [:warner :bwarner]]

I'm not sure when exactly this started happening, but I've noticed that my FF31 (beta)'s "Restart to Update" button (accessed via menu, Firefox > About Firebox) isn't working. I click on the button, but nothing happens.

I *think* that I was prompted to update about an hour ago (the full-size popup that occurs when a new beta version is available), and I chose "Ask Later" instead of "update now". I'm thinking that this put my browser into a state where the menu-reachable "Restart to Update" button stopped working. The last time this happened, I remember restarting my browser, but that didn't resolve the problem. I'll try to reproduce that now. I think I had to wait until the subsequent version update appeared before it started working again.

Comment 1

[Brian Warner [:warner :bwarner]]

Yeah, restarting the browser doesn't fix the problem: the "Restart to Update" button still does nothing. I don't see any relevant error messages in the Browser Console. My (Prefs > Advanced > Update) setting is "check for updates, but let me choose".

Comment 2

[Stijn Herreman]

This is happening on my FF30.

Comment 3

[Tom]

This is happening on my FF30 release channel, restart to update button does nothing.  Deleting all files in the C:\Users\username\AppData\Local\Mozilla\updates does nothing. Downloading Firefox Setup Stub 31.0.exe and installing, updates successfully.

Comment 4

[martin raud]

hello all who's reading.

i had similar problem today. 

Steps what i did to cause this 8i'm unsure that those are right steps what actually causing this )

1) Make sure there is Firefox update available
2) Download that update. If it stat saying "restart to update, don't click it.
3) close Firefox. upper right corner X , kill the process etc
4) Launch some older Aurora build. Lets say august 15th, you can pick
5) Update aurora , when it say's Restart to update the do it
6) Close aurora
7) Start Firefox again
8) go to Help>about Firefox
9) after clicking the "restart to update" u see that the button doesn't have any effect any more.

ps: If those reproducing steps doesn't work , them I'm extremely sorry for spamming.

Comment 5

[martin raud]

sorry for spam

what i forgot to tell was that i used same profile for both builds.

Comment 6

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

Please try it again in safe mode.
https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode

Comment 7

[killbugs]

I have this issue as well.  I have tried restarting in safe mode, but the update button still doesn't work.  I'm on Windows 7 Enterprise 64-bit, running release channel Firefox 31.

Perhaps this is relevant: if I have the Browser Console window open when I open the About Mozilla Firefox window to see if an update is available, this shows up after the spinner stops:

1409787428946	addons.update-checker	WARN	Update manifest for {BBDA0591-3099-440a-AA10-41764D9DB4DB} did not contain an updates property

Comment 8

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

Try the following:
Type about:config in the url bar
Click the button to accept
Paste the following in the search bar devtools.errorconsole.enabled
Toggle the value to true (can be done by double clicking or via the context menu)
Restart

Before you click the restart button the next time open Tools -> Web Developer -> Error Console and click the clear button. Leave the console open and click the restart button. Report in this bug anything that is displayed in the error console.

Comment 9

[killbugs]

After enabling the error console, restarting, and showing the error console, I get: exactly the same behaviour.  I get the same warning after the spinner stops, but no additional messages when clicking the Restart to Update button.

Comment 10

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

Could you try installing an add-on that is not listed as NO RESTART
https://addons.mozilla.org/en-US/firefox/extensions/

Open the add-ons manager and click the restart button for the add-on?

Comment 11

[killbugs]

Clicking the restart button in the add-ons area restarted the browser, but I was still at Firefox 31 when it came back up. And going to the About box showed the same behaviour as before.

I should note that one thing I am not seeing is any indication of the download happening.  While there is a spinner that runs for a bit, don't you usually see how big the update is, and how far along you are?  Anyway, not seeing that now.

Comment 12

[Varuna Seneviratna]

The 'Restart to Update' Button in the about box of Firefox 31.0 does not work.

Comment 13

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

Please open the context menu on the Firefox application bundle under Applications. Select "Show Package Contents". Navigate to the Contents/MacOS/updates/0/ directory. If present, attach the update.status file to this bug.

Comment 14

[FirefoxUser85]

I am getting the same while trying to update from Firefox 31.0 to 32.0. On clicking the button "Update to 32.0", it immediately changes to "Restart to Update" (it appeared almost as if it never even downloaded the update). Clicking "Restart to Update" now doesn't evoke any response. I'm running Windows 8 64-bit.

Comment 15

[Andrew Stein]

Same issue here; Firefox 33.0 Win8 x64; beta channel.

Was prompted to update but I dismissed the message as the update fails if Firefox is not running as Administrator. Re-ran Firefox as Administrator, went to Help->About as I usually do to update, the Restart to Update button doesn't do anything

Comment 16

[Tom]

Happened also to my update to 33.0.  Last time it happened it was my 30.0 to 31.0

Comment 17

[Varuna Seneviratna]

I think now this issue resolved yesterday I was able to update to 33.0 using the "restart to update' button in the about box

Comment 18

[luuk34]

Bug still exists when updating from 33.1 to 34  (in Windows 7)

No information in 'Error console'

Comment 19

[tomevans1412]

New to bugzilla here.  My restart button also does not work.  Win 7 64-bit Enterprise.  Firefox 33.1.1 to 34.  Please let me know if I can help fix.
Thanks,

Comment 20

[Peter]

Same problem here trying to update ver 33.1.1 on a Win 7 home (x64) platform today.  Also tried safe mode and disabling anti-virus without benefit.  Updated by manually navigating to Mozilla Firefox web page, which detected that I was already using FF, and downloading the update stub.  At that point, all went as expected.  This was the first time I ever encountered this bug despite numerous trouble-free updates in the past.

Comment 21

[Miha Vrhovnik]

Same as in comment #19. The difference is that I'm using Windows 7 Pro.

Comment 22

[Michael]

I am using Firefox 33.1.1 on Win7 (x64) Professional. This Problem occurs while I want to upgrade to FF 34. The "Restart to Update" just do nothing.

Close and re-open the Firefox doesn't help.

Comment 23

[Miha Vrhovnik]

There is C:\Users\<User>\AppData\Local\Mozilla\updates\E7CF176E110C211B and the files dated in that directory are dated 2014-11-25. IMO, that's the date 33.1.1 was released.

If I remove that directory, and then go into about dialog.. it's starts to check for new updates, and then displays the Restart to update button, but nothing happens.
Looking at the update directory the subdir \E7CF176E110C211B is created however now it's empty.

Comment 24

[Michael]

(In reply to Miha Vrhovnik from comment #23)
> There is C:\Users\<User>\AppData\Local\Mozilla\updates\E7CF176E110C211B and
> the files dated in that directory are dated 2014-11-25. IMO, that's the date
> 33.1.1 was released.
> 
> If I remove that directory, and then go into about dialog.. it's starts to
> check for new updates, and then displays the Restart to update button, but
> nothing happens.
> Looking at the update directory the subdir \E7CF176E110C211B is created
> however now it's empty.

It seems to be the problem of the update server of Mozilla. No any update file is downloaded although the Firefox can detect the update exists. https://bugzilla.mozilla.org/show_bug.cgi?id=1035400#c17 also report that he/she can update again but doesn't said what have been done before.

Comment 25

[Charles]

Same problem here - Win7Pro 64bit, Firefox 33.1, Help > About says there is an update, offers 'Restart to update' button, pressing it does nothing...

Comment 26

[luuk34]

Can anyone explain why this bug is still set to 'NEEDINFO'?
What kind of info is needed?
I might be able to check if i can collect this info.......

Comment 27

[Gauthier Van Vreckem]

Firefox 33.1.1 Same problem, clicking on restart to update does nothing.

C:\Users\<User>\AppData\Local\Mozilla\updates\E7CF176E110C211B is there
active-update.xml remains with an empty node <updates />
Generating manually the update url from the app.update.url gives:
https://aus3.mozilla.org/update/3/Firefox/33.1.1/20141113143407/WINNT_x86-msvc/en-US/release/Windows_NT%206.1.1.0%20%28x64%29/default/default/update.xml?force=1
and both URL in the response gives a valid download of a .mar file with the right size.
This is probably not an update server problem.

Comment 28

[Adam Banks]

Same here. FF 33.1.1 to 34 ... can't update as "restart to update" doesn't do anything - nor has anything been downloaded/updated as a manual restart of FF doesn't go to 34 either.
:-(

Comment 29

[Miha Vrhovnik]

It updated on me today. Which seems that this really was an server issue? Aka missing update form 33.1.1? to 34.0.x?

Comment 30

[DarkShenron]

For those still having this problem i found a solution, do this,

1) Open appdata, Run=>appdata=>Enter.
2) Delete Local\Mozilla\updates, and rename Local\Mozilla and Roaming\Mozilla to Mozillabak.
3) Start firefox, try to update, CLOSE firefox when it starts downloading.
4) Copy Local\Mozilla\updates folder to someplace else.
5) Rename back Local\Mozillabak and Roaming\Mozillabak to Mozilla
6) Paste back updates folder copied in step 4 to Local\Mozilla\
7) Start firefox and update it should work now

Comment 31

[luuk34]

hmm, seven steps to remember.......
than this 1 step is shorter, and works too:
1) visit: https://www.mozilla.org/en-US/firefox/all/

The question remains why there is a button which does not work for what it was designed to do......

Comment 32

[DarkShenron]

(In reply to luuk34 from comment #31)
> hmm, seven steps to remember.......
> than this 1 step is shorter, and works too:
> 1) visit: https://www.mozilla.org/en-US/firefox/all/
> 
> The question remains why there is a button which does not work for what it
> was designed to do......

Most probably due to something corrupt in firefox data or settings....since it works as soon as we eliminate them.

Comment 33

[Hector Zhao [:hectorz]]

Attachment: Patch

Seems to be a regression from bug 600500.

When some extensions don't have compatible updates for new version of Firefox, clicking the button would open chrome://mozapps/content/update/updates.xul, but do nothing after bug 600500.

Comment 34

[Tom]

Happened on my 34 to 35.  Hasn't happened since my 32 to 33 update so really hit and miss.

Comment 36

[:Felipe Gomes (needinfo for replies!)]

Comment on attachment 8548764 [details] [diff] [review]
Patch

Review of attachment 8548764 [details] [diff] [review]:
-----------------------------------------------------------------

Looks right to me, but I'll let Robert double check

Comment 37

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

Comment on attachment 8548764 [details] [diff] [review]
Patch

LGTM and thanks!

Comment 38

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

[Tracking Requested - why for this release]:
This prevents users from manually updating when the full update ui needs to be displayed (e.g. incompatible add-ons).

Comment 39

[Hector Zhao [:hectorz]]

Thanks! I pushed this to try and will request checkin later:

https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=d984aae2e178

Comment 40

[Hector Zhao [:hectorz]]

(In reply to Hector Zhao [:hectorz] from comment #39)
> 
> https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=d984aae2e178

Comment 41

[[Back July 11] Ryan VanderMeulen]

https://hg.mozilla.org/integration/fx-team/rev/a9240b1eb2fb

Any way to test this?

Comment 42

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

(In reply to Ryan VanderMeulen [:RyanVM UTC-5] from comment #41)
> https://hg.mozilla.org/integration/fx-team/rev/a9240b1eb2fb
> 
> Any way to test this?
Per Bug 1100346 comment #17 tests are being created though I don't know if it is for this scenario. Ideally I'd be given time to work on bug 599574 which would include tests but I have been told other work is a higher priority.

Comment 43

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

https://hg.mozilla.org/mozilla-central/rev/a9240b1eb2fb

Comment 46

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

Note: this bug is actually in the Firefox about window code so fixing component

Comment 48

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

Comment on attachment 8548764 [details] [diff] [review]
Patch

Approval Request Comment
[Feature/regressing bug #]: Bug 600500
[User impact if declined]: This prevents users from manually updating when the full update ui needs to be displayed (e.g. incompatible add-ons).
[Describe test coverage new/current, TreeHerder]: Manually tested
[Risks and why]: Minimal. The change is for a code path that is currently broken so it definitely shouldn't make things worse and the manual testing shows that it fixes this bug.
[String/UUID change made/needed]: None

Comment 49

[Sylvestre Ledru [:Sylvestre]]

I experienced the bug myself and it is a pain... Tracking.

Comment 50

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

Pushed to mozilla-aurora
https://hg.mozilla.org/releases/mozilla-aurora/rev/f736f5e92126

Pushed to mozilla-beta
https://hg.mozilla.org/releases/mozilla-beta/rev/8a2a86c11f7c

Comment 51

[Hector Zhao [:hectorz]]

Is it possible to take this in Fx 35.0.1? For users already on Fx 35.0, they will no longer be affected when they upgrade from Fx 35.0.1+ to 36.0.

Comment 52

[Sylvestre Ledru [:Sylvestre]]

Hector, can this wait for 36?
We have this bug for a while and 35.0.1 is currently building.

Comment 53

[Hector Zhao [:hectorz]]

(In reply to Sylvestre Ledru [:sylvestre] from comment #52)
> Hector, can this wait for 36?
> We have this bug for a while and 35.0.1 is currently building.

This bug will not affect users during a minor version update, release it with Fx 35.0.1 will have the benefit of fixing the bug silently for users currently on Fx 35.0, users on Fx 34 or earlier will still be affected.

So if there're enough users already upgraded to Fx 35.0, I think it's better to take this.

Comment 54

[Sylvestre Ledru [:Sylvestre]]

Since we have this bug since firefox 30, I am not sure to see the rush here. Anything changed?

Comment 55

[Hector Zhao [:hectorz]]

(In reply to Sylvestre Ledru [:sylvestre] from comment #54)
> Since we have this bug since firefox 30, I am not sure to see the rush here.
> Anything changed?

It's not urgent, but releasing this fix with a minor version update will reduce the numbers of affected users.

Without it in Fx 35.0.1, users with:
Fx 35.0 or earlier =(affected)=> Fx 35.0.1 =(affected)=> Fx 36.0

With it in Fx 35.0.1, users with:
Fx 35.0 =(same major version, not affected)=> Fx 35.0.1 =(fixed)=> Fx 36.0
Fx 34.0.5 or earlier =(affected)=> Fx 35.0.1 =(fixed)=> Fx 36.0

I understand this bug will not affect every user, so I'm not sure if the improvement is worth the effort of a build 2. Thanks for the consideration.