Other users had already been able to resolve the problem by reinstalling MacOS - being careful to avoid formatting their disks and destroying their data in the process. Macintosh covered the issue in great detail, posting alternate solutions including a fix appearing at Reddit that’s said to work on “Hackintosh” systems (systems running Mac OS on PC hardware not provided by Apple). But if SIP was disabled on a given machine, the file system was damaged, rendering the Mac unable to boot. Google’s statement includes a set of commands that can be run from the Mac Terminal in order to remove the affected Google Software Update package and repair the file system. If a Mac had SIP enabled, the attempted change was blocked. (And thus a hashtag was born: #varsectomy.) Late yesterday, a Google Chrome support manager posted a statement revealing that a recent Chrome update “damages the file system on MacOS machines with System Integrity Protection (SIP) disabled … including machines that do not support SIP.” Specifically, the Google Chrome update attempted to delete a symbolic link, or symlink, to the /var system folder. Google Comes Cleanīut the solution to the problem came from a different source: Google. Editors scrambled, Variety published a news story highlighting the issue, and Avid swung into action, declaring the issue a “top priority” for engineering and support. On Monday, for example, assistant editor Michael Kamens reported on Twitter that the “whole team at Modern Family” saw their systems shut down. The bug hit Avid users hardest and fastest, as productions saw entire editing rooms go offline. Instead, users discovered and Avid later confirmed, the glitch was caused by a Google Chrome update wreaking havoc with the file system on certain MacOS workstations. A widely reported problem Avid users have been having this week with their MacOS Media Composer systems failing to boot apparently wasn’t an Avid issue after all.
0 Comments
Leave a Reply. |