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

 
 

Fedora 26 - Launcher freezes

Author
Calebus Phobeus
Eternal Seekers of Darkness
#1 - 2017-07-22 07:31:37 UTC
I just upgraded to a new installed Fedora 26, taking the launcher with me. When starting it the original way, I am getting the following error:
Quote:
This application failed to start because it could not find or load the Qt platform plugin "xcb"
in "".

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, xcb.

Reinstalling the application may fix this problem.
Aborted


Reading around in the forum, it seems like using the shell script shall fix this for most people. However, when doing this, the launcher just starts and going into wait for some reason:
Quote:
[...]
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigaction(SIGCHLD, {sa_handler=0x55b8e3f8e6a0, sa_mask=[], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7f7661aa46f0}, {sa_handler=0x55b8e3f8e6a0, sa_mask=[], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7f7661aa46f0}, 8) = 0
close(4) = 0
read(3, ".\n", 128) = 2
read(3, "", 128) = 0
close(3) = 0
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=26972, si_uid=1000, si_status=0, si_utime=0, si_stime=0} ---
wait4(-1, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], WNOHANG, NULL) = 26972
wait4(-1, 0x7ffd77a64710, WNOHANG, NULL) = -1 ECHILD (No child processes)
rt_sigreturn({mask=[]}) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigaction(SIGINT, {sa_handler=0x55b8e3f8b150, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7f7661aa46f0}, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7f7661aa46f0}, 8) = 0
rt_sigaction(SIGINT, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7f7661aa46f0}, {sa_handler=0x55b8e3f8b150, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7f7661aa46f0}, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
read(255, "tmp=\"${dirname#?}\"\n\nif [ \"${dirn"..., 312) = 238
rt_sigprocmask(SIG_BLOCK, [INT CHLD], [], 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [INT CHLD], 8) = 0
rt_sigprocmask(SIG_SETMASK, [INT CHLD], NULL, 8) = 0
clone(child_stack=NULL, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7f7662459e10) = 26973
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigprocmask(SIG_


It seems never to return from this. Any idea, what this might be?
Merkwurkdigliebe
Vigrior
#2 - 2017-07-22 21:42:05 UTC  |  Edited by: Merkwurkdigliebe
Hello!

So the xcb bit was the only relevant error the rest is debug info with no actual errors in it. The xcb error means the launcher can't find the Qt5 libs. Probably when you updated fedora either the symlink to xcb/qt libs was removed or the libs themselves were.

Reinstalling the 32bit compatibility for your video drivers with out using the distro specific package you normally use will fix this (until the next system mesa update) so if that gets you working check /usr/lib/i386-linux-gnu/ and ldconfig -p | grep Qt before and after so you can compare and figure out which symlink you were missing. Or just install qt5 for i386 arch, if they are gone. Remember when installing you need the i386 qt libs even tho your system is 64 bit and you need the opengl 32 bit compatibility libs for your video too... Was that redundant? Yes... yes it was.

Try that and if it doesn't work post your errors from .local/share/CCP/EVE/Launcher/launcher*.txt as that's going to have the most useful info.

Good luck!
M
Calebus Phobeus
Eternal Seekers of Darkness
#3 - 2017-07-23 10:14:36 UTC
Its a fresh installation, not a upgrade. So I think it is more likely that some package might be missing than actually some symbolic link might be wrong. I am also pretty sure that the GPU drivers and libs are setup correctly as other stuff is working fine. My best guess is that it is related to QT as the only other issue I found so far is by Albion Online that is also using a qt launcher that is freezing.

I installed all possible qt5 libs so far as well.

The point to the log file was nice, I wasn't aware that it exist. Nothing suspicious in there either than these lines at the end:
Quote:
2017-07-23T01:19:37.395Z qt.network.ssl warning QSslSocket: cannot resolve CRYPTO_num_locks
2017-07-23T01:19:37.395Z qt.network.ssl warning QSslSocket: cannot resolve CRYPTO_set_id_callback
2017-07-23T01:19:37.395Z qt.network.ssl warning QSslSocket: cannot resolve CRYPTO_set_locking_callback
2017-07-23T01:19:37.395Z qt.network.ssl warning QSslSocket: cannot resolve ERR_free_strings
2017-07-23T01:19:37.395Z qt.network.ssl warning QSslSocket: cannot resolve EVP_CIPHER_CTX_cleanup
2017-07-23T01:19:37.395Z qt.network.ssl warning QSslSocket: cannot resolve EVP_CIPHER_CTX_init
2017-07-23T01:19:37.395Z qt.network.ssl warning QSslSocket: cannot resolve sk_new_null
2017-07-23T01:19:37.395Z qt.network.ssl warning QSslSocket: cannot resolve sk_push
2017-07-23T01:19:37.396Z qt.network.ssl warning QSslSocket: cannot resolve sk_free
2017-07-23T01:19:37.396Z qt.network.ssl warning QSslSocket: cannot resolve sk_num
2017-07-23T01:19:37.396Z qt.network.ssl warning QSslSocket: cannot resolve sk_pop_free
2017-07-23T01:19:37.396Z qt.network.ssl warning QSslSocket: cannot resolve sk_value
2017-07-23T01:19:37.396Z qt.network.ssl warning QSslSocket: cannot resolve SSL_library_init
2017-07-23T01:19:37.396Z qt.network.ssl warning QSslSocket: cannot resolve SSL_load_error_strings
2017-07-23T01:19:37.396Z qt.network.ssl warning QSslSocket: cannot resolve SSL_get_ex_new_index
2017-07-23T01:19:37.396Z qt.network.ssl warning QSslSocket: cannot resolve SSLv2_client_method
2017-07-23T01:19:37.396Z qt.network.ssl warning QSslSocket: cannot resolve SSLv23_client_method
2017-07-23T01:19:37.396Z qt.network.ssl warning QSslSocket: cannot resolve SSLv2_server_method
2017-07-23T01:19:37.396Z qt.network.ssl warning QSslSocket: cannot resolve SSLv23_server_method
2017-07-23T01:19:37.396Z qt.network.ssl warning QSslSocket: cannot resolve X509_STORE_CTX_get_chain
2017-07-23T01:19:37.397Z qt.network.ssl warning QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
2017-07-23T01:19:37.397Z qt.network.ssl warning QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
2017-07-23T01:19:37.397Z qt.network.ssl warning QSslSocket: cannot resolve SSLeay
2017-07-23T01:19:37.397Z qt.network.ssl warning QSslSocket: cannot resolve SSLeay_version
Merkwurkdigliebe
Vigrior
#4 - 2017-07-23 19:44:56 UTC
Ahh so those SSL errors are a common issue after launcher updates. There are supposed to be symlinks in your evelauncher directory pointing to older ssl libs your system maybe doesnt have by default...

I got them manually as you see below, but apparently libssl1.0.2 is compatible if you can find it in your package manager use that then link their location under /usr/lib to ~/evelauncher w/ out the version numbers.

cd ~/eveluancher
wget http://ftp.us.debian.org/debian/pool/main/o/openssl/libssl1.0.0_1.0.1t-1+deb8u6_amd64.deb
dpkg --fsys-tarfile libssl1.0.0_1.0.1t-1+deb8u6_amd64.deb | tar xOf - ./usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 > libssl.so
dpkg --fsys-tarfile libssl1.0.0_1.0.1t-1+deb8u6_amd64.deb | tar xOf - ./usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 > libcrypto.so
rm libssl1.0.0_1.0.1t-1+deb8u6_amd64.deb
cp libssl.so ~/; cp libcrypto.so ~/;

A fellow on the forums gave us a handy script for creating the symlinks:

#!/bin/bash

CRYPTLIB="/usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0"
SSLLIB="/usr/lib/x86_64-linux-gnu/libssl.so.1.0.0"
# Change the paths to wherever you have installed evelauncher
EVECRYPT="/home/user/evelauncher/libcrypt.so"
EVESSL="/home/user/evelauncher/libssl.so"

# Check if libcrypt.so exist in evelauncher directory, if not create it.
if [ ! -f "$EVECRYPT" ] ; then
ln -s "$CRYPTLIB" "$EVECRYPT"
fi

# Check if libssl.so exist in evelauncher directory, if not create it.
if [ ! -f "$EVESSL" ] ; then
ln -s "$SSLLIB" "$EVESSL"
fi

# EOF


Good Luck
M