-
Notifications
You must be signed in to change notification settings - Fork 36
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: symbol lookup error #25
Comments
This seems to be out-of-scope for both Protontricks and winetricks, and probably has to do with how curl is installed inside the Flatpak sandbox. I'm guessing libcurl (shared library) and curl (the binary) are both available inside the sandbox, but have different versions. If you can run
If the version number in |
Certainly. Nevertheless, I'm determined to find out the cause of this error. I've already contacted Flatpak guys about this error, but they (one person who addressed it) hinted at something else. As for your hint, I'm getting this output instead:
However, when I start a new shell within the sandbox, and run
But then if I run protontricks with the said shell, the error still persists:
|
Sorry for the late reply. I looked into this a bit more and looks like curl loads the shared library provided by Steam Runtime, which has the wrong version. Disabling Steam Runtime for Protontricks inside Flatpak seems to solve the issue. Try opening your
Open a new terminal and then check if the command works again. |
It works indeed. Thanks! |
On an unrelated note, I would replace |
Yeah, I noticed that the path had changed the last time I tried out the Flatpak version of Steam. I've made both changes to the wiki page now. |
I encountered the following problem when installing Windows DLL's and components, such as galliumnine standalone:
I have tried downgrading the following so far: protontricks to the release
1.2.2
, winetricks to the point release20190615
, and org.freedesktop.Platform to the commit5c0dd88790d99d5aee62c9a471a9e38b1b7ccbe6b3f9e144dfc9169821755990
(I'm using Flatpak Steam).I have also done a clean installation of Fedora Workstation 30 in a virtual machine to check if something on my installation of Fedora Silverblue 30 causes the error in question, but the issue persisted. However, I do not recall encountering this error 10 days ago when I was still using Fedora Workstation 30. I'm looking forward to hearing any clue as to what is to blame even though it might not be in this project's scope to solve it.
The text was updated successfully, but these errors were encountered: