-
-
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
Curl error(query): Problem with the SSL CA cert @ v0.0.13-11300-f1c65dce #8039
Comments
There is no way LD_PRELOAD libcurl for more test due libcurl is statically link. |
Cannot reproduce |
Thread 1 "rpcs3" received signal SIGSEGV, Segmentation fault. |
How should I rebuild rpcs3 for debug and develop ? rpcs3/.ci/build-linux.sh or ========================= |
Same bug seen here as of RPCS3 Version: 0.0.10-10494-e485c9c7 Alpha , also on Fedora 32. |
I have the same bug too, RPCS3 Version is 0.0.11-10645-282b0067 Alpha. Distro is Fedora 32. |
I encountered this bug as well. RPCS3 version is 0.0.11-10808-af9e217f Alpha. Distro is Fedora 32. |
Found the root cause !!! Rpcs3 Appimage built-in libcurl(libcurl-gnutls.so) is using gnutls back-end which is not libcurl build system default SSL back-end. Most of Linux distribution use openssl as default back-end because its:
Other then code size there is no reason using gnutls instead of openssl. |
Workaround:
|
I have also encountered this bug on openSUSE Tumbleweed with AppImage build 0.0.13-11287. |
I just now tested flatpak build and it doesn't have this error. You can use that for now folks. |
Still happens on 0.0.13-11300-f1c65dce.
The easiest way to fix this issue without touch build configuration which are distribute CA file within App Image or link libcurl to system. |
Please retest with latest AppImage |
Still not working on latest appimage.:
|
Still an issue as of 0.0.15-12056. Il try and draft a PR. it's just annoying and doesn't really prevent you from using the goodies. |
scratch that. i just built from master and its working just fine. Cool! |
Please retest with latest AppImage |
Still the same (F33):
|
Hello everyone, after digging around I have finally pinpoint the cause and come up with a solution. The problem lies in the fact that different distros have different paths for the certificate file that |
Thanks for that, I thought that was fairly common knowledge though, which is why I didn't mention it. Of course this can be fixed client-side, but the whole point of AppImages is that they are supposed to be portable regardless of Distro and without modifying the user system ;) |
My ideal fix for this is building our own version of Qt for our AppImage builds and using WolfSSL instead of OpenSSL, but it's something I haven't had the time to experiment with yet. |
Just wanted to mention, that in openSUSE the command is: |
This is not a solution. From my perspective this is a workaround.
If we have to done it in this way. Why we just put all certificates we need
into app image ?
Don't argue about built-in certificates is not safe.
Because when we choice to download binary application with almost all
library dependency in binary, There is no safety at all.
So as I mentioned before, either put everything into app image to make
users happy from every distribution or
just keep libraries like curl, openssl link dynamically to system, because
those libraries not affect RPCS3 it self's function.
…On Sun, May 23, 2021, 22:45 perrsona1234 ***@***.***> wrote:
For RHEL, CentOS and Fedora distros, the command would be:
sudo ln -s /etc/pki/tls/certs/ca-bundle.crt
/etc/ssl/certs/ca-certificates.crt
Just wanted to mention, that in openSUSE the solution is:
sudo ln -s /etc/ssl/ca-bundle.pem /etc/ssl/certs/ca-certificates.crt
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#8039 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHCDRWPLMJB5HNHNVJJEODTPEIITANCNFSM4MIFU7BA>
.
|
I'm curious if this still happens with the latest version. |
Hi Oltolm,
Not sure. I'll test it in next week.
Best Regards,
Dark
oltolm ***@***.***> 於 2023年7月14日 週五 06:19 寫道:
… I'm curious if this still happens with the latest version.
—
Reply to this email directly, view it on GitHub
<#8039 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHCDRQLGNY6BSQSQF5XCTLXQBX75ANCNFSM4MIFU7BA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Cannot reproduce on v0.0.28-15372- 38a5313 That said, I also cannot reproduce this on v0.0.15-12170- 5724d2d anymore so it's likely this got fixed on my end (Fedora 37 as of this writing). |
Cannot reproduce on v0.0.29-15827- 8b6fa32 |
Closing as it's seemingly fixed. |
I got this error on trying to update rpcs3. I am on a macbook pro m3 silicon chip. What else do you need to know to reproduce it? |
How to reproduce:
0. run AppImage
Expected:
GUI works as its design.
Result:
"Check Update" ->
Do nothing. Error message as below.
E UPDATER: Curl error(query): Problem with the SSL CA cert (path? access rights?)
"Download Compatibility Database" ->
Do nothing. Error message as below. Then Segfault.
E UPDATER: Curl error(query): Problem with the SSL CA cert (path? access rights?)
Segfault reading location 00007fe6b4000080 at 00007fe6b4000080.
Thread id = 140632403251456.
The text was updated successfully, but these errors were encountered: