Issue metadata
Sign in to add a comment
|
"--system-level" parameter is seen twice while installing Chrome. |
||||||||||||||||||||
Issue descriptionChrome Version: Across all Current serving Chrome versions OS: Windows 7 What steps will reproduce the problem? 1. Try to install Chrome from : https://www.google.com/chrome/browser/desktop/index.html https://www.chromium.org/getting-involved/dev-channel 2. open process explorer or task manager and observe the parameters whild Chrome getting installed. What is the expected result? There should be just one --system-level parameter. What happens instead? There are two --system-level parameters, Please find the screenshots for reference. Note : I am just tagging M57 for now, Since this is a server side Chrome milestone won't be that helpful anyways.
,
Feb 9 2017
--system-level was removed from the update configs yesterday, so this has been fixed. Sorin and Ganesh: I believe you're in the clear to remove the special-case in Omaha if you wish -- Chrome's installer (setup.exe) and mini_installer both sniff the "GoogleUpdateIsMachine" environment variable now.
,
Feb 9 2017
Hi Greg, who sets the "GoogleUpdateIsMachine"? I do not see Omaha setting it, nor code in Chromium.
,
Feb 10 2017
Responding directly. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by sorin@chromium.org
, Feb 8 2017