-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash with OpenSSL 3 on arm32 #2736
Comments
Hi, this is with Raspberry Pi OS or a custom system based on that? Please try with a supported distribution: (The Speech SDK releases for Linux arm32 and arm64 are tested on Ubuntu.) |
I've done the same with Ubuntu 22.024 on arm32 and get the same results. Starting from a clean Ubuntu install, and installing the prerequisites as below, with the config.txt tweaked to enable my microphone. OS: Ubuntu 22.04.5 LTS
Hardware: PI CM4 Package: Microsoft.CognitiveServices.Speech version 1.42.0 Prerequisites installed:
Output:
Log (full log attached):
This is on a system with only OpenSSL 3 installed:
Not very scientific, but there is a reference to openssl 1 in the library, where the x64 file references openssl 3:
|
Thank you for reporting the issue. We have confirmed the bug on Linux arm32, and the fix will be included in the Speech SDK 1.43.0 release. This should be available in early March. |
I'm trying to get the Speech SDK working in our environment, a Raspberry PI 4 running a buildroot Linux OS. I had it working a year or so ago before we put the project aside, but since then we've upgraded to OpenSSL 3 (3.3.2 on my test machine) and I now get a ConnectionFailure error.
I've reproduced this in the C# helloworld sample fresh from the git repo (/~https://github.com/Azure-Samples/cognitive-services-speech-sdk/tree/master/quickstart/csharp/dotnetcore/from-microphone), and linked against Microsoft.CognitiveServices.Speech version 1.42.0. Changing only the subscription keys I get the following output when I launch it:
The same sample run locally on Windows works exactly as it should, so it isn't the subscription details at fault.
After enabling logging, I see the following in the log:
The full log is attached. It looks like the log is saying it failed to find openssl, even though it successfully determined to use the openssl 3 library.
log.txt
This seems very similar to the closed issue #2420 for arm64 - could the same thing have cropped up in the arm32 build? I don't have a tool on my target system to check exactly what it's trying to link against, but I do see mention in libpal_azure_c_shared_openssl3.so of libssl.so.1.1. The arm64 version of the same library has libssl.so.3 in the same place in the file.
The text was updated successfully, but these errors were encountered: