I am fully aware of this. My point was simply that Apple isn't to blame if their older software has bugs, which are likely/hopefully patched in newer versions of their software.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Hollywood Mac Pro Workstations Hit by Mysterious Software Issue [Updated]
- Thread starter MacRumors
- Start date
- Sort by reaction score
I am fully aware of this. My point was simply that Apple isn't to blame if their older software has bugs, which are likely/hopefully patched in newer versions of their software.
Google has identified the source of this problem being an issue with the Chrome autoupdater (called Keystone.) It actually had nothing at all to do with Avid. There was a new version of Keystone which deleted the /var symbolic link, which only worked on systems which did not have SIP enabled.
We're the same here. We run Avid but nothing higher than Sierra.
But as a golden rule for our company, we don't allow production computers on the internet. So this bug would never hit us.
Google has identified the source of this problem being an issue with the Chrome autoupdater (called Keystone.) It actually had nothing at all to do with Avid. There was a new version of Keystone which deleted the /var symbolic link, which only worked on systems which did not have SIP enabled.
The morons at these post productions shops, who installed Chrome on sensitive production hardware, should lose their jobs.
Good job compromising critical systems with totally extraneous, redundant and insecure web bull$#@*.
Last edited:
Google has identified the source of this problem being an issue with the Chrome autoupdater (called Keystone.) It actually had nothing at all to do with Avid. There was a new version of Keystone which deleted the /var symbolic link, which only worked on systems which did not have SIP enabled.
So all the pontificating by the “experts” here was wrong? It has nothing to do with Avid or macOS? It’s a Google bug?
Also:Google has identified the source of this problem being an issue with the Chrome autoupdater (called Keystone.) It actually had nothing at all to do with Avid. There was a new version of Keystone which deleted the /var symbolic link, which only worked on systems which did not have SIP enabled.
Google Chrome Keystone is Removing /var symlink on non SIP Macs Causing Boot Issues
Reports that some AVID Users Macs would no longer boot. It now may be that a Google Chrome Keystone update modifies /var on NON SIP Protected Macs.
mrmacintosh.com
That is probably the second most catastrophic bug you could manage to get into a web browser, and it's particularly egregious since it aggressively auto-updates.
Makes sense why regular users aren't seeing it, since almost no one is running without SIP.
Thanks for signing up to post 👏It's not Avid or iLok. It's a corrupted or otherwise broken Google update for Chrome. The update seems to have been pulled or replaced since this morning. Those systems affected all had System Integrity Protection (SIP) turned off, or were old enough to not have it in the first place.
It affected Avid and other video production users because they have a higher tendency to have left SIP disabled.
[automerge]1569353902[/automerge]
Google Chrome Keystone is Removing /var symlink on non SIP Macs Causing Boot Issues
Reports that some AVID Users Macs would no longer boot. It now may be that a Google Chrome Keystone update modifies /var on NON SIP Protected Macs.
Hopefully that’s the only cause; I’m sure we’ll know more later today.
Last edited:
Maybe because the (*4-letter*) AVID software requires it.
I have the 6-core MP, with SIP enabled - because I'm using FCPx.
Avid software does not require SIP be disabled.
[automerge]1569412428[/automerge]
The cause is now well understood by Google and a bunch of Mac admins. It’s definitely a combination of the bad updater and SIP being disabled.
I'm not in the least surprised that the problem stems from Chrome (wouldn't be surprised if it stemmed from any Google product really), but the days in which people could avoid using Chrome are unfortunately over. Chrome is slowly working towards the position that IE used to inhabit back in the blackest days of the internet, where there are many websites that aren't checked for functionality in any other browser (and the companies running those sites don't give a crap). Got a problem with the AirBnB website? Their response from support is (I'm not making this up) "Are you using Chrome? Chrome is the Best Browser!". Have devices that are configured via. a web-interface? (Ubiquiti, I'm looking at you here.) It's very likely that new bug introduced in their latest UI is because they didn't bother to test with anything other than Chrome. Will it be fixed? Maybe. Eventually. But it's "best just to use Chrome". It's becoming a pretty common issue, and while it's great to say "just don't use Google's crap" the reality is that people don't use computers for the sake of "using a computer", they use computers to get specific tasks accomplished.
Yes, and while I personally avoid google as good as I can I totally understand that people give up because they just wanna browse the internet or access data from a host that supports chrome.
Using chrome doesn't make you a moron. One might say it's careless, but look what's going on with facebook (or Insta, WhatsApp, etc.) and it is still used by many. I hope unfortunate events like what just happened will help to change this. We'll see.
This was a big enough problem in the industry that I saw an article about it in Variety.
Just uninstalled Chrome, which I'd been meaning to do anyway.
Just uninstalled Chrome, which I'd been meaning to do anyway.
You'll want to be sure you've followed the instructions to delete the Google updater. Just removing Chrome won't do that.
I'll check that out, thanks for the heads up.
edit: here's what looks like a very thorough set of Terminal commands for anyone interested: https://superuser.com/questions/318186/how-do-i-uninstall-google-chrome-completely-from-my-mac
There may also be /Library/Google, which would have contained the problematic updater.
iLok dongles are the main reason I refuse to use avid products. Also studios are notorious for neglecting to update their hardware. They are so paranoid about software causing bugs that can wipe a project. This excuse has merit. Software and certain computer companies can stick you in a forced obsolescence situation so the fear is usually because of costs.
Neither ilok / pace nor AVID got anything to do with this bug.
It’s an unfortunate combination of a crucial bug on google’s side and having SIP disabled. I guess now the times are over when people claimed it’s not a bad thing to have SIP disabled because it doesn’t do anything good anyways.
iLok is a headache. Maintaining a professional studio is a headache. Producers can be lazy and cheap. SOURCE: cheap lazy producer
I’d say that’s more like an inditement of AirBnB’s Android app, this requiring all website resources poured into the Chrome dev. Where the iOS app works perfectly for most Apple users trying to cheap out on sketchy flop pads. I think the savings probably aren’t worth the skin rash your gf will develop.
Fortunately, AirBnB is a total niche thing, and the rest of the modern web, and almost everything e-commerce related, lives in a Safari world.
Further, this latest incident just killed any continued usage for the professional and prosumer Apple market. The PR damage of this will be long lasting for Chrome.
Want to kill your Mac during a project? Google presents Chrome, now the fastest way to not get paid.