Installing EVE on Linux: Difference between revisions

{{Update|Native Linux launcher has been retired. Recommended solution for running EVE on Linux is Steam/Proton}}

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]].

The current launcher (december 2023, based on squirrel) tidbits to get it running:

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

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

== Custom Launcher Shortcut ==

[[File:Evelauncher.png|thumb|right|Launcher icon]]

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

#: {{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}}

#: {{code|<nowiki>[Desktop Entry]</nowiki><br><nowiki>Name=EVE Online</nowiki><br><nowiki>Comment=EVE Online by CCP Games</nowiki><br><nowiki>Exec=/usr/bin/evelauncher</nowiki><br><nowiki>Icon=Evelauncher</nowiki><br><nowiki>Terminal=false</nowiki><br><nowiki>Type=Application</nowiki><br><nowiki>Categories=Game;</nowiki>}}

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.

:'''''Note:''' Make sure to untick 'Run clients with DX9' if you want to use DX11.'''''

# Open the launcher settings with the small "E" symbol in the top right, tick "Use custom Wine", and in the box below it enter the path of your wine executable, eg.

# Remove EVE's existing wine and wineenv folder

#: {{code|rm -Rd ~/.eve/wineenv ~/.eve/wine}}

# Reopen the launcher and start the game as normal.

# EVE's wine prefix should rebuild itself with the custom version.

[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.

Install Lutris via your package manager, and then head to the [https://lutris.net/games/eve-online/ EVE Online page on the Lutris website] to pick an install script. As of May 2020, there are four main install scripts: a DXVK variant, a non-DXVK (OpenGL-based) one, one with Steam, and a Chinese distribution. The DXVK version offers generally better performance. For the new launcher there is a eve-online-april-beta-launcher installer.

After picking your script from the Lutris website and following the installation procedure, an EVE Online icon will show up in your Lutris client UI. From this point, you can click on "EVE Online" to start the EVE Launcher. You may configure options for the game, runner or system. For troubleshooting, make sure '''Run Client with Logging''' is enabled in the EVE Launcher options.

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.

:'''Note:''' The following example is for Ubuntu - paths and package names will likely be different on other distributions.

# Download the older library from your distribution's repos

#: {{code|sudo ln -s /lib/x86_64-linux-gnu/libssl.so.1.0.0 {{Color|green|/Path/To/evelauncher/}}libssl.so}}

#: {{code|sudo ln -s /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 {{Color|green|/Path/To/evelauncher/}}libcrypto.so}}

# Create the wrapper script in your preferred editor

:'''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}}

# Insert the following text and then save it:

#: {{code|dirname<nowiki>=</nowiki>{{Color|green|/Path/To/evelauncher/}}<br><br>if [ ! -e $dirname/libssl.so.1.0.0 ]; then<br>    ln -s /lib/x86_64-linux-gnu/libssl.so.1.0.0 $dirname/libssl.so<br>fi<br>if [ ! -e $dirname/libcrypto.so.1.0.0 ]; then<br>    ln -s /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 $dirname/libcrypto.so<br>fi<br>exec $dirname/evelauncher.sh}}

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

# Download the installer

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

#: {{code|sudo apt-get install libfontconfig1}}

=== Libxcb dependencies ===

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

=== Launcher Shortcut Issues ===

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

This, and other errors, are likely due to the fact that the 'dirname' and 'pwd' commands will return the location of the soft link, not of the shell script itself. Hence, we need to use readlink to follow every symlink in the path. Make the following changes to /path/to/evelauncher/evelauncher.sh:

:{{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>

 

 

If Eve Online fails to launch, try running it from the terminal. Check for the following error message:

 

 

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.