HBuild Identifier: https://hg.mozilla.org/releases/mozilla-release/rev/7f5abf95991bda0bc2b8e0d774a8866b726b312b Mozilla/5.0 (Windows NT 10.0; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0 ID:20160623154057 Reproducible: 100% Steps To reproduce: 1. Install Firefox47.0.1 and start 2. Help > About Firefox > Check for updates Actual Results: Firefox is up to date. Browser console log: GET XHR https://aus5.mozilla.org/update/3/Firefox/47.0.1/20160623154057/WINNT_x86-msvc-x64/en-US/release/Windows_NT%2010.0.0.0%20(x64)/default/default/update.xml And the url contents is as follows: <?xml version="1.0"?> <updates> </updates> Expected Results: Firefox49.0.1(or latest release build) should be available.

Unfortunately, this is expected in the current update scenario if you have websense installed or for some reason Firefox doesn't have the corresponding hotfix installed. Resolving as WONTFIX :/

(In reply to Rail Aliiev [:rail] from comment #1) > Unfortunately, this is expected in the current update scenario if you have > websense installed or for some reason Firefox doesn't have the corresponding > hotfix installed. Resolving as WONTFIX :/ Okay, That means: Firefox is ended. Firefox does not provide new update any more. BTW, I did not install websense and any hotfix.

In that case, A information and solutions to the user is required. I think "Firefox is up to date" is not enough information. And It makes the misunderstanding to the user. The messagi should be "Firefox has ended. Please uninstall Firefox, do not use again" instead "Firefox is up to date"

(In reply to Alice0775 White from comment #2) > (In reply to Rail Aliiev [:rail] from comment #1) > > Unfortunately, this is expected in the current update scenario if you have > > websense installed or for some reason Firefox doesn't have the corresponding > > hotfix installed. Resolving as WONTFIX :/ > > Okay, > That means: Firefox is ended. No, it's not. :) > Firefox does not provide new update any more. It does, not for everybody. Our current update rules are very conservative, and we are working on solutions. > BTW, I did not install websense and any hotfix. The hotfix is supposed to be installed by Firefox automatically, there is no install it. For some reason not everybody gets it.

(In reply to Rail Aliiev [:rail] from comment #1) > Unfortunately, this is expected in the current update scenario if you have > websense installed or for some reason Firefox doesn't have the corresponding > hotfix installed. Resolving as WONTFIX :/ FWIW, what in comment #0 gives you the information that this even *is* the Websense case?

(In reply to Robert Kaiser from comment #6) > (In reply to Rail Aliiev [:rail] from comment #1) > > Unfortunately, this is expected in the current update scenario if you have > > websense installed or for some reason Firefox doesn't have the corresponding > > hotfix installed. Resolving as WONTFIX :/ > > FWIW, what in comment #0 gives you the information that this even *is* the > Websense case? From bug 1298404: > If WebSense is not present, add "(nowebsense)" directly after "%OS_VERSION%" to the default value of the app.update.url pref > > * New value will be https://aus5.mozilla.org/update/6/%PRODUCT%/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%(nowebsense)/%SYSTEM_CAPABILITIES%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml > > If WebSense is present, add "(websense)" The hotfix is not installed on Alice's Firefox for some reason (bug 1305787), so we're not updating out of prudence.

We're planning to update people gradually. The hotfix has installed for many people now. Since it didn't work for some people, we'd like to figure out why. Alice, since you can reproduce this state, I wonder if you can help us figure out why this is happening. Did you just notice recently that 47.0.1 didn't update? Or is this a new install? Felipe, can you describe some of how the system update should work? Maybe this will help us diagnose an issue.

I think we are close to relaxing the temporary update restriction, and updating more 47.0.1 users this week.

(In reply to Liz Henry (:lizzard) (needinfo? me) from comment #8) > We're planning to update people gradually. The hotfix has installed for many > people now. Since it didn't work for some people, we'd like to figure out > why. > > Alice, since you can reproduce this state, I wonder if you can help us > figure out why this is happening. > Did you just notice recently that 47.0.1 didn't update? Or is this a new > install? > New Install. Restart several times for about 12hr(I do not know exactly), It updated to 48.0.1(I do not know exactly). And then restart again It updated to 49.0.1. Seems, It seems to take a long time to get the hotfix. I think the hotfix should get at the time of every checking updates. Anyway, "Firefox is up to date" is definitely wrong information. It should be a more meaningful description and should provide a link to the valid latest version.

(In reply to Liz Henry (:lizzard) (needinfo? me) from comment #8) > ...since you can reproduce this state, I wonder if you can help us > figure out why this is happening. I can reproduce the state on Win 7 32 bit, old install. I have seen the issue of not updating from 47.0.1 on more than one system. Win 7 and Win 10, 32 and 64 bit. Those systems never had anything to do with websense. Do not agree with "RESOLVED DUPLICATE of bug 1305787" status. Even if websense presence will be fixed in future builds, how old installs will benefit of this and get out of update deadlock? What info is needed from not updating system to debug?

Let me try to clarify things: We have not stopped providing updates to Firefox. The issue is that we can only provide updates to users who don't have WebSense installed, and in order to detect that we shipped a hotfix and a system add-on, which are published through the "add-ons update check" that happens once a day, and not the "firefox update check" that happens (on a timer too) and when opening the About window. There are two different issues that are being mixed here: 1 - Alice wasn't seeing the Firefox update because of running a fresh install, and probably not having enough time to hit the once-a-day check for add-on updates. After understanding that, the comment is that the text "Firefox is up to date" is measleading, which is true. We cannot fix that retroactively, but that is a valid request for enhancement for future versions, and maybe this bug should be morphed into that. E.g.: for users who didn't have either "(websense)" or "(nowebsense)", Balrog could publish some meta-data that makes Firefox use the "manual update text" 2 - J.Will is reporting not seeing the updates either. It can be because of the same reason (not enough time to receive the hotfix), but if he is reporting that is a daily used Firefox install, we can investigate why his system is not receiving the hotfix. That is what is being tracked by bug 1305787. J.Will, question: In Preferences > Advanced > Update, have you changed it from the default ("Automatically install updates") to something else?

(In reply to :Felipe Gomes (needinfo me!) from comment #12) > J.Will, question: In Preferences > Advanced > Update, have you changed it > from the default ("Automatically install updates") to something else? Yes, automatic updates are turned off (set to "never check for updates") > published through the "add-ons update check" that happens once a day, and > not the "firefox update check" that happens (on a timer too) and when > opening the About window. Is there a way to manually run mentioned "add-ons update check"? I tried to run "check for updates" in "about:addons", also noticed "Update Add-ons automatically" was/is ticked there, still not updating. Just look at it from average user use case - he/she run Help > About Firefox, checked for update. Got a message "You are on the latest version", happy days! The issue is that problem is hidden. If user somehow realizes the problem is present - the simplest solution is just to download and run full install with the latest version. It is what I did on the systems which are used daily. The test system in question I can run tests on is not used daily.