Skip to content
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

"Cannot open shared object file" on Debian/stretch #168

Open
jkirk opened this issue Jul 13, 2018 · 6 comments
Open

"Cannot open shared object file" on Debian/stretch #168

jkirk opened this issue Jul 13, 2018 · 6 comments

Comments

@jkirk
Copy link

jkirk commented Jul 13, 2018

libgstapp-0.10.so.0 (and other shared object files) are missing in Debian/stretch:

% ./pydio-ui 
./pydio-ui: error while loading shared libraries: libgstapp-0.10.so.0: cannot open shared object file: No such file or directory

What is the best way to solve this issue?

@gerroon
Copy link

gerroon commented Aug 17, 2018

I have the same issue. Any solutions?

@jkirk
Copy link
Author

jkirk commented Aug 18, 2018

I hate to say that, but the best solution I came up with, was to manually install the old packages:

But pydio-ui at least starts then.

@gerroon
Copy link

gerroon commented Aug 18, 2018

I see that might mess up my sys because I have couple apps uses gst. Thans for the recommendation.

@jkirk
Copy link
Author

jkirk commented Aug 19, 2018

Actually, libgststreamer v0.10 does not conflict with v1.00. You can have both libraries next to another.

Another workaround I tried was to create symlinks like sudo ln -s /usr/lib/x86_64-linux-gnu/libgstapp-1.0.so.0 /usr/lib/x86_64-linux-gnu/libgstapp-0.10.so.0. But this path is quite cumbersome because you have to find and symlink quite a few libraries.

@gerroon
Copy link

gerroon commented Aug 19, 2018

Ok thanks for the pointers, I will give it a try.

@jkirk
Copy link
Author

jkirk commented Aug 24, 2018

JFYI: pydio-sync starts but fine but when adding a workspace (with https), this is shown in the logs (and the connection to the workspace fails):

qt.network.ssl: QSslSocket: cannot resolve CRYPTO_num_locks                                                                                                  
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_id_callback                     
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_locking_callback                                                                                       
qt.network.ssl: QSslSocket: cannot resolve ERR_free_strings         
qt.network.ssl: QSslSocket: cannot resolve sk_new_null                                                                                                       
qt.network.ssl: QSslSocket: cannot resolve sk_push                  
qt.network.ssl: QSslSocket: cannot resolve sk_free                                                                                                           
qt.network.ssl: QSslSocket: cannot resolve sk_num                   
qt.network.ssl: QSslSocket: cannot resolve sk_pop_free                                                                                                       
qt.network.ssl: QSslSocket: cannot resolve sk_value                                   
qt.network.ssl: QSslSocket: cannot resolve SSL_library_init
qt.network.ssl: QSslSocket: cannot resolve SSL_load_error_strings
qt.network.ssl: QSslSocket: cannot resolve SSL_get_ex_new_index
qt.network.ssl: QSslSocket: cannot resolve SSLv2_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv3_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv2_server_method
qt.network.ssl: QSslSocket: cannot resolve SSLv3_server_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_server_method
qt.network.ssl: QSslSocket: cannot resolve X509_STORE_CTX_get_chain
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
qt.network.ssl: QSslSocket: cannot resolve SSLeay
qt.network.ssl: QSslSocket: cannot resolve SSLeay_version
qt.network.ssl: QSslSocket: cannot call unresolved function SSLeay
qt.network.ssl: QSslSocket: cannot call unresolved function CRYPTO_num_locks
qt.network.ssl: QSslSocket: cannot call unresolved function CRYPTO_set_id_callback
qt.network.ssl: QSslSocket: cannot call unresolved function CRYPTO_set_locking_callback
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function sk_num
QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)

I am still looking for a workaround for Debian/stretch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants