37 ms·

We have stopped pushing the affected version of Keystone, so if your computer has not been broken yet, it won't be. If it has been broken but not rebooted:

We have stopped pushing the affected version of Keystone, so if your computer has not been broken yet, it won't be. If it has been broken but not rebooted: sudo rm -rf /Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle sudo ln /private/var /var should fix it. That deletes Keystone and fixes the symlink. If it has been rebooted, these commands at a recovery console should repair the computer. Chrome will subsequently ask for admin credentials to reinstall the updater next time you run it. This will not re-break the computer; the version of Keystone bundled with Chrome is older, and we have stopped serving the version affected by this issue.

im3w1l 7y ago
Please don't run that command as stated. It deletes /var (because HN merged adjacent lines) Edit: It has since been fixed.
- saagarjha 7y ago
  I won't, don't worry ;) That code should probably be indented two spaces, like this: sudo rm -rf /Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle sudo ln /private/var /var
  - norberg 7y ago
    yikes! thanks, fixed.
    - akie 7y ago
      I see a pattern here...
      - Thorrez 7y ago
        I doubt Hacker News automatically merging 2 lines into 1 line was the cause of the original bug.
        J5892 7y ago
        You don't run your code through HN as a post-commit hook?
- norberg 7y ago
  yikes! thanks, fixed.