{"id":29063,"date":"2020-05-27T16:07:50","date_gmt":"2020-05-27T20:07:50","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=29063"},"modified":"2020-06-05T16:04:38","modified_gmt":"2020-06-05T20:04:38","slug":"macos-10-15-5","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2020\/05\/27\/macos-10-15-5\/","title":{"rendered":"macOS 10.15.5"},"content":{"rendered":"

Apple<\/a> (TidBITS<\/a>, MacRumors<\/a>, Hacker News<\/a>, Mr. Macintosh<\/a>, Howard Oakley<\/a>):<\/p>\n

macOS Catalina 10.15.5 introduces battery health management in the Energy Saver settings for notebooks, an option to control automatic prominence of video tiles on Group FaceTime calls, and controls to fine-tune the built-in calibration of your Pro Display XDR. The update also improves the stability, reliability, and security of your Mac.<\/p><\/blockquote>\n\n

The update went smoothly for me on the MacBook Pro. I’m still using Mojave on my iMac. Alas, the update does not fix the remaining data loss issue with Apple Mail<\/a>. Mail’s version number is unchanged since macOS 10.15.4.<\/p>\n\n

Mr. Macintosh<\/a>:<\/p>\n

\n

NOTE!!! on the softwareupdate --ignore<\/code> flag change.<\/p>\n

Major new releases of macOS are no longer hidden when using the softwareupdate<\/code> command with the --ignore<\/code> flag<\/p>\n

****This change also affects macOS Mojave and macOS High Sierra after installing Security Update 2020-003.****<\/p>\n<\/blockquote>\n\n

Adding a Catalina nag in a security update is not very nice.<\/p>\n\n

Jeff Johnson<\/a>:<\/p>\n

Apple’s support article seems to be not entirely accurate. It’s true that the Software Update preference pane now refuses to ignore the Catalina update on Mojave. Nonetheless, softwareupdate<\/code> itself does continue to ignore it! Fortunately, then, there’s still a way to make the red badges go away. We don’t need no stinkin’ badges!<\/p>

The key is to avoid<\/em> opening the Software Update preference pane. It’s fine to open System Preferences though. If you happened to open the preference pane after installing the Security Update 2020-003, you can just repeat the above steps, and the badge will still go away.<\/p>\n

[…]<\/p>\n

It may be a bummer to have to check and install everything from the command line, but it’s preferable to a permanent red stain<\/em> on your Dock, isn’t it?<\/p>\n<\/blockquote>\n\n

Mr. Macintosh<\/a>:<\/p>\n

\n

I have received 3 different reports that the 10.15.5 Update is still changing the ComputerName & HostName back to default<\/p>\n

The last update that I’ve received from Apple said that this issue will NOT be fixed until macOS 10.16<\/p>\n<\/blockquote>\n\n

Mike Bombich<\/a>:<\/p>\n

\n

Early last week we discovered an APFS filesystem bug in a beta of macOS 10.15.5. The technical details of the bug are laid out below, but the short version is that we’re no longer able to use our own file copier to establish an initial bootable backup of a macOS Catalina System volume.<\/p>\n

[…]<\/p>\n

The chflags()<\/code> system call can no longer set the SF_FIRMLINK flag on a folder on an APFS volume. Rather than fail with an error code that we would have detected, it fails silently – it exits with a success<\/strong> exit status, but silently fails to set the special flag. That’s a bug in the APFS filesystem implementation of chflags<\/code> – if a system call doesn’t do what you ask it to do, it’s supposed to return an error code, not success. That’s a fairly nasty bug too. Apple preaches that you should always check your error codes, and we do – religiously. This bug slipped past us for who knows how long because the system call exits with a success<\/strong> error code.<\/p>\n<\/blockquote>\n\n

Tim Schmitz<\/a>:<\/p>\n

\n

Please fix the recurrent kernel panics during sleep on my 16” MBP 🤞🤞🤞<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n