These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Linux

 
  • Topic is locked indefinitely.
 

Installing openssl completely broke my linux launcher
Author
Previous Topic Next Topic
I'mNotAnAlienISwear WhosUrLeader
Sebiestor Tribe
Minmatar Republic
#1 - 2017-01-24 22:14:57 UTC
Hi,
I had the linux launcher with wine working on my computer until about a week ago. I installed openssl (manually, cause I thought I needed it to fix a different bug) and now the launcher itself won't open Here's what I got from the logs.

2017-01-24T16:59:36.656Z    qt.network.ssl    warning    QSslSocket: cannot resolve CRYPTO_num_locks
2017-01-24T16:59:36.656Z    qt.network.ssl    warning    QSslSocket: cannot resolve CRYPTO_set_id_callback
2017-01-24T16:59:36.656Z    qt.network.ssl    warning    QSslSocket: cannot resolve CRYPTO_set_locking_callback
2017-01-24T16:59:36.657Z    qt.network.ssl    warning    QSslSocket: cannot resolve ERR_free_strings
2017-01-24T16:59:36.657Z    qt.network.ssl    warning    QSslSocket: cannot resolve EVP_CIPHER_CTX_cleanup
2017-01-24T16:59:36.657Z    qt.network.ssl    warning    QSslSocket: cannot resolve EVP_CIPHER_CTX_init
2017-01-24T16:59:36.657Z    qt.network.ssl    warning    QSslSocket: cannot resolve sk_new_null
2017-01-24T16:59:36.657Z    qt.network.ssl    warning    QSslSocket: cannot resolve sk_push
2017-01-24T16:59:36.657Z    qt.network.ssl    warning    QSslSocket: cannot resolve sk_free
2017-01-24T16:59:36.657Z    qt.network.ssl    warning    QSslSocket: cannot resolve sk_num
2017-01-24T16:59:36.657Z    qt.network.ssl    warning    QSslSocket: cannot resolve sk_pop_free
2017-01-24T16:59:36.657Z    qt.network.ssl    warning    QSslSocket: cannot resolve sk_value
2017-01-24T16:59:36.657Z    qt.network.ssl    warning    QSslSocket: cannot resolve SSL_library_init
2017-01-24T16:59:36.657Z    qt.network.ssl    warning    QSslSocket: cannot resolve SSL_load_error_strings
2017-01-24T16:59:36.657Z    qt.network.ssl    warning    QSslSocket: cannot resolve SSL_get_ex_new_index
2017-01-24T16:59:36.657Z    qt.network.ssl    warning    QSslSocket: cannot resolve SSLv2_client_method
2017-01-24T16:59:36.657Z    qt.network.ssl    warning    QSslSocket: cannot resolve SSLv3_client_method
2017-01-24T16:59:36.657Z    qt.network.ssl    warning    QSslSocket: cannot resolve SSLv23_client_method
2017-01-24T16:59:36.657Z    qt.network.ssl    warning    QSslSocket: cannot resolve SSLv2_server_method
2017-01-24T16:59:36.657Z    qt.network.ssl    warning    QSslSocket: cannot resolve SSLv3_server_method
2017-01-24T16:59:36.657Z    qt.network.ssl    warning    QSslSocket: cannot resolve SSLv23_server_method
2017-01-24T16:59:36.657Z    qt.network.ssl    warning    QSslSocket: cannot resolve X509_STORE_CTX_get_chain
2017-01-24T16:59:36.657Z    qt.network.ssl    warning    QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
2017-01-24T16:59:36.657Z    qt.network.ssl    warning    QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
2017-01-24T16:59:36.657Z    qt.network.ssl    warning    QSslSocket: cannot resolve SSLeay
2017-01-24T16:59:36.658Z    qt.network.ssl    warning    QSslSocket: cannot resolve SSLeay_version


I removed openssl after I installed it manually, but I still get those errors.

In my evelauncher folder, I have put the libssl.s0.1.0.0 and libcrypt.so.1.0.0 files, but that doesn't help. I've also tried starting fresh and instead doing a symbolic link to the /usr/whateverthepathis/x86-64linux place where those files should be normally, but that also didn't work.

Interestingly, when I first encountered the bug, running the launcher from my file explorer with the "run in terminal" option gave me this error: ATTENTION: default value of option force_s3tc_enable overridden by environment.

since rebooting my computer, I have not been able to reproduce that message.

This seems like it should be an easy fix for anyone who knows linux well, but I don't. I know for a fact that eve can run on this distro and hardware, so I just need to un-break openssl.

Thanks a bunch ahead of time. Also, I can post any additional info if needed.
I'mNotAnAlienISwear WhosUrLeader
Sebiestor Tribe
Minmatar Republic
#2 - 2017-01-26 22:20:48 UTC
Ok, I was able to resolve my problem slightly. There was a problem with my libssl.so and other files. I was able to copy known good ones from my laptop that can run eve. I also made absolutely sure they were going to be used by renaming them to libssl.so without the version number at the end, although a symbolic link will probably work too (like what the solution posted before for this problem did). The launcher seems to be working, but is redownloading some things, except the launcher itself doesn't say it, I'm just reading the log files as they are written.

TL;DR just be absolutely sure that you have good libssl.so.1.x.x and libcrypto.so.1.x.x files, and make sure you have them renamed or symbolically linked to libssl.so etc.
Tarakona Nui
Spelunkers
#3 - 2017-03-04 06:21:28 UTC
I'mNotAnAlienISwear WhosUrLeader wrote:

TL;DR just be absolutely sure that you have good libssl.so.1.x.x and libcrypto.so.1.x.x files, and make sure you have them renamed or symbolically linked to libssl.so etc.

Thank you! For days I've been baffled about why my evelauncher.sh just sat there failing silently. It didn't occur to me to look at the logs, nor that my compiling and installing a new openssl would have anything to do with it. I'd even gone to the extent of deleting every file on my system that had to do with either EVE, CCP or Wine, and rebuilding them one at a time from scratch.

Renaming my /usr/local/lib to /usr/local/lib-hide was enough - there wasn't much in it except for the new libssl and libcrypto stuff.

Thank you!