Installing EVE on Linux: Difference between revisions

 

== Options to run a client on Linux ==

=== Squirrel launcher ===  

The current launcher (december 2023, based on squirrel) unofficial channel on discord:

[https://discord.com/channels/940573867192221696/1096046348421312574 Official Eve Online Discord server, new launcher channel, linux thread]

[https://forums.eveonline.com/t/recap-of-vanguard-on-linux-after-first-strike/432438 Eve Forums] Excelent write up from Katrina Bekers:

A. Use Steam, by opting-in the Beta branch and the code “TheInvitation” (case sensitive), installing the launcher from Steam, bypassing Squirrel altogether.

B. Manually extract the launcher package (“nupkg”, which is just a zip archive), and put it where it can be correctly run by WINE/Proton. Use this URL, modifying the version number adequately:

https://launcher.ccpgames.com/eve-online/release/win32/x64/eve-online-1.1.0-full.nupkg 3

C. Use [[Linux#Lutris|Lutris]], which implements a workaround for the “run as Administrator” default behavior in WINE/Proton, thus letting Squirrel do its job, see install notes.

D. Get the Squirrel installer and modify the Setup file with a binary editor so that the check for Administrator is reversed, and the installer proceeds if the user has Administrator privileges. smurftek: If you want to use the beta launcher under wine / proton without going through steam or having to change a bunch of settings, edit the binary and at address 00407436 replace it with “b8 01 00 00 00” and presto the launcher will work anywhere.

=== 'Old launcher' ===

 

A. Use Steam

 

B. Use [[Linux#Lutris|Lutris]]

[https://lutris.net/ Lutris] is a gaming platform for Linux. It offers Wine builds that are pre-configured for specific games, and allows for a graphical installation of various games and applications. Those that are unable to use the methods above, or are weary on the process, may find this solution more viable.

 

 

 

== Whey back when we had a native launcher & other problems ==

While Linux is not ''officially'' supported by CCP, a side project by '''CCP Snorlax''' has yielded a native Linux application that downloads a prebundled version of [https://www.winehq.org/ Wine] (also built by CCP Snorlax) which allows Linux to run the EVE launcher more easily. The launcher requires a <span style="color:yellow">'''64-bit'''</span> installation of Linux, but should work with most distributions.

Alternatively, for a more visual installation and cleaner management of multiple WINEPATHs, you can use [[Linux#Lutris|Lutris]].

Native Linux launcher has been [https://forums.eveonline.com/t/linux-launcher-key-details/159751 retired]. Recommended solution for running EVE on Linux is Steam/Proton

:''Much of this guide is adapted from the official forum post by CCP Snorlax, which can be found [https://forums.eveonline.com/t/eve-launcher-for-linux/7286 here]. Questions about the information found in this article are best asked on the [https://forums.eveonline.com/c/technology-research/linux official EVE forums]''.

# Create a symbolic link (symlink) to the script in the user binaries folder

#: {{code|sudo ln -s {{Color|green|/Path/To/}}evelauncher.sh /usr/bin/evelauncher}}

# And make it executable

#: {{code|sudo chmod u+x /usr/bin/evelauncher}}

#: {{code|wget <nowiki>https://wiki.eveuniversity.org/images/a/af/Evelauncher.png</nowiki>}}

#: {{code|sudo mv Evelauncher.png /usr/share/pixmaps/}}

#: {{code|sudo edit /usr/share/applications/eve.desktop}}

# Insert the following text and then save it:

# Run the game through the newly-created launcher shortcut!

The copy of wine bundled with the launcher is quite outdated, but thankfully you can use your distribution's own wine runtime instead which gives access to things like DirectX11 support.

# Reopen the launcher and start the game as normal.

The EVE launcher requires the 1.0.x version of the openssl library in order to function, however, some newer versions of Linux distributions and those that use rolling releases include the 1.1.x version by default (this will be evident by the launcher simply not appearing at all when the script is run), so some extra steps to install the older compatibility library may be necesssary.

# Download the older library from your distribution's repos

# Add symbolic links to the libraries in the launcher's folder

This should correct the issue temporarily, but the symlinks will be removed when the launcher is updated. A solution to this is to make your own script which checks for the existence of the symlinks, remakes them if they are missing and then triggers the launcher's script.

:'''Note:''' The wrapper script cannot be located in the launcher's own folder, or it will be deleted when the launcher updates.

#: {{code|$EDITOR {{Color|green|/Path/To/Wrapper/}}evewrapper.sh}}

#: {{code|sudo ln -s {{Color|green|/Path/To/Wrapper/}}evewrapper.sh /usr/bin/evelauncher}}

==== Qt dependencies ====

In some rare instances on Ubuntu, you may be lacking the required Qt dependences for the launcher, This will manifest as some QT files not be located and the launcher window opening but not displaying anything. <br/>

Instructions for this install are taken from here: https://wiki.qt.io/Install_Qt_5_on_Ubuntu

#: '''Note:''' These can be put wherever the user prefers, but the home directory <code>~/</code> is recommended.

#: {{code|wget http://download.qt.io/official_releases/qt/5.7/5.7.0/qt-opensource-linux-x64-5.7.0.run}}

<br>

Evelauncher comes with its own libxcb. In some instances it fails to find xcb in its launch directory as well as to find libxcb installed in the system. This is indicated by message in console:<br>

 

To solve this problem just delete all files located in the directory of eve launcher, that have "libxcb" as part of their names.

 

 

 

:{{code|/bin/sh: {{Color|orange|warning}}: shell level (1000) too high, resetting to 1}} <br>

 

 

:{{code|#!/bin/sh <br>{{Color|green|appname<nowiki>=</nowiki>"evelauncher"<br>}}<br>{{Color|green|dirname<nowiki>=</nowiki>$(dirname "$(readlink -f "$BASH_SOURCE")")}}<br>tmp<nowiki>=</nowiki>"${dirname#?}"<br><br>if [ "${dirname%$tmp}" !<nowiki>=</nowiki> "/" ]; then<br>dirname<nowiki>=</nowiki>"$PWD/$dirname"<br>fi<br><br>LD_LIBRARY_PATH<nowiki>=</nowiki>"$dirname:$LD_LIBRARY_PATH"<br>export LD_LIBRARY_PATH<br>export QTDIR<nowiki>=</nowiki>$dirname<br>export QT_PLUGIN_PATH<nowiki>=</nowiki>$dirname/plugins<br>"$dirname/$appname" "$@"}} <br>

:'''Note:''' The first change is necessary only if you choose to give your soft link a different name.

 

 

 

 

:{{code|user@localhost<nowiki> > ./evelauncher.sh</nowiki><br>...<br>{{Color|orange|Invalid MIT-MAGIC-COOKIE-1}} }}<br>

 

As explained [https://unix.stackexchange.com/a/10126/29963 here], an X program needs (1) the address of the display (typically ":0") and (2) the password for the display. The second requirement is known as the "Magic Cookie". One workaround to sidestep this access problem is to use xhost, which is an X server access control program. Make the following changes to /path/to/evelauncher/evelauncher.sh:

 

:'''Note:''' xhost here is granting temporary access to any local application running as the current user. It is ''not'' allowing any kind of remote access.