Closed Bug 1417060 Opened 7 years ago Closed 7 years ago

Firefox 54 an empty shell prior to 57 update

Categories

(Toolkit :: Application Update, defect)

All
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1397562

People

(Reporter: julie, Unassigned)

Details

Attachments

(2 files)

I brought up Firefox at 6:02 AM PST, expecting it to update to 57. What came up was an "empty shell". Almost not content, no bookmarks, no history, nothing. The tabs were confused - combo of rectangular and rounded corners. I went to preferences to make sure updates were enabled (they were), exited and came back in. Same result. I clicked on Firefox\About Firefox, and it updated to 56.0.2. At that point, my bookmarks re-appeared. Firefox\About Firefox then showed a button that says "Restart to update Firefox."
Attached image Firefox 54 before updating to 57.png (deleted) —
This is what Firefox looked like when I brought it up just after 57 was released.
After I restarted Firefox, the 57 update appeared.
To summarize, from my MacBook Pro running OS X 10.11.6: 1. I started with Firefox 54, which looked totally blank when I brought it up. It had overlapping rectangular and rounded corner tabs. (rounded corner tabs were transparent, with the blue rectangular ones showing up behind them). 2. I initiated the update by visiting Firefox\About Firefox. 3. It updated to 56.0.2 and my bookmarks and tabs re-appeared. 4. I re-visited Firefox\About Firefox and found the button that said ""Restart to update Firefox." 5. I exited Firefox, and when it came back up Photon appeared, and Firefox\About Firefox said I was on 57 (64 bit).
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:57.0) Gecko/20100101 Firefox/57.0 Firefox: 57.0a1, Build ID 20171112125346 I have not managed to reproduce the issue on Mac 10.11, Windows 10 x64 and Ubuntu 14.04 x64. I've installed Firefox 54, opened the browser on an older profile, updated it and I have not encountered any problems as the ones described in comment #3. Could you please provide us a copy of the "about:support" page to eliminate custom settings as a possible cause?
Component: Untriaged → Application Update
Flags: needinfo?(jmccracken)
OS: Unspecified → Mac OS X
Product: Firefox → Toolkit
Hardware: Unspecified → All
about:support from Julie McCracken's Firefox (post 57 update) Thanks for looking into what happened.
Flags: needinfo?(jmccracken) → needinfo?(marius.coman)
I've tried to install the add-ons from the provided "about:support" in order to reproduce the user environment more accurately, however I still have not managed to reproduce the issue. Robert, can you please give us your opinion regarding this issue?
Flags: needinfo?(marius.coman) → needinfo?(robert.strong.bugs)
I highly doubt that this issue is due to update since we restore the install to the previous state on failure. I have seen blank widgets due to add-ons in the past and since this affected 54 and the add-on changes included in 57 I suspect that is the cause. Julie, just to verify. You saw the issue in 54 and the issue went away when you updated to 57? Have you used 54 without this issue and then without updating you saw this issue with 54?
Flags: needinfo?(robert.strong.bugs) → needinfo?(jmccracken)
I've been on PTO the past couple weeks so apologize for this late response. To answer your question above - yes, I had used 54 without this issue and experienced it the morning Quantum came out (before it was updated). I had to know how to initiate the update. It didn't prompt me for it, even though I had updates enabled.
Flags: needinfo?(jmccracken) → needinfo?(robert.strong.bugs)
(In reply to Julie McCracken (:julie) from comment #8) > I've been on PTO the past couple weeks so apologize for this late response. > > To answer your question above - yes, I had used 54 without this issue and > experienced it the morning Quantum came out (before it was updated). This likely due to update staging which was disabled in Firefox 57 via bug 1397562. > I had > to know how to initiate the update. It didn't prompt me for it, even though > I had updates enabled. Clients aren't prompted to update immediately and for the vast majority of clients the update happens when they restart Firefox for other reasons. Since chances are this is fixed by disabling staged updates I'm resolving this as a dupe of bug 1397562. If you see this happen again please either comment in this bug or file a new bug. Thanks
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(robert.strong.bugs)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: