<story><title>Google Chrome Keystone is modifying /var symlink on non SIP Macs causing k-panic</title><url>https://mrmacintosh.com/google-chrome-keystone-is-modifying-var-symlink-on-non-sip-macs-causing-boot-issues/</url></story><parent_chain><item><author>norberg</author><text>Hey. Google Keystone tech lead here. We are aware of the issue, and we&amp;#x27;ve stopped the release. We&amp;#x27;re building a replacement that fixes the problem. In the meantime, to fix affected machines:&lt;p&gt;&lt;pre&gt;&lt;code&gt;  sudo rm -rf &amp;#x2F;Library&amp;#x2F;Google&amp;#x2F;GoogleSoftwareUpdate&amp;#x2F;GoogleSoftwareUpdate.bundle
  sudo ln -F &amp;#x2F;private&amp;#x2F;var &amp;#x2F;var
&lt;/code&gt;&lt;/pre&gt;
This deletes the affected version of Keystone and reinstates the damaged &amp;#x2F;var symlink.&lt;p&gt;The version of Keystone packaged with Chrome is not affected by this bug, so allowing it to reinstall Keystone will not recreate the issue.</text></item></parent_chain><comment><author>Scapeghost</author><text>@norberg or any other Google Chrome&amp;#x2F;Keystone engineers:&lt;p&gt;WHY can you not make Chrome update like every other sane, well-behaved app?&lt;p&gt;Update notification -&amp;gt; User confirmation (or an OPTION for auto-updating) -&amp;gt; Download status.&lt;p&gt;Why do you insist on installing things into our startup sequence without our permission? If your intent is to &amp;quot;protect&amp;quot; users, increase the nagging. I&amp;#x27;d be fine with Chrome refusing to load any website until Chrome is updated to the latest version.&lt;p&gt;Even Apple, who is notorious for making users&amp;#x27; decisions for them, lets us choose when to update apps and operating systems.</text></comment>
<story><title>Google Chrome Keystone is modifying /var symlink on non SIP Macs causing k-panic</title><url>https://mrmacintosh.com/google-chrome-keystone-is-modifying-var-symlink-on-non-sip-macs-causing-boot-issues/</url></story><parent_chain><item><author>norberg</author><text>Hey. Google Keystone tech lead here. We are aware of the issue, and we&amp;#x27;ve stopped the release. We&amp;#x27;re building a replacement that fixes the problem. In the meantime, to fix affected machines:&lt;p&gt;&lt;pre&gt;&lt;code&gt;  sudo rm -rf &amp;#x2F;Library&amp;#x2F;Google&amp;#x2F;GoogleSoftwareUpdate&amp;#x2F;GoogleSoftwareUpdate.bundle
  sudo ln -F &amp;#x2F;private&amp;#x2F;var &amp;#x2F;var
&lt;/code&gt;&lt;/pre&gt;
This deletes the affected version of Keystone and reinstates the damaged &amp;#x2F;var symlink.&lt;p&gt;The version of Keystone packaged with Chrome is not affected by this bug, so allowing it to reinstall Keystone will not recreate the issue.</text></item></parent_chain><comment><author>norberg</author><text>We have a revised set of commands that fix the symlink more correctly. These can only be run from macOS Recovery Console:&lt;p&gt;&lt;pre&gt;&lt;code&gt;  rm -rf &amp;#x2F;Library&amp;#x2F;Google&amp;#x2F;GoogleSoftwareUpdate&amp;#x2F;GoogleSoftwareUpdate.bundle
  ln -shf &amp;#x2F;private&amp;#x2F;var &amp;#x2F;var
  chflags -h restricted &amp;#x2F;var
  chflags -h hidden &amp;#x2F;var
  xattr -sw com.apple.rootless &amp;quot;&amp;quot; &amp;#x2F;var&lt;/code&gt;&lt;/pre&gt;</text></comment>