Solid as a rock until I upgraded to macOS 15.0 (Sequoia). Now, Parallels Client is abending frequently when connected to my local Linux server running XRDP. I'm am not aware of Sequoia implementing OpenSSL, so this message has me confused. This is what I see in the log: [I 00/00000071/TED66B240/P4773] 02-10-24 13:50:55 - Initialising OpenSSL library [E 00/00000070/TED66B240/P4773] 02-10-24 13:50:55 - Failed to initialize openssl fips provider with error: '40B266ED01000000:error:1C8000D5rovider routines:SELF_TEST_post:missing config data:../../../providers/fips/self_test.c:290: 40B266ED01000000:error:1C8000E0rovider routinesssl_set_error_state:fips module entering error state:../../../providers/fips/self_test.c:388: 40B266ED01000000:error:1C8000D8rovider routines:OSSL_provider_init_int:self test post failure:../../../providers/fips/fipsprov.c:707: 40B266ED01000000:error:078C0105:common libcrypto routinesrovider_init:init fail:../../../crypto/provider_core.c:932:name=fips ' [D 02/00000000/TED66B240/P4773] 02-10-24 13:50:56 - Restoring MainViewModel.SavedState: Optional({ rdpViewModel = { selectedConnection = "_86269B8D80D14B1CB928FA08D4123062"; }; state = { state = rdp; }; }) [D 02/00000000/TED66B240/P4773] 02-10-24 13:50:56 - Saving MainViewModel.SavedState: Optional({ rdpViewModel = { selectedConnection = "_86269B8D80D14B1CB928FA08D4123062"; }; state = { state = rdp; }; })
Update: An update to macOS Sequoia 15.0.1 may have resolved the issue. I've held a connection to my server for a couple of hours now without it abending.
Update #2: Nope. The problem still exists. And it's happening on two different Macs, both running macOS 15.0.1 (Sequoia). One is an M1 MacBook Pro (2020) and the other is an M2 MacBook Air (2022). I've send the crash reports to Apple, but who knows what if anything they do with them.
An upgrade to Parallels Client (v 20.0.25389) appears to have fixed the problem. I'm running macOS Sequoia 15.1 and the client has been stable for nearly 24 hours without crashing.
Hello, Yes, v20.0 has the fix for the crash problem. Error messages in logs you provided indicates issues with loading some of SSL contexts, it was not related to the crash. As for networking problems, it appears that macOS 15.1 also has connectivity problems while firewall is turned on. Hopefully they will fix it in the next release.
Well, I'm happy that the recent update seems to have fixed my connectivity problems (I run a self-signed certificate on my server, which is not public facing, so the SSL message was probably related to that). I've now run it for nearly two days continuously without any issues.