Whoever fixes this first will make a lot of money.
Edit: SteamDeck is also very good at this and that's why I'm sticking to it for handheld gaming.
Whoever fixes this first will make a lot of money.
Edit: SteamDeck is also very good at this and that's why I'm sticking to it for handheld gaming.
The solution happened to be unplug and replug for the first issue, and force reboot for the second. I've enough people having issues with external displays that I don't think it's an isolated problem.
For comparison a Surface Pro failing to go to sleep or getting hot in the bag hasn't happened to me in 2 years of owning these machines. It might surely happen, but it's far from a regular occurrence I think.
This isn’t something to be proud of. It means that you’re not applying the regularly-released security updates.
macOS is spectacularly good at restoring state on reboot. It’s like it never happened.
Update your software.
Numerous minor updates have screwed up things for me, particularly with some applications I rely on. I will usually lag 2-3 patches behind and wait for other people to suffer first and confirm what I use is stable. I am still on Sonoma / 14.5 at the moment.
Incidentally I actually have a Mac Pro here which is running Monterey which hasn't been patched for about 9 months. The universe has not and will not be imploding any time soon.
Everyone forgets the "availability" bit of security.
I don't disagree, but also...
I find it a bit surprising that this is still a thing. Why is there ever a time when I _must_ reboot? Is it just that mainstream kernels were designed at a time when people had lower expectations around this sort of thing, and now it's too hard to evolve their designs toward something that would allow for zero-downtime patching in ~all cases?
Other examples that make me wonder if it's mostly because people haven't demanded better:
- Enormous updates for all kinds of things (gigabytes for a bug fix release) because differential updates aren't pervasive. - Windows updates where a huge amount of work is done during the "rebooting" phase (why can't most of this be done before reboot?) - Absolutely atrocious power management on pretty much anything that's not a MacBook, and even not perfect on those.
I never thought we'd have flying cars by now, but if you asked me a decade ago to predict the future of operating systems... it wouldn't be this.
edit: maybe not the specific S3 sleep problem but a general inability to sleep correctly
On my personal laptops the cause could be all the accumulated junk I installed. Apple's refusal to support legacy software may help out since it seems the old software doesn't want to run on new hardware.
I've never had any issues with entering my password/doing TouchID to unlock the laptop as soon as I've opened the lid.
I've my own ritual for preparing myself for the "I am done" phase. Doing the last commits, writing down a few sentences on what should I do when I go back to work and closing the lid.
This have never happened with any other laptop I've had.
I got woken up in the night a couple of times because of my macbook doing that.
Note that security updates are independent of the OS updates (or should be). There is no real excuse of forcing a user upgrade an OS version.
Otherwise under personal use/control macbooks are great, though, in not forcing you do updates of annoy you to death about them.