Closed Bug 755880 Opened 13 years ago Closed 13 years ago

Drag down from help to about; checking for updates just sits there.

Categories

(Toolkit :: Application Update, defect)

15 Branch
x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: grgoffe, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/15.0 Firefox/15.0a1 Build ID: 20120516030515 Steps to reproduce: From the help menu, drag down and release on "About Nightly". Actual results: I got a popup that says "Checking for updates". After a few minutes of no apparent activity, I killed the popup. Subsequent retries produced "Nightly is up to date". Expected results: The check for updates should either find updates or NOT and say so.
Are you able to reproduce this or did it just happen once? The build you reported was the latest version on the day you reported this so I would expect it to find no updates. Note that updates are served in part on a network of community provided mirrors. Sometimes you will hit a slow mirror which could result in it taking longer than normal to check for updates.
Component: Untriaged → Application Update
Product: Firefox → Toolkit
QA Contact: untriaged → application.update
Anthony, Thanks for your response to this ticket. I seem to be able to recreate this problem as follows: 1) I have 6 or 7 windows open and poke the "software update" popup. This works well I think. 2) after 24 hours or so, I drag down help and release on the "About Nightly" action. This comes up with "connecting...". I believe that this situation is not going to end by itself. Do you need more information? Regards, George...
I just tried this with Firefox 15.0a1 2012-05-14 and it found an update to Firefox 15.0a1 2012-05-19 no problem. Is this happening for you every day? Can you edit your about:config and change "app.update.log" to true, then restart Firefox and copy what appears in error console when you check for updates into a text file and attach it to this bug?
Anthony, I will do this right now. Typically, the problem appears when I pull down the help menu holder AFTER a popup "software update" is implemented. Thanks, George...
Anthony, I just checked this boolean and it's set to true now. I'll try to find the error console since I have not seen one. Regards, George...
You can find the Error Console under the Tools > Web Developer menu.
Anthony, I have the error console now. I don't see any way to save the contents. Only "All" and "Warnings" have anything in them. I suspect that if I try to use the "About" method to check for updates now it will show this error. Do you have anything special you'd like me to do now? Regards, George...
You'll have to copy and paste each item by right clicking on it. As I said, I cannot reproduce this problem locally. Does this happen every time you try to update? If not, I'm less concerned about this issue. One more thing you can try...does it happen if you use a new profile? http://kb.mozillazine.org/Profile_Manager#Linux
Anthony, I have several profiles that I use for just this kind of testing. I'll give it a try and report here. Thanks, George...
Well, I actually want you to create a brand new profile from scratch. I want to remove any and all existing profile data from the equation.
Anthony, Ok. I created a new profile and updated about:config for the app.update.log and tried the About method. It paused and then succeeded. I'll have to keep this profile active until a new update appears at which time I'll try again. Do you know how to force the popup "software update"? Removing an update file perhaps? Regards, George...
You can adjust your timers to make the ping to the update servers happen more often, but there is no way to strictly force it. app.update.idletime = 0 app.update.interval = 10 app.update.download.backgroundInterval = 0
Anthony, Thanks. I'll have to wait for the build people to push a new build. It'll probably be tomorrow. Thanks for your help. George...
Anthony, I applied the new "software update" with the new profile. It worked fine. Then I tried the "about" method. It seemed to work fine as well. I went back to the old profile with various plugins active and the problem re-appeared. I'm sitting at the "Checking for updates" popup now. Sigh. I suppose a search composed of 1) disabling a plugin, 2) testing if the problem still exists, could work. Do you have a better idea? Regards, George...
Anthony, I just killed the popup and tried "About" again... It came right back that Nightly is up to date. Does this give you any clues? Regards, George... I also get these messages from Nightly. Do they mean anything to you? George... *** AUS:SVC getLocale - getting locale from file: resource://app/update.locale, locale: en-US *** AUS:SVC Checker:getUpdateURL - update URL: https://aus3.mozilla.org/update/3/Firefox/15.0a1/20120520030530/Linux_x86_64-gcc3/en-US/nightly/Linux%203.3.5-2.fc16.x86_64%20(GTK%202.24.8)/default/default/update.xml?force=1 *** AUS:SVC gCanCheckForUpdates - able to check for updates *** AUS:SVC Checker:checkForUpdates - sending request to: https://aus3.mozilla.org/update/3/Firefox/15.0a1/20120520030530/Linux_x86_64-gcc3/en-US/nightly/Linux%203.3.5-2.fc16.x86_64%20(GTK%202.24.8)/default/default/update.xml?force=1 *** AUS:SVC Checker:getUpdateURL - update URL: https://aus3.mozilla.org/update/3/Firefox/15.0a1/20120520030530/Linux_x86_64-gcc3/en-US/nightly/Linux%203.3.5-2.fc16.x86_64%20(GTK%202.24.8)/default/default/update.xml *** AUS:SVC Checker:checkForUpdates - sending request to: https://aus3.mozilla.org/update/3/Firefox/15.0a1/20120520030530/Linux_x86_64-gcc3/en-US/nightly/Linux%203.3.5-2.fc16.x86_64%20(GTK%202.24.8)/default/default/update.xml *** UTM:SVC TimerManager:notify - notified @mozilla.org/updates/update-service;1 *** AUS:SVC Checker:onProgress - 42/42 *** AUS:SVC Checker:onLoad - request completed downloading document *** AUS:SVC Checker:onLoad - number of updates available: 0 *** AUS:SVC UpdateService:removeDownloadListener - no downloader! *** AUS:SVC Checker:getUpdateURL - update URL: https://aus3.mozilla.org/update/3/Firefox/15.0a1/20120520030530/Linux_x86_64-gcc3/en-US/nightly/Linux%203.3.5-2.fc16.x86_64%20(GTK%202.24.8)/default/default/update.xml?force=1 *** AUS:SVC Checker:checkForUpdates - sending request to: https://aus3.mozilla.org/update/3/Firefox/15.0a1/20120520030530/Linux_x86_64-gcc3/en-US/nightly/Linux%203.3.5-2.fc16.x86_64%20(GTK%202.24.8)/default/default/update.xml?force=1 *** AUS:SVC Checker:onProgress - 42/42 *** AUS:SVC Checker:onLoad - request completed downloading document *** AUS:SVC Checker:onLoad - number of updates available: 0 *** AUS:SVC UpdateService:removeDownloadListener - no downloader! *** AUS:SVC Checker:getUpdateURL - update URL: https://aus3.mozilla.org/update/3/Firefox/15.0a1/20120520030530/Linux_x86_64-gcc3/en-US/nightly/Linux%203.3.5-2.fc16.x86_64%20(GTK%202.24.8)/default/default/update.xml?force=1 *** AUS:SVC Checker:checkForUpdates - sending request to: https://aus3.mozilla.org/update/3/Firefox/15.0a1/20120520030530/Linux_x86_64-gcc3/en-US/nightly/Linux%203.3.5-2.fc16.x86_64%20(GTK%202.24.8)/default/default/update.xml?force=1 *** AUS:SVC Checker:onProgress - 42/42 *** AUS:SVC Checker:onLoad - request completed downloading document *** AUS:SVC Checker:onLoad - number of updates available: 0 *** AUS:SVC UpdateService:removeDownloadListener - no downloader!
Robert, Although not definitive, I did the help -> "restart with add-ons disabled" and then did an update. There was a pause which I think was "normal" and then the update succeeded. Here's a small jpeg that shows what add-ons I have running. Regards, George...
My best recommendation would be to start with all addons disabled and then enable them one by one until the issue reproduces again.
Robert, I have not seen this problem since my last post to this bug. Someone magically fixed it? Regards, George...
(In reply to George R. Goffe from comment #19) Quite possibly and thanks... resolving ->wfm
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: