Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

tomsguide.com

Post reply on HN
Print view View original

401–410 of 440 posts

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

#401

Post by dang »

doc_gunthrop wrote: post #339
swat535 wrote: post #256

Earlier quoted context omitted.

People on reddit are serious ? Which subs are you following ? All I see everywhere there is one word comments such as @nice, @oof,..etc and witty remarks. The discussion quality on HN is far better. Granted we do nitpick here though..

Sure the discussion quality is far better, if you're comparing to reddit in general . Discussion is often on par if you're on a niche subreddit focused on something technical. From a personal perspective, the discussion quality on HN (on average) has declined over the past couple years. In the past the majority of comments were more substantial; it was more common to see paragraphs of well thought-out comments that d…

HN has always had that. I think you're running into the perception bias where it always seems like things are getting worse.

Complaints about HN getting more like Reddit go back to 2007, before it was even called Hacker News.

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

#402

Post by plorkyeran »

apple4ever wrote: post #275
trevyn wrote: post #153

Earlier quoted context omitted.

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.

Over the last few years Xcode has dropped support for older versions of macOS very aggressively. It requires upgrading to a new major version within the year that the new version came out, and quite often requires the latest minor version as well.

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

#403

Post by ttepasse »

Avi-D-coder wrote: post #86

Why is Catalina so unstable, were there major architectural changes? I know they broke Nix, ssh and a few others, but why?

There was a major change in architecture: In spring 2018, beginning with the development cycle for Catalina Apple's developers started to move into the Spaceship, the new office building with open office "pods". ;)

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

#404

Post by filchermcurr »

forgingahead wrote: post #88

Side poll: Do people automatically download OS updates for their computers? A lesson from my Windows days way back when was never to update anything unless absolutely needed -- computer, phones, etc. "Needed" is loosely defined as "key software that you need to work is no longer working on your older OS, hence you need to upgrade your OS to keep using this key software (sorry!)." I'm aware of security patches etc, bu…

I love updates! I always update everything as soon as humanly possible. MacUpdater is like a sweet, sweet drug. I find the incidents of things breaking to be fairly low for me, and when things do break, it's usually fairly easy to find a workaround. Thankfully I've never had hardware get bricked before.

Having said that, I may have some kind of mental disorder because the thought of being behind when new software is released is abhorrent to me... Oh, but I don't AUTO update. I like to do it manually so I can read changelogs when available.

... I'm starting to feel like that person who enthusiastically tells everybody how much they love to peel their dead skin off. And everybody gives them 'that look'.

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

#405

Post by odshoifsdhfs »

ThePowerOfFuet wrote: post #298
odshoifsdhfs wrote: post #191

Earlier quoted context omitted.

I have this issue. Computer went to sleep after the update. This was on Friday. Haven't been able to do any kind of thing on it. Trackpad 'clicks' but no screen, not touchbar, nothing (2018 Macbook Pro). Called apple, they tld me it had to go a store, unfortunately where I live, due to quarantine there are no shops available to pick it, and we aren't allowed to drive outside our district. Will try the apple configura…

Have you tried force-restarting it?

Tried it all, nothing worked. Even the DFU revive/restore.

Tomorrow will call a close enough store that seems to be (stated on their website) doing pick-ups and see if they can come and pick it.

My main concern now is they will try to try and charge 1000 or so euros for a repair and I will have to eat the cost as I can't really ask for a replacement one from company or friends since everyone is stuck at home

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

#406

Post by odshoifsdhfs »

LASR wrote: post #342
odshoifsdhfs wrote: post #191

Earlier quoted context omitted.

I have this issue. Computer went to sleep after the update. This was on Friday. Haven't been able to do any kind of thing on it. Trackpad 'clicks' but no screen, not touchbar, nothing (2018 Macbook Pro). Called apple, they tld me it had to go a store, unfortunately where I live, due to quarantine there are no shops available to pick it, and we aren't allowed to drive outside our district. Will try the apple configura…

Did you try the basics first? Hold down power for long time. 30 seconds. There is a small chance you’re not affected by this issue.

All possible things. 30 seconds, 60 seconds. 10 seconds then plug in cable. SMC reset. DFU mode (it enters dfu mode, but restore doesn't work). I spent the last 48 hours trying to bring it back to life. Unless Apple releases some kind of software we can use on another mac to 'fix' this one, I don't feel it will be fixed without shipping it to them.

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

#407

Post by breatheoften »

owenmarshall wrote: post #246
sethammons wrote: post #239

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.

there are a really large number of things i can no longer accomplish with ios 13 text selection model that i used to be able to do ... the easiest test case for finding all the flaws is trying to edit a url in safari.

ios 13 wants you to "grab" the text insertion cursor and drag it around -- but what are you supposed to do when the text cursor is not visible? and what are you supposed to do when an entire text region gets auto selected as in the url area ...

i would really love for someone to fix this issue

-- or if anyone knows how to do it ... here's the problem: say you have a long url that ends with a number -- and you want to change that number or select it to copy and paste it elsewhere. how do you do this on iphone in safari after ios 13?

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

#408

Post by thesquib »

VHRanger wrote: post #388
nothis wrote: post #296

Earlier quoted context omitted.

With Catalina, I'm also not seeing any major benefit to upgrading. The features list is thin and no 32bit programs kills a lot of random stuff that I can't find a quick replacement for. This is the first time I'm not upgrading macOS in 15+ years.

There's Apple Arcade for one benefit

I haven't heard of that! But it sounds like it might be game related, so I probably haven't found it due to lack of interest.

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

#409

Post by brailsafe »

iaml wrote: post #306
nothis wrote: post #296

Earlier quoted context omitted.

With Catalina, I'm also not seeing any major benefit to upgrading. The features list is thin and no 32bit programs kills a lot of random stuff that I can't find a quick replacement for. This is the first time I'm not upgrading macOS in 15+ years.

Unfortunately if you want a good keyboard, you don't have a choice - new mbps can't downgrade lower than catalina.

The keyboards are mediocre at best anyway. My MS sculpt is the best keyboard I've used and try to bring it with me even if I'm just using my mbp as a laptop

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

#410

Post by brailsafe »

unloco wrote: post #332
crazygringo wrote: post #281

Is there any actual quantitative evidence this update is any worse than any average update? The article presents three forum posts as evidence... which isn't evidence. I assume every update ever has messed up a handful of people's computers, even if just coincidentally (e.g. the computer was going to die on the next reboot no matter what). If thousands of people were complaining on Twitter that would be one thing. Bu…

2019 imac getting kernel panics when going to sleep. It seems silly if you're not affected. But now that it's hit me, i'm about to go back to mojave. If it was just a weird bug, I could deal with it. But to kernel panic is a big deal to me. I cant trust the computer to not break if I walk away from it for 10 minutes. I guess I could turn off sleep, but that doesnt seem like a solution to me. To keep it running all th…

This could very well be a hardware or deeper issue. I had a similar but more specific issue with my 2018 mbp, and managed to isolate the issue after quite a bit of trial and error. They replaced it with a 2019 model brand new. I think for me it was specific to letting the battery drain completely, then closing it and plugging it into power and waiting a while. I'd open to a computer that had kernal panicked. It could be related to deep sleep/hibernate, where the contents of ram is written to the ssd and then restored on wake. You can test this probably by setting a hibernate timer and then testing what happens if it sleeps for just under and just over that time.
Post reply on HN