Closed
Bug 1051223
Opened 10 years ago
Closed 10 years ago
Updater installs Mozilla Maintenance Service without consent
Categories
(Toolkit :: Application Update, defect)
Tracking
()
RESOLVED
FIXED
mozilla36
People
(Reporter: krystian4842, Assigned: bbondy)
References
Details
Attachments
(1 file)
3.21 KB,
patch
|
robert.strong.bugs
:
review+
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.125 Safari/537.36 Steps to reproduce: I installed Firefox without Mozilla Maintenance Service. Actual results: When an update for Firefox came and updater ran it installed Mozilla Maintenance Service. Expected results: Updater shouldn't install Mozilla Maintenance Service when I didn't choose it in the installer for Firefox.
Comment 1•10 years ago
|
||
Is "Use a background service to install updates" in Options > Advanced > Update also checked?
Flags: needinfo?(krystian4842)
Comment 4•10 years ago
|
||
What is the value (true/false) of "app.update.service.enabled" when you search for it in about:config?
It's "true". I forgot to add that I've uninstalled Mozilla Maintenance Service when the updater installed it.
Assignee | ||
Comment 7•10 years ago
|
||
Did you install with the stub installer or the full installer originally? I believe that we set an entry in the registry when it is specifically checked off on install, and on update it won't install it if that registry entry is set. Perhaps this entry isn't being set correctly for the stub installer or something like that though.
Assignee: nobody → netzen
I installed Firefox through stub installer with unchecking the Mozilla Maintenance Service.
Assignee | ||
Updated•10 years ago
|
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Assignee | ||
Comment 9•10 years ago
|
||
This sets the "Attempted" reg value so that new upgrades won't try to install the service. Tested locally and it's working. Pave over installs with checkbox on will still install it.
Attachment #8496668 -
Flags: review?(robert.strong.bugs)
Comment 10•10 years ago
|
||
Did you figure out what changed to make this happen?
Assignee | ||
Comment 11•10 years ago
|
||
No I looked back at blame history but I couldn't find a reason. I'm wondering if we just missed this case originally. I thought we had this working at some point but I couldn't find a reason within a reasonable time frame. This is the right fix IMHO though.
Updated•10 years ago
|
Attachment #8496668 -
Flags: review?(robert.strong.bugs) → review+
Assignee | ||
Comment 12•10 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/2fd40580507b
Target Milestone: --- → mozilla36
Comment 13•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/2fd40580507b
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•