Evelaunsher.sh fails w/o any logs


(Kuro Shinjitsu) #1

My Eve just stopped starting since the last update.

The last time I had fixed it by linking the crpyto- and ssl-libs, but this time this didnt fixed it.
If I start eve it just does nothing, not a single line.
The cursor blinks in the first col of the next line and that’s it…

My OS is Linux Mint 18.1 Serena (64bit).

I would apprecciate any help, as I just got omega few days ago …

Thanks :slight_smile:

Hardware-Data:

H/W-Pfad       Device     Klasse         Beschreibung
=====================================================
                          system         80JV (LENOVO_MT_80JV_BU_idea_FM_Lenovo U41-70)
/0                        bus            Lenovo U41-70
/0/0                      memory         128KiB BIOS
/0/7                      processor      Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz
/0/7/8                    memory         32KiB L1 Cache
/0/7/9                    memory         256KiB L2 Cache
/0/7/a                    memory         3MiB L3 Cache
/0/6                      memory         32KiB L1 Cache
/0/b                      memory         8GiB Systemspeicher
/0/b/0                    memory         8GiB SODIMM DDR3 Synchron 1600 MHz (0,6 ns)
/0/100                    bridge         Broadwell-U Host Bridge -OPI
/0/100/2                  display        Broadwell-U Integrated Graphics
/0/100/3                  multimedia     Broadwell-U Audio Controller
/0/100/14                 bus            Wildcat Point-LP USB xHCI Controller
/0/100/14/0    usb3       bus            xHCI Host Controller
/0/100/14/1    usb2       bus            xHCI Host Controller
/0/100/14/1/1             input          USB-compliant keyboard
/0/100/14/1/2             input          USB Gaming Mouse
/0/100/14/1/4             multimedia     Lenovo EasyCamera
/0/100/16                 communication  Wildcat Point-LP MEI Controller #1
/0/100/1b                 multimedia     Wildcat Point-LP High Definition Audio Controller
/0/100/1c                 bridge         Wildcat Point-LP PCI Express Root Port #1
/0/100/1c.2               bridge         Wildcat Point-LP PCI Express Root Port #3
/0/100/1c.2/0  wlp2s0     network        BCM4352 802.11ac Wireless Network Adapter
/0/100/1c.3               bridge         Wildcat Point-LP PCI Express Root Port #4
/0/100/1c.3/0  enp3s0     network        RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
/0/100/1c.4               bridge         Wildcat Point-LP PCI Express Root Port #5
/0/100/1c.4/0             display        GM108M [GeForce 940M]
/0/100/1d                 bus            Wildcat Point-LP USB EHCI Controller
/0/100/1d/1    usb1       bus            EHCI Host Controller
/0/100/1d/1/1             bus            USB-Hub
/0/100/1f                 bridge         Wildcat Point-LP LPC Controller
/0/100/1f.2               storage        Wildcat Point-LP SATA Controller [AHCI Mode]
/0/100/1f.3               bus            Wildcat Point-LP SMBus Controller
/0/100/1f.6               generic        Wildcat Point-LP Thermal Management Controller
/0/1           scsi0      storage
/0/1/0.0.0     /dev/sda   disk           256GB RTNMB256VBM8EWXL
/0/1/0.0.0/2   /dev/sda2  volume         488MiB EFI partition
/0/1/0.0.0/3   /dev/sda3  volume         237GiB EFI partition
/1                        power          Smart Battery
/2                        power          TBD by ODM

And lscpi says following for the active graphiccard:
04:00.0 3D controller [0302]: NVIDIA Corporation GM108M [GeForce 940M] [10de:1347] (rev a2)
Subsystem: Lenovo GM108M [GeForce 940M] [17aa:3821]
Kernel driver in use: nvidia


(Lucius Kalkoken) #2

See EVE Launcher version 1222103

Because of the update SSL broke again. There is a log that it writes to, check that, something like /home/username/.local/share/CCP/EVE/Launcher/launcherlog-2017.12.19-18.50.21.936.txt


(Kuro Shinjitsu) #3

Thanks for the quick reply,

Thanks for pointing out to the location of the logs.
(thought all the other penguin-capsulers get this in their terminal or loglite).

And yes, I got the same error like in that thread (just didnt know before), but unfortunately your fixer-script doesn’t help me here .-.


(Lucius Kalkoken) #4

You did edit the script with the right paths? Make sure the files you’re symlinking actually exist.


(Kuro Shinjitsu) #5

Whoopsie,
didn’t know you can symlink to non-existing files o:

"The files I linked to before (*.1.0.2, worked till last update) are gone, now I use the libssl provided by wine

I adjusted them to *.1.0.2, as this was my fix-after-updates-script before:

ln -s /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.2 libcrypto.so
ln -s /usr/lib/x86_64-linux-gnu/libssl.so.1.0.2 libssl.so

Therefore I tried this additional commands:

ln -s /usr/lib64/libssl.so.1.0.2 libssl.so.1.0.2
ln -s /usr/lib64/libcrypto.so.1.0.2 libcrypto.so.1.0.2

And then this, as above didn’t worked):

ln -s /usr/lib64/libssl.so.1.0.2 libssl.so.1.0.0
ln -s /usr/lib64/libcrypto.so.1.0.2 libcrypto.so.1.0.0

Didn’t think about checking if these libs are still there…
Somehow they are gone and now I only got version 1.1

Then I think, okay, just try it with version 1.1:

rm libssl.so*
rm libcrypto.so*
ln -s /usr/lib64/libssl.so.1.1 libssl.so
ln -s /usr/lib64/libssl.so.1.1 libssl.so.1.0.0
ln -s /usr/lib64/libssl.so.1.1 libssl.so.1.1
ln -s /usr/lib64/libcrypto.so.1.1 libcrypto.so
ln -s /usr/lib64/libcrypto.so.1.1 libcrypto.so.1.1
ln -s /usr/lib64/libcrypto.so.1.1 libcrypto.so.1.0.0

But still just a black screen.

As I’m somehow unable to install the 1.0.0 or 1.0.2, i tried locating the libs and now just link to the libs of my wine-staging

  • all commands are executed in the evelaunsher-directory

EDIT:
To actually fix the Issue, I located the same libraries on my drive

locate libssl.so.1.0.0
locate libcrypto.so.1.0.0

Then I symlinked the files into my evelauncher-dir.
My system-libs didn’t had them anymore, but whine had (and steam, too)

Thank you for pointing me in the right direction.

Fly safe o7


(Rhyme Bittern) #6

Can you share the commands that actually solved your issue? I’m struggling with this on my Ubuntu to no avail.


(Yossarian Otomeya) #7

Follow this section: https://wiki.eveuniversity.org/Installing_EVE_on_Linux#Incompatible_OpenSSL_library


(Rhyme Bittern) #8

Thanks for the link, but it does not work for me.
The ssl and crypto links were created and they are not broken, but I still get the following errors:

2017-12-21T17:27:57.189Z qt.network.ssl warning QSslSocket: cannot resolve SSLv2_client_method
2017-12-21T17:27:57.189Z qt.network.ssl warning QSslSocket: cannot resolve SSLv2_server_method
2017-12-21T17:27:57.248Z default warning Installed Qt WebEngine locales directory not found at location /home/yotam/הורדות/evelauncher/translations/qtwebengine_locales. Trying application directory…
2017-12-21T17:27:57.248Z default warning Qt WebEngine locales directory not found at location /home/yotam/הורדות/evelauncher/qtwebengine_locales. Trying fallback directory… Translations MAY NOT not be correct.
2017-12-21T17:28:01.513Z default error Couldn’t open index file “/home/yotam/.eve//ResFiles/56/5610a6eb8b5a4975_2d75e946e3d61224690c0fd3f80d5966”
2017-12-21T17:28:01.605Z default warning Update failed for Tranquility with error: 5
2017-12-21T17:28:02.365Z default error Couldn’t open index file “/home/yotam/.eve//ResFiles/56/5610a6eb8b5a4975_1a90d14a174be46336f04c5d8fa1b7c8”
2017-12-21T17:28:02.465Z default warning Update failed for Singularity with error: 5

Everything worked just fine until several days ago. Any ideas?


(Rhyme Bittern) #10

Downloading the 8gb resfiles solved the issue for me.


(system) #12

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.