←back to thread

macOS unable to open any non-Apple application

(twitter.com)
2603 points mattsolle | 1 comments | 12 Nov 20 21:00 UTC | HN request time: 0.001s | source
Show context
submeta ◴[12 Nov 20 21:15 UTC] No.25075156[source]▶
Unbelievable. When I read the tweet (tried to post here as well), I suddenly realized why my Mac was unresponsive an hour ago.

Here is another tweet that describes the problem in more detail:

https://mobile.twitter.com/llanga/status/1326989724704268289

> I am currently unable to work because macOS sends hashes of every opened executable to some server of theirs and when `trustd` and `syspolicyd` are unable to do so, the entire operating system grinds to a halt.

EDIT:

As others pointed out, I put this to my `/etc/hosts` file and refreshed it like so:

    sudo emacs /etc/hosts # add `0.0.0.0 ocsp.apple.com` 
    sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder # refresh hosts
replies(26): >>25075338 #>>25075481 #>>25075547 #>>25075666 #>>25075887 #>>25076053 #>>25076387 #>>25076568 #>>25076811 #>>25077902 #>>25077923 #>>25077940 #>>25079234 #>>25079856 #>>25079879 #>>25080093 #>>25080357 #>>25080370 #>>25080849 #>>25081772 #>>25081989 #>>25083938 #>>25087820 #>>25090415 #>>25090991 #>>25095226 #
read_if_gay_ ◴[12 Nov 20 21:49 UTC] No.25075547[source]▶
I started panicking mildly thinking my drive was failing or something.

And just before this, I finally managed to fix Spotlight pegging one core at 100% constantly. Next thing, I reboot into a laggy system. macOS is my favorite OS, but the shit I put up with... it's basically an abusive relationship at this point.

replies(10): >>25075694 #>>25075845 #>>25075881 #>>25075908 #>>25076012 #>>25076608 #>>25079197 #>>25079319 #>>25080929 #>>25085281 #
auslegung ◴[12 Nov 20 22:15 UTC] No.25075908[source]▶
> macOS is my favorite OS, but the shit I put up with...

Idk, the several Linux distros I’ve used recently, and Windows, have a much longer list of “shit _I_ put up with”

replies(6): >>25076146 #>>25076830 #>>25078156 #>>25078536 #>>25078842 #>>25085318 #
GordonS ◴[12 Nov 20 22:35 UTC] No.25076146[source]▶
Can you really think of a single thing worse than this?
replies(6): >>25076730 #>>25077674 #>>25077851 #>>25077883 #>>25078777 #>>25079002 #
jimmydorry ◴[12 Nov 20 23:26 UTC] No.25076730[source]▶
Computer failing to turn on as a buggy, mandatory update has replaced broken or replaced a driver with a non-functional one.
replies(1): >>25077086 #
GordonS ◴[13 Nov 20 00:08 UTC] No.25077086[source]▶
Fair enough, but that's not a typical experience on either Windows or Linux in this decade - if that's happened to you, then I think you've just been incredibly unlucky.
replies(7): >>25077673 #>>25077875 #>>25078015 #>>25078314 #>>25078701 #>>25080353 #>>25084526 #
quantummkv ◴[13 Nov 20 04:01 UTC] No.25078701[source]▶
I believe you must have been using Windows 7 without updates for the decade, because with windows 10 every[1] update[2] borks the system so much that Microsoft had to pull updates. And last but not the least, a big guide to fix problems caused by a forced, mandatory windows update[3]

[1] https://www.techradar.com/in/news/microsoft-kills-off-window...

[2] https://www.techradar.com/news/dont-install-this-windows-10-...

[3] https://www.techradar.com/in/how-to/windows-10-may-2020-upda...

Meanwhile on Linux, I cannot upgrade to the new kernel that contains a lot of support and fixes for my new shiny AMD Ryzen chip because it completely breaks the Nvidia driver, refusing even to boot.

Apple may suck, but it still sucks less than the alternatives

replies(2): >>25079452 #>>25080622 #
1. rvz ◴[13 Nov 20 06:13 UTC] No.25079452[source]▶
> Meanwhile on Linux, I cannot upgrade to the new kernel that contains a lot of support and fixes for my new shiny AMD Ryzen chip because it completely breaks the Nvidia driver, refusing even to boot.

Well that's the problem with Linux distros for the desktop in general. A user upgrading a newer version of a single system component risks breaking the whole desktop: systemd, libdrm, x11, whatever and something else doesn't work. I'm even excluding drivers here but again it's clear what happens when a user finds that out for themselves on Linux. If they even have the time and energy to do all that digging and googling of cryptic errors.

To save yourself the time and frustration, Just keep using Windows 10 with WSL2. I don't have any reason to dual boot to a Linux desktop any more due to this.