User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3 Build Identifier: Firefox/3.0.3 I use Firefox since several years (I started with F1.5). I pass to Firefox 3 since one mounth, and since a fortnight I often receive proposal to upgrade to Firefox 2.0.0.17. I think it is a small "administrative" bug. In addition how can I delete this "proposal" Reproducible: Always Steps to Reproduce: 1.Just wait few hours ! 2. 3. Except French dictionaries I don't use any add on

In my opinion this could be solve easily by adding : to the present proposals to upgrade to a new version, either "Now" or "Later", a third button "never".

I think this is related to Bug 458875, which I will mark as a dupe.

Firefox 3.0.5 upgraded via WPKG, in the help menu says it's downloading 2.0.0.14. Different computer but the same setup as bug 463170, unfortunately it didn't occur to me to check active-updates.xml before running Firefox - I'm logged in as the local admin which isn't used very often. So far no dialog has popped up offering the update.

Reporter, please open about:config in the url bar and type app.update.url. Then double click app.update.url and copy the value into a comment in this bug. Also, if app.update.url.override is present double click it and copy the value for it into the same comment. Thanks

James, can you provide an answer to comment #5?

OK, let's take this in stages. I'm logged in as local administrator on a machine that has has Firefox upgraded via WPKG to 3.0.7, but hasn't been run by this user since 3 February. Here's the app.update prefs from prefs.js: user_pref("app.update.lastUpdateTime.addon-background-update-timer", 1233646684); user_pref("app.update.lastUpdateTime.background-update-timer", 1233646684); user_pref("app.update.lastUpdateTime.blocklist-background-update-timer", 1233646684); user_pref("app.update.lastUpdateTime.microsummary-generator-update-timer", 1233646684); user_pref("app.update.lastUpdateTime.search-engine-update-timer", 1233646684); user_pref("app.update.never.2.0.0.6", false);

It isn't in your prefs.js file. Please do the following: (In reply to comment #5) > Reporter, please open about:config in the url bar and type app.update.url. Then > double click app.update.url and copy the value into a comment in this bug. > Also, if app.update.url.override is present double click it and copy the value > for it into the same comment. Thanks

Yes, I just wanted to capture the state of upgraded via WPKG but not yet run since the upgrade. updates.xml is also present in Local Settings etc. but dated 27/06/2008. app.update.url is https://aus2.mozilla.org/update/3/%PRODUCT%/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml and there's no app.url.override.

That is actually the Firefox installer's install.log and not from WPKG though WPKG might be launching our installer. Did you run the installer as the same user as has the attached active-update.xml? It does some cleanup but won't be able to cleanup other accounts. btw1: There has been at least one change that has landed for 3.5 that will prevent updating to older versions. btw2: if you aren't going to use App update and instead use WPKG to update you can also disable App update under Tools -> Options -> Advanced -> Update.

On starting Firefox, the Help menu had "Downloading Firefox 2.0.0.14" again which brings up a dialog showing progress. No proxy is set in the profile.

WPKG runs as the SYSTEM user, so not the same as has the attached active-update.xml. WPKG just runs '"Firefox Setup 3.0.7.exe" -ms'. The upgrade completed, and now Firefox crashes on startup, even in safe mode. My guess is that if Firefox 3.0 is in the middle of an upgrade, it'll continue that upgrade on restart instead of fetching the latest updates.xml and processing that. It's not a issue for most of our users, since they don't have admin privileges.

I've re-run WPKG and it's installed 3.0.7 with no problems, and Help/Check for Updates... reports no updates available. In Local Settings etc., active-updates.xml is an empty xml file, and updates.xml looks to be the same with the 2.0.0.14 and 2.0.0.10 updates.

This adds protection against resuming a download for an older version. notes: a) bug 313057 added a version check before trying to update. b) The reason the installer wasn't able to remove the files that caused the download of an older version of Firefox is because a different user than the one installing Firefox had an update download already in progress. This will be fixed as part of bug 485113.

btw: bug 313057 was not approved for Firefox 3.0.x which is why it didn't protect against applying the old update.

I think it makes more sense to add the protection against resuming a download for an older version in bug 353804 which this appears to be a dupe of.