Detect outdated system Keystone |
|||
Issue descriptionChrome Version : 54.0.2840.71 OS version : 10.11 What steps will reproduce the problem? (1) Start Chrome with a broken, old system install of Keystone (2) Launch Chrome (bundled with newer version of Keystone) What is the expected result? A warning to the user that Chrome may not be able to update itself and a button to fix it. This already happens if a system ticket is found without Keystone. It should also happen if an outdated Keystone is present. What happens instead? No warning displayed. I just worked with a couple of users in that state. Possibly an older version of Keystone - 1.2.2.428 had lower success rate of system installs and ended up with non-functional installation.
,
Nov 10 2016
,
May 8 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/b8064914cafec9166c25773ec203542a9c08c6bf commit b8064914cafec9166c25773ec203542a9c08c6bf Author: Boris Vidolov <borisv@chromium.org> Date: Tue May 08 02:11:07 2018 Check system Keystone version to offer recovery in the UI when system Keystone is broken. Refactored a bit KeystoneGlue implementation. Added unit tests. Bug: 658993 Change-Id: I16870fc37e1f71772848240f0ae397d6aa13b2e5 Reviewed-on: https://chromium-review.googlesource.com/1044527 Commit-Queue: Boris Vidolov <borisv@chromium.org> Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#556647} [modify] https://crrev.com/b8064914cafec9166c25773ec203542a9c08c6bf/chrome/browser/mac/keystone_glue.mm [modify] https://crrev.com/b8064914cafec9166c25773ec203542a9c08c6bf/chrome/browser/mac/keystone_glue_unittest.mm
,
May 8 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by patricia...@chromium.org
, Nov 8 2016