Live data from Hacker News

Nasty macOS flaw is bricking MacBooks: Don't install this update

tomsguide.com

421–430 of 440 posts

Re: Nasty macOS flaw is bricking MacBooks: Don't install this update

#421
post #49

Well, that's it for Catalina then. Although I really want full Xcode 11.4/Swift UI/Swift 5.2 and my MacBook Pro a Catalina upgrade is just too much of a risk. On top of all the previous Catalina woes Apple should be hanging their heads in shame.

Maybe this one [1] help you enable Xcode 11.4?

[1] https://github.com/cormiertyshawn895/Retroactive

Re: Nasty macOS flaw is bricking MacBooks: Don't install this update

#423
post #102
post #82

Earlier quoted context omitted.

I had a similar issue to yours when I manually ran this update on my 16". It froze on a black screen, after doing the BridgeOS part of the update. I had to force it down. When it started, it continued the update and, thankfully, everything worked. However, I'm still having kernel panics after the Supplemental update. But interestingly, they only happen when the machine is supposedly sleeping, with the shell closed. I…

Even a supposedly sleeping Mac will wake up from time to time, doing exactly what I don’t know. But I consistently see it in the logs.

Yes, I know this, but when a Mac does this, it does it only to run routine Apple code, stuff that should not, under any circumstances, cause a kernel panic. And up until Catalina, that it never has, barring binary corruption or defective hardware.

In this case, the kernel panic seems to be related to the Intel Iris video driver.

Re: Nasty macOS flaw is bricking MacBooks: Don't install this update

#424
post #227

Earlier quoted context omitted.

Does anyone know what might have caused this recent downturn in Apple's software quality?

The iPad’s software keyboard is still buggy as hell. The software keyboard , the part of the OS that the user will interact with the most, and the part of the OS that is required to be the most stable, frequently just completely breaks and requires a full device reboot to fix. That, to me, is insane. It shows how shit the project management must be if they cannot even prioritize fixing critical bugs in the most impor…

I'll qualify this by saying I haven't owned an iPad since the 2nd gen, but how are the 3d party keyboards on iOS? Do they limit them like they do with non-Safari browsers?

I remember one of the main reasons I "jailbroke" my iPad was so I could install an improved/alternate software keyboard, but I remember reading they added the option officially a while back.

I'm curious: are they artificially limited or do they all just suck?

Re: Nasty macOS flaw is bricking MacBooks: Don't install this update

#425
post #227

Earlier quoted context omitted.

Does anyone know what might have caused this recent downturn in Apple's software quality?

Not sure myself though I’m sure books will in future be written about “the early signs of Apple’s demise”. My MacbookAir 6,2 (mid-2013) was screwed after the 10.15.4 update (not the supplemental). The SSD was totally not recognised. I’ve tried SMC and NVRAM resets numerous times and remote Recovery. The drive is now invisible. I opened it up to reseat it (cleaning pins and socket) to no avail. Fortunately I’ve got a…

Please let me know if replacing the drive works, my friend has the same issue.

Re: Nasty macOS flaw is bricking MacBooks: Don't install this update

#426
post #111

Earlier quoted context omitted.

It will sync email and other things so that everything is already downloaded when you wake it up. See https://support.apple.com/en-gb/HT204032

And it won’t do CRON because reasons

Ironically -- I think this bug is fixed in a like 10.15.3 or so. Eitherway a cron I set up over a year ago before I realized this bug has started mailing me since I updated to Catalina.

Re: Nasty macOS flaw is bricking MacBooks: Don't install this update

#427

Earlier quoted context omitted.

For 3, what it's taught me is that I have to load a video conference, go into the privacy settings, allow use of camera and microphone, then exit the video conference and load it again before anyone can see or hear me. I'm a consultant and talk to multiple clients all with their own video conference solution and having to do this every time I join a call where a client is using a different video conference solution i…

Surely this is the fault of the app and not macOS? I have plenty of apps that asked for those permissions once, got it, and never asked again.

They’re not asking again but asking for the first time is what is disruptive because it forces you to close whatever application is requesting permissions. It’s sucks when WebEx does it but at least that only makes you close WebEx. Still a really poor design choice but not nearly as disruptive as browser-based tools that make you close your browser.

Re: Nasty macOS flaw is bricking MacBooks: Don't install this update

#428

Earlier quoted context omitted.

If your entire startup is dependent on one single Macbook there is something severely wrong with your business model and I hope your customers and/or investors are aware of this risk before giving you any money.

Obviously depending on a laptop for runtime code would be bad, but plenty of early stage startups depend heavily on a small number of machines for customer support and continued development. Probably a bigger issue isn’t that they’re a single laptop failure away from collapse, the bigger problem is that replacing a laptop right now would be unusually difficult.

In the world of git and cheaply available easy to use backup software, there is zero excuse to not have backups of everything to load on another machine. Even if you want to avoid the cloud and keep it local, a 128gb USB3 drive is under $50.

“A small number of machines” is not what we are talking about. We’re talking about one single consumer-grade laptop that would collapse the entire business forever.

Re: Nasty macOS flaw is bricking MacBooks: Don't install this update

#429

Earlier quoted context omitted.

I absolutely agree. The action of pushing out major updates every year has lead to a drop in quality. They never get a chance to fix last years bugs because they are working on next years features.

That's not a fundamental issue though. Chrome pushes new features every six weeks. Android updates every year and doesn't suffer these kinds of problems. You absolutely can do regular updates that are high quality. You just can't do them in an environment that's deadline driven, or which gives PMs too much power over what dev teams work on.

You are comparing a browser to an entire operating system (and I believe Android does have those problems).

But you do have a point: it should be product driven not feature driven.

Re: Nasty macOS flaw is bricking MacBooks: Don't install this update

#430

Earlier quoted context omitted.

If that had happened to me my entire startup would have to shut down. Not cool.

Might not be a bad idea to buy another laptop (cheap) and just boot it up once a month to make sure you can use it, and if your system dies, then just pull that one out and use it while Apple RMAs your primary. If the cheap laptop doesn't have enough power, just connect to an Amazon Workspace or something and use that until your normal laptop can work again.

I think the critical need is access to the data on the dead Mac. After all, the owner of the dead Mac is still able to post to HN.
Post reply on HN