Stories
Slash Boxes
Comments

SoylentNews is people

posted by Fnord666 on Friday September 27 2019, @02:07AM   Printer-friendly
from the testing-is-a-good-thing dept.

On Monday night, Variety reported that film editors around Los Angeles who had Avid Media Composer software installed were suddenly finding that their Macs were unable to reboot. The publication speculated that malware may have been the cause. On Wednesday, Google disclosed the real cause—a Chrome browser update.

Specifically, it was a new version of Chrome's Keystone updater that caused so many Macs to stop rebooting, according to this Chrome open bug post. When the update was installed on Macs that had disabled a security feature known as system integrity protection and met several other conditions, a crucial part of the Mac system file was damaged, a Google employee said in the forum.

"This appears to be an issue with a new version of Google Keystone," a different Google employee wrote earlier in the thread. "We have halted the rollout and are working on remediation right now."

[...] Google has instructions for restoring unbootable Macs here. The process involves booting into recovery mode and then opening a terminal window, which among other ways can be accessed from the utilities folder. From there, run the following commands:

chroot /Volumes/Macintosh\ HD # "Macintosh HD" is the default
rm -rf /Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle
mv var var_back # var may not exist, but this is fine
ln -sh private/var var
chflags -h restricted /var
chflags -h hidden /var
xattr -sw com.apple.rootless "" /var

Then reboot.

If everything goes right, the Mac will restart with the buggy Chrome update no longer installed and with the damaged file system repaired. It wasn't immediately clear when a fixed version of the Chrome update will be available.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by helel on Friday September 27 2019, @03:59AM (1 child)

    by helel (2949) on Friday September 27 2019, @03:59AM (#899422)

    It's worth noting that system integrity protection is on by default and there is no way to turn it off through the GUI. No causal user is suffering this problem right now and anyone who knows what they're doing will turn it back on if they ever need to turn it off. While the bulk of the blame has to go to google here the only people being burnt are those that know just enough about the command line to get themselves into trouble.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 0) by Anonymous Coward on Friday September 27 2019, @07:09AM

    by Anonymous Coward on Friday September 27 2019, @07:09AM (#899467)

    Except it is Google how got them in trouble here, no matter how you look at it.