Todays update to app-1.10.1 is again not working. (sadly as i suspected). So we Linux users are stuck.
1 Like
The same trick, deleting the app-1.10.1 directory, fortunately still works.
1 Like
Might be a good idea to figure out what the root cause of this is so that it can be fixed. I don’t know how to get any kind of useful log output though.
Switching Lutris (I run through Lutris rather than Steam because I need backup games while waiting in EVE :D) to “ge-proton” under configuration/Runner options makes the launcher work and client also works well from what I can tell (DX12 setting in the launcher).
This is on AMD Ryzen 7 5700G APU if it matters.
That worked. Thank you for posting this. At least we have something. o7
2 Likes
Interesting, does it keep working? As in, with the latest version of the launcher after it updated today?
I also run the game with GE-Proton but I do have the issue that version 1.10.x of the launcher fails to start.
Had to apply the fix, deleting the folder today. Worked earlier today, right after Legion patch. Now, 8-10 hours later, same deal. “app-1.10.1” appeared again, deleted it, Launcher works again.
For those who installed and runs Eve via Lutris, click the arrow next to “Play”. Browse files. Go to: drive_c/users//AppData/Local/eve-online
‘user’ can be your username or steamuser, both lead to the same place.
Thanks D43dun!
Checked it again just now and yes it is working:
- Launcher is version 1.10.1
- ge-proton
- enable DXVK
- enable VKD3D
- Enable Esync
- Enable Fsync
- Enable FSR, BattlEye Anti-cheat and easy anti-cheat (I doubt that this matters)
Like many I had the “failing to launch” issue with the Launcher update from 1.9. to 1.10. ,which I resolved by replacing the 1.10… folder with the old 1.9… folder as suggested above.
The launcher updated again on Tuesday to 1.10.1 (I don’t know if this is significant but the update didn’t remove the 1.9 folder, just added the 1.10 folder but the Launcher reports it is running 1.10.1)
All appears to be working fine so far.
I run Eve via Steam (not the flatpack version), using Proton Experimental, DX11.
A couple of things that may or may not be significant. I am using the Nvidia driver version 550.144.03 which is not the latest version (570.133.07) as this caused me some issues with some other applications so I rolled it back.
In between these two Launcher updates my Steam client updated Proton Experimental.
The steam client downloads a 160k “Eve Online” file pretty much every day - as far as I can make out its related to Vulcan shaders.
My Linux flavour is Mint 21.3 Virginia. AMD 5600 GTX 1660 Super. 32gb
Thank you for the notice that there was an update to ge-proton which seems to allow the launcher 1.10.1 to run.
This made me think why there was no update for wine-staging for the last two weeks. I discovered that there was a release for wine-devel and staging for version 10.8, but apt update does not know about wine-staging 10.8 in spite of these files are available in the repository.
I don’t know if this is an error or an oversight from winehq repository maintenance.
However there was at the same time of the wine-staging release 10.8 a wine-devel 10.8 release and this one is installable with apt install. So i installed that, manually downloaded the 1.10.1 launcher and installed that as well and now i am running 1.10.1 launcher with winehq-devel 10.8 fine.
I didn’t want to try manually downloading and installing the winehq-staging 10.8 files for now. Maybe they got retracted or something else. I will switch back to wine-staging when devel is not up to run eve anymore.
1 Like
Got the launcher 1.10.1 update today and the launcher stopped working again like before, Running Proton 9.0-4 through Steam. Downloaded GE-Proton 10-3 and using that with EVE the 1.10.1 launcher is now working for me.
2 Likes
Can confirm GE-Proton 10.3 working with 1.10.1 launcher version
1 Like
any Ubuntu version 24.04.2 LTS solutions? My husband has been at this for HOURS now trying to fix it, even did a fresh install, has tried through steam and lutris with no luck. Can someone please help before he throws his computer through a window???
Your husbo could download this: ProtonUp-Qt Scroll down for Appimage or Flatpak. Launch it. With Appimages, it helps if you also have Appimagelauncher installed. Much smoother experience. Just double-click the file.
At “Install for:” Select Steam or Lutris. At the bottom, “Add version”, click it.
Peeps are saying GE-Proton 10-3 works, can try with that
8th May 2025, we were discussing the release of v1.10.0 and all the Electron problems being linux-only.
1 Like
Electron version 36.1.0 crashes WINE/Proton.
Alright. Thanks for the insight. Guess i was wrong.
I’m glad that problems got resolved now for all methods to run Eve on Linux it seams.
Yesterday, with Stroopwafel and Avalon, we had confirmation of what you experienced:
Briefly, from time to time, also WINE/Proton users would have their Launcher autoupdate - namely after a major expansion release like Legion, or a Launcher release.
Then they (manually) re-disable automatic Launcher updates for W+P, and the Launcher stays at 1.9.4 if has been rolled back.
How do we know when/how/if/etc.?
There are two critical files, named the same, but different if you run a Windows client natively or a Windows client through WINE/Proton, that somehow arbitrate what’s the version to download.
The file is stored in Eve Online/packages/RELEASES and depending what OS you’re running, it’s either downloaded from
https://launcher.ccpgames.com/eve-online/release/linux/wine/RELEASES
or
https://launcher.ccpgames.com/eve-online/release/win32/x64/RELEASES
(You have traces of this in the Squirrel Update and CheckForUpdate logs, if you need counter proofs)
Besides the fact that CCP devised a way to differentiate from pure Windows to WINE’d clients, and built a different, dedicated URL structure to (stealthy) support us, but if you get both files and diff them, you realize how the “freeze the update” would work:
There are no reference to nupkgs newer than v1.9.4 on Linux’s RELEASES, so the Launcher would never try to fetch v1.10.x+ based on the content of that file.
The two files differ also because WINE has no(t yet a) working msdelta library implemented, so the “delta” packages would mess up the Launcher update procedure: for Linux, only the “full” packages are visible, and thus downloaded and automatically installed.
This is to further reinfore the idea that CCP won’t officially support Linux, but its devs are actually doing a TON of work to let us work around the quirks of our ecosystems.
3 Likes
Had the same problem.
THIS worked for me: Eve Launcher on Linux (Lutris) not working after launcher update 5/08/2025 - #88 by Axhind. The GE-Proton setting was the key for me.