Browser not up to date
Reported by
nny...@gmail.com,
Jan 3 2017
|
||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2970.0 Safari/537.36 Steps to reproduce the problem: 1. Stop showing the warning 2. 3. What is the expected behavior? What went wrong? Browser not up to date, but it actually is Did this work before? N/A Chrome version: 57.0.2970.0 Channel: canary OS Version: OS X 10.11.6 Flash Version:
,
Jan 3 2017
borisv@, IIRC from threads you may have some insight into failed updater issues. Could you forward to the appropriate people (there doesn't appear to be an "autoupdate" component).
,
Jan 3 2017
This is somewhat unusual. We used to have a version of the updater that would not report an error when it cannot reach the auto-update server. To be sure, can open Terminal application, copy/paste the command below and press enter? Then send the generated .zip file to borisv@chromium.org for me to check the results? ~/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/ksdiagnostics
,
Jan 3 2017
,
Jan 4 2017
,
Jan 6 2017
nnylzx@: Could you please update the thread as per C#3.
,
Jan 7 2017
no more bugs. sorry and thank you for the trouble.
,
Jan 9 2017
As per Comment#7, marking this issue as WontFix. Please feel to free to log a new defect once you face the issue again. Thank you.
,
Jan 16 2017
The core issue is which is correct: 'Out of date' or 'Up to date', which is not clear as stated; always difficult for Canary and depends on time of day.. See issue 662228 for active follow up. |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by ccameron@chromium.org
, Jan 3 2017356 KB
356 KB View Download