Live data from Hacker News

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

tomsguide.com

261–270 of 440 posts

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

#261
post #219

Earlier quoted context omitted.

For a lot of people, any non-normal state == bricked. Especially now, when the genius bar isn't open. And yes, there's a difference between a soft brick and a hard brick, and it depends on your ability to repair. Getting my phone stuck in a bootloop is usually a soft brick, but my Pixel went into one a few years ago for no apparent reason (likely mobo failure) and that was beyond my capacity to repair or diagnose, so…

I have literally never heard the term "soft brick" before. You're just describing "broken".

It's somewhat common in the custom Android ROM community, where there are different levels of "brick".

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

#262
post #257

Earlier quoted context omitted.

If you go that route, "bricked" is now indistinguishable from "broke," and we already have a word for that. Broke. We would have then gone from a situation where we had two different states and names for each of those states to a situation where we have two words for the very same, very fuzzy state and no way to talk about the other state. It makes a mockery of the idea of advice. Imagine your parents calling you and…

You mean advil? Aspirin is most definitely not ibuprofen. Or is this just proving the point note that language does matter a lot.

You're all just messing with that n-gate.com guy, right?

(FWIW: If the terms are to be interpreted relative to the device owner's competence level, we also need to prosecute people saying "You're dead to me" for murder)

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

#263

Earlier quoted context omitted.

Recently moved from android to an iPhone. The one that gets me while typing: I can’t tap and place the cursor in the middle of a word! Say you mistype a word, you cannot edit that word. You have to delete the entire word or tap and hold to get highlighting and then drag the highlight together to cover one letter on the word and then you can delete and get your cursor in the middle of the word. Insane.

That’s not a bug. It’s worse: it used to work the way you describe but that functionality was removed. Next time: tap the cursor and hold. You’ll see it get bigger and you can drag it where you want.

Yep, this is an iOS 13 feature. Prior to this, hard-pressing the space bar was the correct solution (although it still works on devices with 3D Touch, and long-touch works on newer models).

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

#264
They're earning billions yet can't afford to keep 5 mac books of each type in different configurations in one room and person or computer who will launch update before release and report green light. As always whatever size of company testing is a bottleneck because having roughly 25 computers and testing room is a problem. What a wonderful world.

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

#265
post #72

Earlier quoted context omitted.

The original source[0] states that access to Recovery Mode is not possible, at least in some cases. One user there reports[1] that the device shows no signs of life--no power, no fans spinning, nothing: > No power at all. I tried SMC and PRAM reset but sadly was unable to do either since my computer won’t even turn on. [0]: https://forums.macrumors.com/threads/warning-macos-catalina-... [1]: https://forums.macrumors.…

Does this issue only affect T2 Macs and MacBooks? If so, maybe a DFU restore is needed.

Confirmed; this is what happened to my 16" after this install. I needed to do a DFU restore (using Apple Configurator 2 -- you can download it to your hopefully spare MacBook from the app store) to get my mac back up and running. Unfortunately, for some reason, after the DFU restore, my 16" came back up to do a full reinstall, and I had to restore my files from backup.

Took a day, but all's well now.

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

#266

Earlier quoted context omitted.

Does this issue only affect T2 Macs and MacBooks? If so, maybe a DFU restore is needed.

Confirmed; this is what happened to my 16" after this install. I needed to do a DFU restore (using Apple Configurator 2 -- you can download it to your hopefully spare MacBook from the app store) to get my mac back up and running. Unfortunately, for some reason, after the DFU restore, my 16" came back up to do a full reinstall, and I had to restore my files from backup. Took a day, but all's well now.

I hope Apple doesn’t expect that everyone has a “Spare Macbook” laying around. I’ve been experiencing random system crashes when anything connects via TB3, and 3 random Kernel panics since the update.

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

#267

Earlier quoted context omitted.

And what has users gained by that? For the past 5 years or so, I don't exactly know anything worth it from users' perspective. Getting third party app updates are enough to increase productivity.

One of the high-impact changes (which broke Nix as the grand-grand parent mentioned) was moving / to a read-only volume: https://support.apple.com/en-us/HT210650 Although this change may not be immediately visible it does increase security a fair bit (malware cannot embed themselves or replace system files) and also prevents accidental deletion. Apple made large strides in the last few years improving security, e.g.…

> I am still grumpy that they replaced Spaces by Mission Control

Can you elaborate? This terrifies me as I rely a lot on Spaces to organise my desktop between different projects

Is this a change in Catalina?

Is seems like Spaces is still a thing: https://support.apple.com/en-gb/guide/mac-help/mh35798/mac https://support.apple.com/en-gb/guide/mac-help/mh14112/10.15...

I'm pretty happy with how this works in Mojava, apart from the major gripe that the apps don't restore to the Space they were in after you reboot.

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

#269
post #67

I'm consistently amazed by HN's ability to take the most meaningless, inconsequential part of an article (the scroll behavior, the whitespace, the usage of the word "bricked"), and nitpick it to hell and back instead of actually discussing the article. Bravo.

> I'm consistently amazed by HN's ability to take the most meaningless, inconsequential part of an article (the scroll behavior, the whitespace, the usage of the word "bricked"), and nitpick it to hell and back instead of actually discussing the article. > Bravo. 'Bravi', or 'brave'(f) would be the plural of that.

To the others commenting on this comment: YHBT. HAND.

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

#270

Earlier quoted context omitted.

Recently moved from android to an iPhone. The one that gets me while typing: I can’t tap and place the cursor in the middle of a word! Say you mistype a word, you cannot edit that word. You have to delete the entire word or tap and hold to get highlighting and then drag the highlight together to cover one letter on the word and then you can delete and get your cursor in the middle of the word. Insane.

Press and hold on the spacebar. Wait a second. Then you can move the cursor left/right from the spacebar. iOS is generally quite good at these things. Like any new platform, you can't expect it the UX to be identical to an old platform that you're more familiar with.

But if the UX is objectively worse, requiring additional unnecessary steps, it’s super annoying.
Post reply on HN