Closed
Bug 1161370
Opened 10 years ago
Closed 10 years ago
restart buttons not functioning on software update dialog
Categories
(Toolkit :: Application Update, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: chofmann, Unassigned)
Details
Attachments
(1 file)
|
24.74 KB,
image/png
|
Details |
I think I'm tracking pretty close to latest 38 betas...
the first time I saw this last week I thought it might be a fluke and ignored, but seems it's happened two times now.
After prompted to update I accept the download and updating and after the install happens I get the software update dialog
"Update ready to install
The updates will be installed the next time firefox starts. You can restart now or continue working and install later."
plus the two buttons "Restart Later" and "Restart Firefox"
neither of the buttons are funtional. Clicking on them gets not response in terms of the buttons getting focus, or intiating the restart, or dismissing the update dialog.
about: tells me...
Build identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:38.0) Gecko/20100101 Firefox/38.0
Comment 1•10 years ago
|
||
Hmmm... there are tests for the Restart Later button though there isn't for the Restart button since that would terminate tests. I also run this ui periodically (last week) to verify they work and haven't experienced any issues.
Please set the app.update.log preference to true and the devtools.errorconsole.enabled to true. The next time you see this open the error console under tools -> web developer. Paste any messages that start with AUS:UI in this bug.
Updated•10 years ago
|
Component: Installer → Application Update
Product: Firefox → Toolkit
| Reporter | ||
Comment 2•10 years ago
|
||
ok, devtools.errorconsole.enabled set to true and I'll watch on the next update.
One extra bit of information is that I'm running the update with lots of windows and tabs running for a while and there is general, but not severe, perf degradation across all windows. by not severe I'm meaning that other browser windows can be scrolled, moved around, etc... but response is sometimes sluggish and see the occasional beachball.
I was able to hit the quit button on the the dialog to dismiss, then restarted ok.
Comment 3•10 years ago
|
||
The restart button hands off the request to restart just as other restart code (e.g. the add-ons mgr, Help -> Restart with add-ons disabled, etc.) and shouldn't make any more difference for the app update ui as it does for any of these other places where restarting occurs. Do those restart buttons, menuitems, etc. work for you?
| Reporter | ||
Comment 4•10 years ago
|
||
"Firefox | Quit Firefox" worked.
I'll check "Help | Restart with Addons disabled" when I get the next update.
Comment 5•10 years ago
|
||
Thanks though quit doesn't use the same code path as restart.
Comment 6•10 years ago
|
||
I just verified restart still works for me so more sleuthing will be needed.
| Reporter | ||
Comment 7•10 years ago
|
||
ok, back to the point where they update was prompted and has progressed to the point where I've been asked to restart.
I checked the error console and I think I saw this message
http://mxr.mozilla.org/mozilla-central/source/toolkit/mozapps/update/content/updates.js#1808
I tried to copy it, but now its seems like its gone from the log, and the paste didn't work...
maybe I cleared it from the log instead?
| Reporter | ||
Comment 8•10 years ago
|
||
but interestingly enough while the buttons on the "restart later/restart now" dialog seemed to be dead
help | restart with addons disabled
and the following dialog with options to restart with addons disabled or restart clean
seems to work.
Comment 9•10 years ago
|
||
Interesting. If you did see that message in the error console the code that follows is for all practical purposes the same as in the about dialog. If you see it again try to find that same message in the error console and any messages that seem to be applicable as well as error messages following it and paste them in this bug.
| Reporter | ||
Comment 11•10 years ago
|
||
I can't explain it but the problem seems to have gone away.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(chofmann)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•