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

Forum Index

EVE Forums » EVE Technology and Research Center » Linux » To whom it may concern - Launer not launching anymore

Topic is locked indefinitely.

To whom it may concern - Launer not launching anymore
Author

Previous Topic Next Topic

Mister Ripley

Ministry of War

Amarr Empire

Likes received: 251

#1 - 2016-11-19 14:52:51 UTC | Edited by: Mister Ripley

I'm on Debian testing (gnome) and I just noticed that updating gstreamer1.0-plugins-bad from 1.10.0-1 to 1.10.1-1 pulls libssl1.1 version 1.1.0c-1.
This breaks the launcher since it seems to break qt network stuff.


2016-11-19T15:25:39.460Z    qt.network.ssl    warning    QSslSocket: cannot resolve CRYPTO_num_locks
2016-11-19T15:25:39.461Z    qt.network.ssl    warning    QSslSocket: cannot resolve CRYPTO_set_id_callback
2016-11-19T15:25:39.461Z    qt.network.ssl    warning    QSslSocket: cannot resolve CRYPTO_set_locking_callback
2016-11-19T15:25:39.461Z    qt.network.ssl    warning    QSslSocket: cannot resolve ERR_free_strings
2016-11-19T15:25:39.461Z    qt.network.ssl    warning    QSslSocket: cannot resolve EVP_CIPHER_CTX_cleanup
2016-11-19T15:25:39.461Z    qt.network.ssl    warning    QSslSocket: cannot resolve EVP_CIPHER_CTX_init
2016-11-19T15:25:39.461Z    qt.network.ssl    warning    QSslSocket: cannot resolve sk_new_null
2016-11-19T15:25:39.461Z    qt.network.ssl    warning    QSslSocket: cannot resolve sk_push
2016-11-19T15:25:39.461Z    qt.network.ssl    warning    QSslSocket: cannot resolve sk_free
2016-11-19T15:25:39.461Z    qt.network.ssl    warning    QSslSocket: cannot resolve sk_num
2016-11-19T15:25:39.462Z    qt.network.ssl    warning    QSslSocket: cannot resolve sk_pop_free
2016-11-19T15:25:39.462Z    qt.network.ssl    warning    QSslSocket: cannot resolve sk_value
2016-11-19T15:25:39.462Z    qt.network.ssl    warning    QSslSocket: cannot resolve SSL_library_init
2016-11-19T15:25:39.462Z    qt.network.ssl    warning    QSslSocket: cannot resolve SSL_load_error_strings
2016-11-19T15:25:39.462Z    qt.network.ssl    warning    QSslSocket: cannot resolve SSL_get_ex_new_index
2016-11-19T15:25:39.462Z    qt.network.ssl    warning    QSslSocket: cannot resolve SSLv2_client_method
2016-11-19T15:25:39.462Z    qt.network.ssl    warning    QSslSocket: cannot resolve SSLv3_client_method
2016-11-19T15:25:39.462Z    qt.network.ssl    warning    QSslSocket: cannot resolve SSLv23_client_method
2016-11-19T15:25:39.462Z    qt.network.ssl    warning    QSslSocket: cannot resolve SSLv2_server_method
2016-11-19T15:25:39.463Z    qt.network.ssl    warning    QSslSocket: cannot resolve SSLv3_server_method
2016-11-19T15:25:39.463Z    qt.network.ssl    warning    QSslSocket: cannot resolve SSLv23_server_method
2016-11-19T15:25:39.463Z    qt.network.ssl    warning    QSslSocket: cannot resolve X509_STORE_CTX_get_chain
2016-11-19T15:25:39.463Z    qt.network.ssl    warning    QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
2016-11-19T15:25:39.463Z    qt.network.ssl    warning    QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
2016-11-19T15:25:39.463Z    qt.network.ssl    warning    QSslSocket: cannot resolve SSLeay
2016-11-19T15:25:39.463Z    qt.network.ssl    warning    QSslSocket: cannot resolve SSLeay_version

You will see a bunch of this error messages at the end of

launcherlog-"date".txt

~/.local/share/CCP/EVE/Launcher

I fixed it by downgrading, but I'm not sure how to handle this issue in the future because gstreamer1.0-plugins-bad is required by some gnome components What?

Hooloovoo Blue

Aliastra

Gallente Federation

Likes received: 2

#2 - 2016-11-28 14:51:20 UTC

Thanks for posting this - I didn't know about the existence of the log files, all I could see under strace and ltrace was the networking calls hanging.

I upgraded my Debian unstable install for the first time in weeks yesterday and hit this issue. I've resolved it by copying libssl1.0.0.so and libcrypto1.0.0.so from an un-updated machine, and dropped them into the evelauncher folder - you'll need to rename or symlink them to libssl.so and libcrypto.so


Mister Ripley Ministry of War Amarr Empire Likes received: 251	#3 - 2016-11-28 19:18:21 UTC Thank you for the hint with copy to launcher folder. For everyone having the same problem on Debian testing: libssl.so.1.0.2 and libcrypto.so.1.0.2 are in /usr/lib/x86_64linux-gnu/ Maybe CCP Snorlax can include it in the launcher files. I'll mail him and ask.

SQUAD V Northern Coalition. 7
Ailatan SQUAD V Northern Coalition. Likes received: 7	#4 - 2016-11-29 14:49:45 UTC Thanks for solution!

E.X.A.L.T.E.D The Initiative. 0
Coldren Kray E.X.A.L.T.E.D The Initiative. Likes received: 0	#5 - 2016-11-30 10:29:23 UTC thx is working :)

Ant4r3s

Rock n Goo

Likes received: 0

#6 - 2016-11-30 19:39:20 UTC

easy fix for those affected without messing up your distribution:
download libssl-1.0.0 (eg from here:https://packages.debian.org/jessie/amd64/libssl1.0.0/download)
use midnight commander(mc) or another tool to unpack libssl and libcrypto into the evelauncher folder. since the shellscript sets LD_LIBRARY_PATH, the copied version takes precedence over the installed version)
you find the libs in the deb-archive under CONTENT/usr/lib/x86_64-linux-gnu/

Sebiestor Tribe 474
Mr M Sebiestor Tribe Likes received: 474	#7 - 2016-12-07 16:31:18 UTC I had this problem too. Copying and renaming libssl.so.1.0.2 and libcrypto.so.1.0.2 to the EVE launcher folder was enough. Share your experience Write for the EVE Tribune www.eve-tribune.com

Mister Ripley

Ministry of War

Amarr Empire

Likes received: 251

#8 - 2016-12-08 15:29:25 UTC | Edited by: Mister Ripley

I had to do it again after the recent launcher update. It seems to delete this files on update. So better copy libssl.so.1.0.2 and libcrypto.so.1.0.2 somewhere one folder above or something like that to fix it again without looking for the files every time.

Sadly I got no answer so far from CCP Snorlax if he could include the files in the launcher download. Sad

Roesjka

The Last Solution Inc

Likes received: 7

#9 - 2016-12-09 18:58:14 UTC | Edited by: Roesjka

Ok to summarize steps to be taken sofar when on Debian Testing/Stretch and using wine-staging:

Check if you have still installed libssl1.0.2, normally libssl1.0.2_1.0.2j-4 should still be installed,
otherwise reinstall it. It is still in the Testing/Stretch repo's.

Make a symlinks in the evelauncher directory:
ln -s /usr/lib/x86_64-linux-gnu/libssl.so.1.0.2 libssl.so
ln -s /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.2 libcrypto.so

In case you are running into the wineserver mismatch versions rename SharedCache/wine/bin/wineserver to wineserver.org or just remove it.

I can now launch and run EVE with my custom wine-staging 1.9.23.

Thx guys for giving me the pointers to get it working again.

Cheers

Cheers,

Retired UNIX/Linux IT Specialist.

AsRock 990FX Extreme4, FX-8320, 16GB mem, GTX 1070

y50-70, i7, 16GB mem, GTX 860M

Both running Debian stretch 64bit

The Scope Gallente Federation 0
Orbonius Primus The Scope Gallente Federation Likes received: 0	#10 - 2016-12-13 16:15:22 UTC Thank you guys for your write-up here. I've been struggling with this bug since my last update and now I finally have it working. The key point I was missing was creating the naming links between the libraries. Cheers

V0LTA WE FORM V0LTA 51
MachineOfLovingGrace V0LTA WE FORM V0LTA Likes received: 51	#11 - 2016-12-22 22:09:43 UTC Thanks a lot guys, I don't think I would have found this on my own!

Linux

Ministry of War

Amarr Empire

Aliastra

Gallente Federation

SQUAD V

Northern Coalition.

E.X.A.L.T.E.D

The Initiative.

Rock n Goo

Sebiestor Tribe

The Last Solution Inc

The Scope

Gallente Federation

V0LTA

WE FORM V0LTA