Otherwise this will definitely be the last MacBook I I am not a pristine Mac user but a Unix and macOS veteran. I hope someone at Apple decides that this is embarrassing enough to prioritize a fix. I routinely have to reboot my computer while I work, and sometimes wind up losing data because I cannot properly shut down apps or the OS.Īpple has fallen very far indeed if it no longer bothers to test its OS against popular devices and network setups. This really *****, as it makes my new $4k 16-inch MacBook Pro less stable than my old 2010 one. The only reliable solution at this point is to reboot the computer, after which things will work ok for a while before the issue reoccurs. Once in this bad state, the computer becomes unstable, and random apps (even those that don't seem to need access to the NAS), including Finder, Safari, and third-party apps, will hang, and cannot be completely force-quit and restarted. Some access, such as TimeMachine, may continue to work, while other access, such as in Finder, will not. Once in this bad state, the connection cannot be fully disconnected and thus reconnected, even by terminating the connection from the NAS side. The problem is that the the connection to the NAS gets into a bad state after some amount of time passes. Nor does setting the minimum SMB version to SMB 2, and the maximum to SMB 3. I hate to be the buzzkill regarding some of the "fixes" posted on here, but restarting does not resolve this issue. I know Apple is dealing with a few issues with the Catalina release mostly having to do with 64bit vs 32bit application support so I am not sure where this falls on their priority scale." Unfortunately, there is not an ETA that we are aware of. ".At this point it is a waiting game with Apple and our developers as they work together for a resolution.
Supposedly their engineers are working together on a fix, but Synology tells me that it's a low priority for Apple, since it only affects a small subset of their users (i.e. I have confirmed with both Apple and Synology that this is a known issue with OSX Catalina.
0 kommentar(er)
