EVE Launcher for Linux


(Liquid Entropy) #144

Ubuntu 16.xx

Tried to follow the DL instructions and also DL my own wine, changed to my wine in the hamburger menu in the logging screen. Game will not launch after entering in account info.

Errors in the terminal when running the launcher script:
[0330/161122:WARNING:resource_bundle.cc(291)] locale_file_path.empty() for locale
Installed Qt WebEngine locales directory not found at location /home/evelauncher/translations/qtwebengine_locales. Trying application directory…
Qt WebEngine locales directory not found at location /home/evelauncher/qtwebengine_locales. Trying fallback directory… Translations MAY NOT not be correct.
[0330/161122:WARNING:resource_bundle.cc(291)] locale_file_path.empty() for locale
[S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.
[S_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local steamclient.so.

I DL the QT files and installed. Do I need steam to make this work?


(elitatwo) #145

Did you make your EVE account with steam? Then yes.

If not, you can ignore the warnings about Steam. Did you install mono-all?


(Liquid Entropy) #146

No I did not. I will investigate this. Ty


(elitatwo) #147

Here is what you need to do:

Debian, Ubuntu, and derivatives

Add the Mono Project GPG signing key and the package repository to your system (if you don’t use sudo, be sure to switch to root):

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
echo “deb http://download.mono-project.com/repo/debian wheezy main” | sudo tee /etc/apt/sources.list.d/mono-xamarin.list
sudo apt-get update

sudo apt-get install mono-devel mono-complete mono-dbg referenceassemblies-pcl ca-certificates-mono mono-xsp4 xsel xdotool


You can type this in a terminal and wait until it is complete.


(Eura) #148

Seems to be working on Ubuntu 18.04 beta.

Same SSL and Crypto library issues.

Also needed to install these including whatever Steam installs of 32 bit libraries.

sudo apt install libldap-2.4-2:i386
sudo apt install libpulse-dev:i386
sudo apt install libasound2-dev:i386

I also tried adding these but one of those two packages BROKE it (probably font). If you click on the EVE window after you select character it crashes.

sudo apx install libmpg123-dev:i386
sudo apx install libfreetype6-dev:i386

apt* copy paste protection


(Tommy Arrano) #149

o7 all

I cannot launch EvE with linux launcher.
Gentoo linux, Plasma Desktop, fresh installation.
I have these lines in terminal after running evelauncher.sh:

kde-open5: /stuff/evelauncher/evelauncher/./libQt5Core.so.5: version `Qt_5.9’ not found (required by kde-open5)

kde-open5: /stuff/evelauncher/evelauncher/./libQt5Core.so.5: version `Qt_5.9’ not found (required by /usr/lib64/libKF5KIOWidgets.so.5)

What I am doing wrong?


(Durarara Onnlin) #150

ο7 all :smiley:
for me the problem is the following
i open the client and when i click play nothing happens…
i run the client through terminal so i can see possible errors etc…
any1 had similar or the same problem??
thanks in advance :smiley:


(1eg01as) #151

url link in launcher/game not work


(Ban Mjolnir) #152

Tommy:

Your Plasma installation has newer versions of the QT library than the ones provided with the EVE launcher and they end up conflicting.
One workaround is to substitute the QT libraries in the evelauncher directory - copy from /usr/lib or usr/lib64 depending on where your distro puts them.
If the launcher itself updates in the future you will need to repeat the procedure.


(1eg01as) #153

i use symlinks to system Qt libs. 5.7 work fine. 5.9 segmentation at startup launcher


(RevBem) #154

I have followed the steps found here…https://wiki.eveuniversity.org/Installing_EVE_on_Linux but when I run the eve launcher nothing happens. No window, no errors, nothing. I did have to install the gtk module cause I was getting an error with that but now it just sits there.

Im running Ubuntu 18.04

Any ideas?


(Gharim Turen) #155

Maybe you have a look on this thread EVE Installing or here Some notes on Ubuntu 18.04 .


(Sabrina Winslow) #156

wanted to report some recent improvements I have noticed.

It used to be that I would have to fix system links for truetype, libcrypto, etc. after performing system updates on my Arch Linux machine. It appears that after running a full system update, this is no longer necessary for my specific use case and I can run evelauncher.sh after a full system update (pacman -Syy followed by pacman -Syu) without any further modifications.

I recently performed a clean installation of Arch on my chromebook (Acer C720, i3) and was able to get the AUR package for the Eve Launcher to work without any issues. I did have to change the display option to Fixed Window but I think that has more to do with my window manager (i3) than anything else. I also used to encounter bad crashing on my chromebook after playing for maybe ~30 minutes, but this no longer seems to be the case.

Things have definitely improved with the Eve Launcher for Linux and I want to thank the devs for everything they have done to improve the game for people who use Linux.

o7

  • Sabrina Winslow

(Dabljuh) #157

My problem still persists. Running the linux evelauncher, the download fails within seconds. The logfile mentioned isn’t helpful.


(Bastien Rotineque) #158

I was in the same problem, just install eve directly on WINE. worked for me first try


(Sabrina Winslow) #159

I started encountering crashes immediately after start-up after re-enabling sound. I’ve stopped using the launcher entirely and have had success using the following instructions, running Arch Linux and Wine Staging 3.9:

https://wiki.archlinux.org/index.php/User:Mcnster/EVE_Online

https://appdb.winehq.org/objectManager.php?sClass=version&iId=25823

I personally am not using a wineprefix considering EvE is the only thing I really run with wine, but after following all of the instructions on both pages, the game has been running with no issues (well, loglite crashes, but if the game works, I guess I don’t need logs).


(Sar Theron) #160

Debian / Ubuntu

Sharing my working setup on Debian stable. It should also work on Ubuntu and other derivatives.

Setup:

Install dependencies before running the launcher.

apt install wine64 libldap-2.4-2:i386 libssl1.0-dev

Download the launcher. Make .eve folder in your home directory and extract evelauncher.tar.gz into .eve folder.

The launcher will create symlinks after the first run, which would be broken, if you move or rename the folder. Don’t do it in order to avoid future problems.

cd ~/ && wget https://binaries.eveonline.com/evelauncher-1104891.tar.gz
mkdir .eve && cd .eve && tar -xf …/evelauncher-1104891.tar.gz

Run the launcher, open settings and under wine options leave everything unchecked.
bash .eve/evelauncher/evelauncher.sh

The launcher will download latest wine and setup wine environment for itself. System wide installed wine64 will cover other missing libraries and there is no need to link them to the launcher.

Using winehq-master and then leaving everything unchecked worked for me.

I am using x11 with i3 window manager, but it doesn’t matter which desktop environment you chose as long as you don’t have broken package dependencies.


(Fynn Saraki) #161

Installed EVE Launcher for Linux on Slackware 14.2 and it installed flawlessly. Logged in with no problems.

There are some issues with graphics. Most likely due to the integrated (substandard) video card on this machine - an ATI Radeon X1270. Poor rendering on ships, keepstar, no in-game video and approx. 40 fps. All objects in-game were black shadows - not playable. Adding a 2nd card and disabling this one should fix it so I can multibox for fleets.

Good stuff, CCP.

Thanks for the port.


(Dravick Afterthought) #162

I had similar problems on my 10-year-old PC running Mint 17, I fixed most of them (after consulting this forum) by disabling ‘Anti-aliasing’ in the ‘Graphics Content Settings’ of the in-game settings panel.


(Whitehound) #163

The default is to run with DirectX11. And as @Dravick_Afterthought has pointed out does it cause still a problem when anti-aliasing is enabled.

You can change it to run in DirectX9 in the launcher settings. This improves framerate and also allows for anti-aliasing at the cost of a little less visual finesse.