Issue metadata
Sign in to add a comment
|
Error 12 - Chrome updates haven't been working for months, if not longer
Reported by
clifford...@gmail.com,
Jan 6 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.98 Safari/537.36 Steps to reproduce the problem: I don't know if it's been summer 2015 (that's a long time ago), but I know my issue has been at least months... I'm currently on OS X Sierra 10.12.2 and Chrome 54.0.2840.98 after doing a Time Machine backup and a manual re-install of Chrome several months back. I installed https://www.google.com/dl/release2/5b/auto/GoogleSoftwareUpdate-1.2.6.1370.dmg and ejected the virtual disk after completing the install. I didn't find anything in Applications but I visited chrome://help/ and got the same error 12 and same error message: 2017-01-05 09:50:22.865 GoogleSoftwareUpdateAgent[2773/0x700001aaa000] [lvl=3] -[KSAgentApp(KeystoneThread) runKeystonesInThreadWithArg:] Failed to connect to system update engine from the system agent. 2017-01-05 09:50:22.867 GoogleSoftwareUpdateAgent[2773/0x700001aaa000] [lvl=3] -[KSUpdateEngine updateProductID:] KSUpdateEngine no ticket to update for the specified product ID. (productID: com.google.Chrome) [com.google.UpdateEngine.CoreErrorDomain:3003] I'll try closing Chrome and possibly restarting my iMac and report back... Neither restarting Chrome nor restarting iMac did the trick. FYI: I understand I have error 12 and not error 11, but I got here from https://productforums.google.com/forum/#!topic/chrome/kE6kmXOgfjU The issue's been persisting for so many months that I thought I'd give this a try. :( What is the expected behavior? What went wrong? Cannot update Did this work before? Yes Unknown Chrome version: 54.0.2840.98 Channel: n/a OS Version: OS X 10.12.2 Flash Version: Shockwave Flash 24.0 r0 From https://bugs.chromium.org/p/chromium/issues/detail?id=520135#c215
,
Jan 6 2017
,
Jan 11 2017
Clifford, have you got chance to try the suggestion above?
,
Jan 11 2017
Hey, great, thanks! Version 55.0.2883.95 (64-bit) Google Chrome is up to date. I’m so appreciative!!! ᐧ
,
Jan 12 2017
Thank you, Clifford. Hopefully, your follow ups will help other who get into this situation and if we see more cases, we may add a help page.
,
Jan 12 2017
I am resolving as "won't fix", as the issue seem to arose either from incomplete machine restore or older updater installed - the new one seem to work. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by borisv@chromium.org
, Jan 6 2017