Chrome Updater doesn't work
Reported by
denniske...@gmail.com,
Sep 4 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/603.3.8 (KHTML, like Gecko) Version/10.1.2 Safari/603.3.8 Steps to reproduce the problem: 1. Open Chrome 2. Under Help > About in the settings it tries to fetch updates (and finds one) then the following error is displayed. What is the expected behavior? Chrome downloads & installs the most recent version. What went wrong? * The following error lines are displayed: https://t.co/oYyEv5qmxT * Chrome does not update Did this work before? N/A Chrome version: 59.0.3071.86 Channel: stable OS Version: OS X 10.12.6 Flash Version: If my Chrome is up to date it doesn't display any errors which makes is hard to debug this problem. Because the first answer I get is always: Update to the latest version... which I've done a thousand times in the last two years. I have also tried all suggestions under https://t.co/jCGUoVjoe5 several times as mentioned in these tweets https://twitter.com/wottpal/status/893053426267033602 with @googlechrome.
,
Sep 12 2017
This looks similar to Issue 752353 and is probably fixed in the latest stable(61.0.3163.79). @ denniskerzig:Could you please un-install chrome and install latest version from https://www.chromium.org/getting-involved/dev-channel and check whether issue reproduces or not. Thanks!
,
Sep 12 2017
I am on the latest dev-build now and can confirm (or not) if it works when the next update is pushed. On 12. Sep. 2017, 14:19 +0200, sc00335… via monorail <monorail+v2.3058424708@chromium.org>, wrote:
,
Sep 12 2017
Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 13 2017
,
Sep 14 2017
Can’t confirm the fix. Still displays the following error message after Chrome has found an update which it wants to install: 2017-09-14 14:04:34.337 GoogleSoftwareUpdateAgent[913/0x700006174000] [lvl=3] -[KSAgentApp(KeystoneThread) runKeystonesInThreadWithArg:] Failed to connect to system update engine from the system agent. 2017-09-14 14:04:34.343 GoogleSoftwareUpdateAgent[913/0x700006174000] [lvl=3] +[KSProductsCountingMetricsStore verifyCountingMetrics:error:] Unrecognized key in counting metrics: ProductState 2017-09-14 14:04:34.345 GoogleSoftwareUpdateAgent[913/0x700006174000] [lvl=3] -[KSUpdateEngine updateProductID:] KSUpdateEngine no ticket to update for the specified product ID. (productID: com.google.Chrome) [com.google.UpdateEngine.CoreErrorDomain:3003] 2017-09-14 14:04:34.348 GoogleSoftwareUpdateAgent[913/0x700006174000] [lvl=3] +[KSProductsCountingMetricsStore verifyCountingMetrics:error:] Unrecognized key in counting metrics: ProductState On 13. Sep. 2017, 22:44 +0200, erikc… via monorail <monorail+v2.3185994615@chromium.org>, wrote:
,
Sep 15 2017
I am afraid that the system version of GoogleSoftwareUpdate (the updater) is now in broken state and since it is installed as root, the Chrome cannot change it. For your specific machine, the solution is to install latest updater from here: https://dl.google.com/mac/install/googlesoftwareupdate.dmg. Please try this and let us know if it fixes the problem. In general, if newer updater gets into this state, it reports to the user how to recover, but your version is from before we added that change.
,
Oct 30 2017
The latest version of the update does additional steps to ensure that the updater daemon is not disabled. I am marking this bug as fixed for now. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by meh...@chromium.org
, Sep 4 2017