macOS 13.3.1
Juli Clover (release notes, security, full installer, IPSW):
According to Apple’s release notes for the update, it introduces a fix for a bug that could cause Auto Unlock with Apple Watch not to work, plus it includes a fix for an issue that caused the pushing hands emoji not to show skin tone variations.
See also: Howard Oakley, Mr. Macintosh.
Previously:
Update (2023-04-22): Maynard Handley:
If anything 13.3.1 is more of a disaster than 13.3.
(a) Unmounting then remounting all external volumes every 5 minutes! WTF???
(b) PERMANENT decal of the volume control icon sitting in the middle of the screen!!!
The latest point release of macOS (13.3.1) broke my screensaver. The screensaver works as expected on the MacBook when it’s not plugged into any external displays, and it works on one of the two monitors when it’s connected to two external displays, but the right monitor is always broken. I use “Classic” set to “Colors”. When the screensaver kicks on the right monitor just shows a black screen that says “No Photos”. How did it somehow manage to decouple the screensaver between displays?
Update (2023-04-24): Gabriel Zachmann:
With the latest upgrade to macOS 13.3, I have received a few reports from users that my screensaver (a real .saver) looks funny when the Mac has two monitors, the built-in one and an external one.
I read all the other comments concerning this fault after the update to Ventura 13.3, all happening with external monitors. So I don't feel alone. If I disconnect my 27 inch AOC external monitor, the problem goes away and the iMac shows my photos just fine.
Update (2023-04-25): Howard Oakley:
macOS Ventura 13.3.1 has a bug preventing the password for encrypted sparse bundles from being changed using
hdiutil. As there’s no alternative method, this has a high impact on those using encrypted sparse bundles, for instance to store Time Machine backups on network shares.[…]
Thanks to Paolo for confirming that this bug isn’t present in 13.2.1. This makes it most likely that it was introduced in 13.3, or possibly 13.3.1.
5 Comments RSS · Twitter · Mastodon
> The latest point release of macOS (13.3.1) broke my screensaver. The screensaver works as expected on the MacBook when it’s not plugged into any external displays, and it works on one of the two monitors when it’s connected to two external displays, but the right monitor is always broken.
Yup. Either 13.3 or 13.3.1 broke that for me, and as of 13.4 Beta (22F5049e), it isn't fixed.
(Screen saver in my case: Aerial. I imagine this either affects _all_ screen savers, or those that use the legacy engine.)
I was kind of hoping they'd fix two things that seem irreparably broken:
- TouchID with Bluetooth keyboards just plain doesn't work for me on a brand new M2 Pro mini (works a couple of times and then... nope)
- Stage Manager badly needs the same next/prev group keyboard shortcuts that are on iPad OS (will rant about that separately sometime soon)
None of these were fixed.
>Yup. Either 13.3 or 13.3.1 broke that for me, and as of 13.4 Beta (22F5049e), it isn't fixed.
But apparently it _is_ fixed in 13.4 Beta (22F5059b).
What isn't fixed is "legacyScreenSaver (Screen Saver (System Settings))" taking up an entire CPU core and especially going to "not responding".
Never mind, it's back. Filed as FB12166219. Currently says "Recent Similar Reports: None", but I don't know if that label updates immediately (do they use ML to immediately find similar reports?).
Apple just responded to my feedback saying that 13.5.1 fixes the weird screen saver bug.
So far, so good.
