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
libcurl-gnutls.so.4: cannot open shared object file #6
Comments
yes, there is such trouble with deployment on some linux distros |
please download the new version and report the results |
@K0R0L Where is the new version? Is it ported away from the old curl open ssl version 3 protocol? |
new version on site |
problem persists on Fedora 25... but with
it opens, but with some warnings,..
|
Same on Fedora 26. |
Works on F26 as per @fchicout suggestion above. |
Has this problem. FIx like @fchicout |
Had this problem on F28. Fixed as per @fchicout. |
OnlyOffice crashed for me on Fedora 29 even with the workaround applied, but after the December 2018 update v5.2.4 it finally starts and runs (still needs the workaround, to be clear). |
OO crashes without ever starting with a fresh install (downloaded today, 02.02.2019) on Fedora 29. Error: The workaround in this thread allows it to run. |
OS : ArchLinux When I try to connect to a ONLYOFFICE cloud using HTTPS:
But I have the lib:
So I tried a fchicout-like workaround:
But it didn't work:
Edit: AUR |
Fedora libcurl uses openssl not gnutls. Could you please provide the RPM spec file you are using so that I could fix it together with other Fedora developers? |
Need to figure out how to extract the spec file from the built rpm, but here is additional information in the interim:
|
@TheRoarkster you cannot retrieve it from the compiled RPM. You need the SRPM (source RPM) |
Right. Any idea where I can get that? |
Still happens in Fedora and Centos 7 |
DesktopEditors 5.3.3 was released. Issue should be fixed |
OS: Fedora 24
Installed from RPM download which claims to be for Fedora 24.
./DesktopEditors: error while loading shared libraries: libcurl-gnutls.so.4: cannot open shared object file: No such file or directory
The text was updated successfully, but these errors were encountered: