←back to thread

2603 points mattsolle | 1 comments | | HN request time: 0.419s | source
Show context
submeta ◴[] 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_ ◴[] 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 ◴[] 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 ◴[] No.25076146[source]
Can you really think of a single thing worse than this?
replies(6): >>25076730 #>>25077674 #>>25077851 #>>25077883 #>>25078777 #>>25079002 #
jimmydorry ◴[] 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 ◴[] 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 #
Osiris ◴[] No.25078015[source]
Disagree with Linux. I make an LVM snapshot before making any attempts to upgrade the graphics driver. It's a disaster. And don't say proprietary code, that's beside the point. Windows runs drivers in a way that one that crashes can be restarted without bringing down the kernel or the whole system.
replies(2): >>25078295 #>>25090471 #
simias ◴[] No.25078295[source]
FYI I've had the issue you describe half a dozen times with CentOS but literally never with Arch Linux (on both machines with similar nVidia cards, using the proprietary driver). In general I'm pretty impressed with Arch's package quality, I seldom encounter any issue and when I do it's patched very quickly.
replies(2): >>25078928 #>>25078966 #
1. Osiris ◴[] No.25078966[source]
I tried Arch Linux in a dual boot scenario on this System76 laptop and I don't recall why I switched back... I think it's because I tried to upgrade the graphics driver and got into state where I couldn't get X to run at all.

A co-worker keeps telling me to try Manjaro. I'm just not sure if I want to spend a weekend reinstalling all the stuff I use.