Does it have any fixes for the notarization delays ?
macOS Catalina 10.15.5
231–240 of 387 posts
Re: macOS Catalina 10.15.5
#232Earlier quoted context omitted.
Is it a remote time-machine backup, i.e. to a Time Capsule (or a NAS pretending to be one)? Time Machine used to use AFP, but since AFP was deprecated, it now exclusively uses SMB for remote backups. (Specifically, it creates a sparsebundle image on the SMB share, and then locally mounts it.) Now, Apple has their own implementation of SMB; and it seems to have been seeing frequent updates in Catalina (see https://sup…
I'm hitting the stupid SMB bug everyday but the symptom seems to be different. I tried to manually connect to `smb://nasbox.local` in Finder and it works with `nasbox.local` appearing in the sidebar. I can also click `nasbox` (without `.local` and this is advertised by the avahi-daemon on the nasbox I believe) and it opens the network shares fine. However, if the Mac goes to sleep for a while and then later wakes up,…
> I tried to manually connect to `smb://nasbox.local` in Finder and it works with `nasbox.local` appearing in the sidebar.
Right; that part still works, seemingly because probing for SMB shares doesn’t involve passing an SMB URI through whatever layer of the SMB stack can no longer resolve mDNS origins. It’s only connecting to the shares themselves that generates that arcane error message.
> I can also click `nasbox` (without `.local` and this is advertised by the avahi-daemon on the nasbox I believe) and it opens the network shares fine.
Yup; the Apple SMB stack is seemingly happy to resolve a WINS origin. Which means SMB servers will interoperate fine with macOS clients as long as the SMB server doesn’t run AFP (which nobody has a reason to be running these days anyway) and doesn’t offer Time Machine backup (which... is often the whole point of having a NAS.) If your NAS is configured to offer Time Machine backup, the WINS announcement gets subsumed by/attached to the mDNS host metadata record for the NAS (which is required to make Time Machine work), such that trying to connect to the SMB share via the Networks item (or the sidebar) will try to use the "canonical" mDNS origin for the host, rather than the WINS SMB-service origin—even if mDNS pointed at it.
> However, if the Mac goes to sleep for a while and then later wakes up, I can no longer access the shares
A thing about mDNS is that it gets announced on intervals, and clients are expected to cache it; but like regular DNS, the cached record announcements have TTLs, and you’re not allowed to use a record after its TTL runs out... but unlike regular DNS, you can’t just go re-fetch the mDNS record from the source once it expires; you have to wait for it to be re-announced.
This is why every bonjour/avahi/zeroconf tutorial has a line that says “now wait 15 minutes to see if your changes took effect.”
And this also means that these services inevitably do this thing where their URIs won’t resolve for the first few minutes after your computer wakes up from sleep, until they receive a refreshed announcement of the mDNS peer’s A and SRV records.
This has always been an inherent flaw in mDNS, papered over by various pre-resolution or standards-violating caching strategies by things higher-up the stack than the mDNS resolver itself. I’m not surprised that this sort of hacks papering-over is something prone to regressions, in macOS or any OS.
(This is also why Apple gave up on "Back To My Mac." It was dependent on "Wide-Area Bonjour", which was even more fraught and flaky than regular mDNS, with service records frequently disappearing from their domain, leaving you unable to resolve the address of your remote peer, despite it sitting there happily waiting with ports open. It especially didn't play well with laptops sleeping in a Wake-on-LAN state, despite several generations of Power Nap trying to make it work.)
Re: macOS Catalina 10.15.5
#233Earlier quoted context omitted.
I've got a brand-new 2019 16" and am dealing with the widespread crashes on wake from sleep. Honestly, it's a harder decision to send it back than you might think, for several reasons: 1) The hardware quality of other OEMs is bad too. Lenovo has really gone downhill. I sold my maxed-out X1 Carbon 7th Gen, which in less than a year: a) came with an LTE card that never worked for more than an hour at a time; b) had the…
XPS 15
Personal experience: XPS 15 overheats and becomes extremely slow. Maybe it's a user error...
Touchpad hardware is good, but the software and adjustability... it's nowhere comparable to a Macbook.
Re: macOS Catalina 10.15.5
#234Earlier quoted context omitted.
> Binary patching hasn't been a thing for years unfortunately. True, and it's fair to say binary diffs aren't worth the complexities they introduce anymore, yet the concept of only pulling updates for individual packages has been a thing for over two decades in the *nix world. It seems like a poor choice for Apple to not bother making updates more discerning while also removing binary diffs... certainly a shitty move…
Definitely frustrating for anyone not on broadband. There are more of us than you'd think. It's a giant 'fuck you' from the software industry, real world efficiency be damned.
Totally agree. Updated to Catalina recently and on top of the huge patch size the update client doesn't seem to have any retry mechanism built in. Connection drops 9.9G into a 10G download? Too bad, start over. Just a simple wget -c would do. Incredible.
Re: macOS Catalina 10.15.5
#235I have Catalina on a iMac Pro, a 16inch and 15 MacBook pro and for what it worth have hit zero issues.
Yep late 2013 MacBook Pro: Catalina brought some security annoyances but mostly pain-free. IMO this computer is the epitome of function and form; I'm worried nothing will truly replace it when that time comes.
I had a mid 2013 MacBook Pro at work and I completely agree - the epitome of function, form and longevity. I used it daily for almost 7 years and just recently passed it on to a non-dev coworker who needed a laptop at home, and got a 2019 MBP instead. I replaced it because I needed more than 500 GB of disk space. Otherwise it still works perfectly. I think that's very impressive for a 7 year old laptop these days.
Re: macOS Catalina 10.15.5
#236I have Catalina on a iMac Pro, a 16inch and 15 MacBook pro and for what it worth have hit zero issues.
No problems on my 15" 2017 MBP :) . I'm not much of a power user though
Re: macOS Catalina 10.15.5
#237> The battery health management feature in macOS 10.15.5 is designed to improve your battery's lifespan by reducing the rate at which it chemically ages. The feature does this by monitoring your battery's temperature history and its charging patterns. > Based on the measurements that it collects, battery health management may reduce your battery's maximum charge when in this mode. This happens as needed to ensure tha…
I just had a MBP fixed (it was quick!) due to it swollen up one day. It would not lie down flat on a table and the trackpad was useless. Obviously could not close the screen either. How common is this?
I'm on my second swollen battery in my 2015 15" MBP.
Java dev though so my computer is always near the temperature of the sun's surface which I think has something to do with it. We purchased 5 of these MBPs on the same date and the other Java devs machine is swollen while the testers machines are still fine.
Re: macOS Catalina 10.15.5
#238Earlier quoted context omitted.
Oh damnit, damnit. I've been having those on 10.15.4 too, was really hoping they'd fixed it on this one. It's really profoundly upsetting to spend $3,500 on a brand new computer by the most reliable major manufacturer in the industry and still have daily damn kernel panics.
> by the most reliable major manufacturer in the industry You might want to revisit that. If you are looking for reliability, ThinkPads are way better.
I have had too many bad experiences with Lenovo business class desktops and servers to hope that one product line from them is somehow exempt from reliability issues.
Re: macOS Catalina 10.15.5
#239Earlier quoted context omitted.
> XPS 15 OH YES? https://www.google.com/search?rls=en&q=dell+xps+15+crashing https://www.google.com/search?rls=en&q=dell+xps+15+coil+whin... https://www.google.com/search?rls=en&q=dell+xps+15+battery+s... https://www.google.com/search?rls=en&q=dell+xps+15+overheati...
I have trouble measuring how many complaints are real at scale type issues anymore. I think you could find any popular hardware, particularly with any emphasis on performance where there aren't some issues logged.
Yes, this is reality. But for some reason some people decide that they're absolutely certain about the huge scale of issues with Apple products while being absolutely certain about the lack of scale for issues everywhere else. It couldn't _possibly_ be their bubble.
Re: macOS Catalina 10.15.5
#240Earlier quoted context omitted.
Apple got sued for throttling iPhones with overly aged batteries. My understanding is that for all battery-dependent devices, you either sometimes throttle the CPU so it doesn’t demand more voltage than the battery can reliably deliver, or else you risk sudden power loss at what appears to be 20% life. After the lawsuit I assume now all manufacturers leaving it up to the consumer to decide which behavior they want.
There's nothing wrong with throttling in itself. Pretty much anyone will prefer a performance hit to a spontaneous shutdown. Where Apple got in trouble was that they were doing it secretly . Now days they still do the throttling, but you can go into battery status and it tells you if the battery is delivering peak performance or not.
It actually gets worse in Apple's case. They were doing it secretly, which is bad enough, but they were also denying warranty repairs to throttled phones (since policy was to only conduct the repairs once an arbitrary "health" metric fell below a certain point, and the throttling kicked in first).
This meant your options were to either deal with the crap performance, or void your warranty by installing a third party battery.