Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Update process bypasses all user input

  • 2 replies
  • 1 has this problem
  • 4 views
  • Paskiausią atsakymą parašė Matt Brubeck

more options

Just "checked" for an update to Firefox 12. This "check" downloaded the update using an unknown name and to an unknown location, bypassing the designated download folder and making it impossible to find. It then proceeded to install without first asking if that's what I wanted. This process could only be terminated with a force quit, which was done. Upon relaunch, the update installed without asking if that was desired. This is nonsense. I very much don't appreciate folks at Mozilla.org taking away my decisions just because that makes their life a bit more convenient. The update option should do the following, and Mozilla .org should not have to be told this.

1a.) Inform the user that this process involves automatic download and installation, with no opportunity for user input, and provide a "cancel" option.

OR:

1b.) Provide an option for manual download of the dmg file to the designated download folder using a logical filename-- like, with "Firefox" as part of the name. This option should include the opportunity to manually install the download at a later time, rather than forcing it on the user's throat with no opportunity to control the process.

2.) This update protocol should emphatically not conceal the download using an unknown name in an unknown location. This is disrespectful of prerogatives that belong to the user, and not to Mozilla.org.

So could someone please tell me how these downloads are named, and where Firefox places them?

Thanks.

Just "checked" for an update to Firefox 12. This "check" downloaded the update using an unknown name and to an unknown location, bypassing the designated download folder and making it impossible to find. It then proceeded to install without first asking if that's what I wanted. This process could only be terminated with a force quit, which was done. Upon relaunch, the update installed without asking if that was desired. This is nonsense. I very much don't appreciate folks at Mozilla.org taking away my decisions just because that makes their life a bit more convenient. The update option should do the following, and Mozilla .org should not have to be told this. 1a.) Inform the user that this process involves automatic download and installation, with no opportunity for user input, and provide a "cancel" option. OR: 1b.) Provide an option for manual download of the dmg file to the designated download folder using a logical filename-- like, with "Firefox" as part of the name. This option should include the opportunity to manually install the download at a later time, rather than forcing it on the user's throat with no opportunity to control the process. 2.) This update protocol should emphatically not conceal the download using an unknown name in an unknown location. This is disrespectful of prerogatives that belong to the user, and not to Mozilla.org. So could someone please tell me how these downloads are named, and where Firefox places them? Thanks.

All Replies (2)

more options

Sorry about that; that indeed sounds like a bug in the Firefox update system. I agree that "Check for updates" should prompt before installing the update. I'll make sure there's a bug on file about that.

The automated updated downloads a ".mar" file to a temporary directory. These .mar files are only used for automatic updates; there's no way to install them manually. If you prefer to update Firefox manually, then you should instead go to http://mozilla.org/firefox to download and install the latest version.

(Note: Mozilla strongly recommends having Firefox keep itself up to date automatically, since updates contain security fixes that are important for keeping your computer and your browser secure.)

more options

This has been reported to Mozilla as bug https://bugzilla.mozilla.org/show_bug.cgi?id=600500