Live data from Hacker News

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

tomsguide.com

271–280 of 440 posts

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

#272
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

Bugs me too. Your best bet is launchd which solves the problem, but it is a bit of pain to write job definition property lists. More here: https://www.launchd.info

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

#273
post #172

I think that Apple should take advantage of the lockdowns and focus just on fixing things. They don't need to ship anything new and they have the perfect excuse to focus on improving both their OS and their processes that allowed such flawed things to reach their users.

I wish macOS would just drop back to major releases every 2-3 years. Sure, drop a point release in September to add compatibility with whatever new feature iOS has gained, but my Mac is the computer I do work on. I need it to always be reliable. Right now it seems the only way to do that is wait a long time before installing any update they push.

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.

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

#274

Earlier quoted context omitted.

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, ap…

> Is this a change in Catalina?

No this was done years ago in 10.7. Spaces was awesome and super configurable. But they combined it into Mission control and made it much simple but less useful.

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

#275
post #153

Earlier quoted context omitted.

> Xcode 11.4 your probably not missing much, there are some serious regressings in that release, for example [0] [0] https://forums.swift.org/t/swift-5-2-struct-property-wrapper... (for me, cant make release builds because the compiler crashes... sigh...)

You’re missing the ability to connect to and debug on iOS 13.4 devices, I believe: https://forums.developer.apple.com/thread/130988 So now I’m stuck on 10.14.6 and iOS 13.3.1, one of which is not getting security updates. Really hoping Fuschia or someone steps up and displaces Apple.

What??? Xcode 11.4 requires Catalina now?? That’s nuts.

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

#276

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.

The SSD in a T2 Mac is encrypted in the same way that an iPhone is, so if the DFU crashes hard enough you’ll have to regenerate new keys and that’s equivalent to drive zero.

Glad it helped.

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

#277
post #227

This has been mentioned quite a few times but Apple's software quality seriously has taken a turn for the worse in the last few years. I've usually updated my macs to the latest OS's within a couple of weeks of release, but Catalina is the first time where I still have yet to update. Stories of bugs such as this as well as mail messages getting blanked out and unrecoverable makes me actually scared to upgrade.

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

According to HN threads within the lifetime of any given MacOS release, the last acceptable MacOS was System 8.

I'm running a 6-year old MB Pro, updated within the first week of every releases' public beta availability, never reinstalled. I use sudo far too liberally to be good for system health, including (as long as it was possible) deleting all sorts of files in /System, /private, etc. when I run out of space and believe they're superfluous via cursory inspection ( i. e. sudo rm -rf /System//{AMD,SCSI}).

And... it just works? I've never lost any data. I've typed in my WIFI password once and not changed anything since. Time Machine recently stopped working, and I had to follow the cable because I didn't remember where the HD actually was (taped beneath a cupboard, as it turns out; the power cable had somehow unplugged). Catalina did throw up a few permission dialogs after installation, but that took less than five minutes, even though I run a few low-level utilities (karabiner etc).

There are certainly some annoying UI bugs or inconsistencies. When you open an ePub in Books and immediately press cmd+f, for example, the search field loses focus repeatedly while the book opens. And why is cmd+f the shortcut for search almost everywhere, but not Keychain?

I recently installed Linux on a Desktop for some Cuda work, for the first in 15 years or so. Based on what I had read (mostly on HN), I expected Linux on the desktop to have made vast progress over that time. I'm sorry to say that it is, still, a complete disaster by almost any measure. I have no idea why the popular narrative sees the two anywhere close to each other.

Case in point: My installation of Ubuntu, using defaults, had an application menu with categories "Preferences", "Setting", "Utilities, and "System". Those all mean (almost) the same thing! There are two package managers now (apt and I forgot the new one's name), each with abpout five GUI and three CLI applications for installing packages. But both sometimes installed three year old versions of standard software (calibre, I believe). Good thing Homebrew is now available for Linux, because somehow they have no trouble keeping up.

Font sizes, margins, and contrast are all over the place. There are dozens of color schemes, yes. But much like unhappy families, each one fails in its own manner: with both a dark and a light one, I encountered parts of the UI where you'd suddenly have light buttons with light (invisible) text. Or, IIRC, light text on dark backgrounds. Which works -- until there's a link in the text.

There seem to be five different subsystems between my mouse and the desktop. None of seemed to allow adjusting scroll wheel acceleration. (Even pointer acceleration felt wrong to me. And even though I found the system of partial differentials that seems to be the official interface for adjustments, I failed to find the sweet spot. But this might be an issue of familiarity more than objective quality).

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

#278
post #16

This really sucks. Can’t use the new Xcode without Catalina but this release sounds so buggy.

I just found that out. Definitely stupid.

I’ve been avoiding Catalina because of report after report of how buggy it is. For example, emails disappearing and can’t SSH on a custom port are still problems even with 10.15.4.

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

#279
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…

The screen on my MacbookPro13,1 (late 2016) recently gave out. I needed a replacement but I was not convinced by any of the current Apple offerings -- I can't stand the stupid touch bar on the Pros, and the new MBA didn't sufficiently excite me.

The usual build-to-order options like Dell or Lenovo being backordered due to the pandemic, I walked into a Costco and bought a LG Gram 17[0]. This is the first time I bought a laptop off the shelf, and the first time my primary laptop has not been a Mac, in over a decade. I installed Xubuntu 18.04 LTS on it with no fanfare and have been quite happy with it since.

The early signs of Apple's demise, indeed.

[0] https://www.lg.com/us/laptops/lg-17z90n-r.aac8u1-ultra-slim-...

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

#280
post #255

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…

As much as I would like precise and accurate language, the reality is that people have varying degrees of knowledge of any field. That is why computer technicians and doctors alike have to ask deeper questions when making a diagnosis. Even within a field, people may have slightly different interpretations of what a word means. Take consumer electronics. Say someone plugged in the wrong power supply and blew an induct…

I agree with your definition of bricked- the specialized tools is the key part. However, even the definition of specialized tools can be ambiguous!

Machinery standards at least define this mechanically as a screwdriver or above. The software equivalent may be a USB cable.

Post reply on HN