A wave of reported Macs being no longer able to boot was caused by a recent Google Chrome update that was corrupting a necessary operating system folder. Once the update was installed, affected users found they were no longer able to boot into macOS.
If this does not help you remove browser hijacker from Firefox, then Reset Mozilla Firefox. This manual was created to help get rid of “Google Automatically Switches To Bing” from your Mac. We described in detail how to remove browser hijackers from the Chrome, Safari and Firefox. We hope that this instruction helped you. Deltek Ajera support resources include: classroom & self-paced training, consulting & award winning customer support.
MantisBT is a popular free web-based bug tracking system. It is written in PHP works with MySQL, MS SQL, and PostgreSQL databases. MantisBT has been installed on Windows, Linux, Mac OS, OS/2, and others. The text that is displayed in the URL dropdown. Can contain XML-style markup for styling. The supported tags are 'url' (for a literal URL), 'match' (for highlighting text that matched what the user's query), and 'dim' (for dim helper text).
Yesterday we reported that some users of the Avid Media Composer video editing program were not able to boot their Macs after shutting down or restarting. While some users were concerned it was a virus, the thought was that a system folder was being corrupted.
Help+manual Bug Chrome For Macbook
It turns out that this issue is not being caused by a virus or an Avid update, but rather by a faulty Google Chrome for Mac update that is causing the /var symlink to be removed.
According to a Google Chrome open bug post, this is being caused by a bug in a new version of Google's software updater, codenamed Google Keystone.
Mac blog Mr. Macintosh explains that this is happening to users running macOS 10.9 – 10.14 Mojave who have disabled Software Integrity Protection (SIP).
They further state that many Avid users use 3rd-party video cards for video editing and need to disable SIP in order to use them, which might be the reason why the issue was noticed by so many in that community.
Google has posted a support article on how to resolve this issue by removing the current Google updater package and then recreating the /var symlink.
We recently discovered that a Chrome update may have shipped with a bug that damages the file system on macOS machines with System Integrity Protection (SIP) disabled, including machines that do not support SIP. We've paused the release while we finalize a new update that addresses the problem.
If you have not taken steps to disable System Integrity Protection and your computer is on OS X 10.11 or later, this issue cannot affect you.
To recover a machine that has been affected by this bug, please boot into recovery mode, and then from the Utilities menu open the Terminal application.
In the Terminal application, you can 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
Help+manual Bug Chrome For Macbook Pro
xattr -sw com.apple.rootless ' /var
Then reboot. This will remove the affected version of Google Software Update, then restore the damaged portion of the file system.
Note: An earlier version of this page mentioned OS X 10.9 instead of OS X 10.11.
As for Avid, they are just happy that it was not their program causing the issue and have shared this statement with BleepingComputer:
Today, Avid is confirming that the root cause for a reboot issue encountered by some of our customers has been identified and is unrelated to Avid and its creative tools. Google confirmed that a Chrome update “may have shipped with a bug that damages the file system on macOS machines.” Google has paused its release and provided instructions for affected users.
Help+manual Bug Chrome For Mac Os
Avid is also pleased to share that it has received no reports of data loss by affected customers. From the beginning when this issue was made known to Avid, our teams actively worked with customers, Apple and partners to identify solutions and communicate them to customers. At this time, most affected Avid customers have recovered from this issue by reinstalling their macOS. Avid received no reports of incidents from customers running on non-Mac operating systems. To reiterate, this was not an Avid issue, as was reported in some early media coverage. We are proud of the coordinated response by Avid, Apple and our partners and we jointly thank our customers for their patience, support and assistance as we worked to quickly resolve this issue.
Avid CEO Jeff Rosica stated, “Avid is pleased that the reboot issue facing some customers is solved and while Avid products are not the root cause, we’re keeping an intense focus on bringing all of our customers back online and back to work. Over the past 36 hours, the deep dive of due diligence working closely with Apple, PACE and other partners exhausted all options and we’ve landed in the right place as quickly as possible. We owe our special thanks to Avid’s customer and user community for their typically strong show of support at this time, especially to those who welcomed our engineers into their studios to troubleshoot.”
Comments are closed.