Eve Launcher > app-1.9.4 with proton-likes/linux

Issues, Workarounds & Localization EVE Launcher
1

Hi,

this has been a recurring issue and I fear one day the workaround will just not work, so I am hoping either for someone having found something that reliably works and is future proof, or at least some confirmation that this is an issue that is going to be worked on.

As you probably know, because this happens every time there is a launcher update after app-1.9.4, the launcher does not start, at least not under linux/steam/proton.

The workaround is always to go to

~/.steam/debian-installation/steamapps/common/Eve Online

(steam path, with different packaging YMMV) where you can find files like

app-1.12.1  _CommonRedist  packages  eve-online.exe               Squirrel-Update.log  Update.exe
app-1.9.4   Launcher       app.ico   Squirrel-CheckForUpdate.log  steam_appid.txt

Removing the newest app-xxx i.e. today app-1.12.1 does work (for now), but I’d wish there was some confirmation that at some point playing the game will not boil down to luck and being able to use legacy launchers. Kinda breaks the immersion in a game where you plan multi month to year long campaigns, when you have to expect it to never work again in a few weeks.

See also (not extensive list of the issues, I am only allowed to post 2 links)

Or is there possibly a linux/steam user who found a way to make it work with the newer launcher apps? That’s be cool as well.

1 Like
2

You can just use GE-Proton or Proton Experimental

3

When the problem OP describes occurs, no amount of proton version selecting will work. The launcher will simply insta-close onClick.

You have to get in and delete that folder.

However, I should point out that when this happens to me, I don’t delete the most recent one, I delete the oldest one, and then I can play again.

1 Like
4

This happens for me if there’s a zombie process still running. Since I run with flatpak, I just use flatpak kill to get rid of it.

5

Thanks for the info! I will try that next time!

6

Yeah I know it’s not that since my configuration is vastly different; a reboot doesn’t even take that away, the only thing that worked was the procedure outlined above

7

Sadly removing the old app-1.9.4 and only keeping 1.12.1 did not result in anything that started, even after changing Proton versions inbetween.

8

I don’t know how the release process is with proton/steam. But they should release new versions from time to time to incorporate fixes, right? Or do you need to report errors to them to get stuff fixed or ported from wine?

I only know that this was fixed in wine way back in May. The fix version was winehq-devel 10.8 and right now we are are winehq-devel 10.16. The launcher worked ever since with all new versions released.

9

It was removing the other one (1.12 etc) that just worked for me. I kept the 1.9 one.