Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem



You can always rebuy the game at a later date (when it’s more stable, hopefully).
I would like to support this small indie early.
In that case, I don’t know what to suggest. I know what I’d suggest doing on a Steam Deck, but on a Linux PC I wouldn’t really know where to start (I assume that’s what you’re using). Sorry I can’t be of more help. I use a plugin called “Storage Cleaner” on my Deck that detects shader cache files and compact data for Steam games and allows you to individually delete the data per game. But I don’t know if there are any non-Steam Deck programs that do something similar for Linux.
You could always experiment with different Proton versions (or Proton GE)-or check Proton db to see if anyone has had a similar issue.
You also might want to read this report from 4 weeks ago, OP and be sure you have EAC installed for the game:
https://www.protondb.com/app/4124950?device=pc
I re-read their post and realized that-and updated mine. It’s late for me too, lol.
Same I was so confused when I could recreate the issue. After a reboot it does the launch loop still.
This was a juicy thread. I was able to confirm EAC was/is running in the logs. However the game client gets terminated server side is the consensus. Since it produces no error locally.
According to ddiazg90 on my ashes thread.
https://test1.login.steam.hlxgame.cc/app/4124950/discussions/0/792200576013326937/
I looked through the linux crash log all that happens is CrashReportClient.exe gets called and nothing pre/post to indicate why. Idk how that could possibly bork my steam client. Also doesn't appear to write a log anywhere for this. (this might be me looking at the wrong place, using terminal "journalctl -xe", journalctl | grep <appname> @steam @ashes and journalctl -p 3 -xb - My linux knowledge is limited i've been on the OS for only a ~month ubuntu)
I can't 100% guarantee you that this is your issue but I can sure say that it seems to causes random issue to quite a number of people.
After reading the thread in the Ashes hub, it might just be something got borked on EAC’s end for Linux when they updated the client. That’s unfortunately one of the realities of running Linux-devs often have to carve out special exceptions to get EAC to “play nice” with Linux and/or Steam Deck and often games just stop working entirely until:
1)The devs release a fix
2)Someone finds a new Proton (or Proton GE-short for Proton Glorious Eggroll-should be in your discover store if you don’t already have it) that works with the updated client
Or
3)In your case, Linux releases a new update that resolves the issue (for me, it’s Steam OS)
I feel your pain, I was playing a game that’s in maintenance mode now (was still fun, though) until a Steam OS update suddenly made the EAC they were using incompatible with SD. I’ve heard the game will still run if you install it via flatpack, but I don’t know what that means and no one’s been able to explain it to me in simple terms.
they mean install Steam on the Steam Deck through flatpak. It probably means go into Desktop, click the little blue shopping bag icon to launch "Discover" which is the GUI app for flathub. Search Steam and then install it.
This will be a separate Steam under ~/.var so you will need to re-login and re-install your game. Whether or not you can make flatSteam aware of the your other games, and even give the flatpak permissions to use them properly, sometimes I've found that flatpak apps can conflict with SElinux and other thing in weird ways when things aren't in .var so just reinstall the game in flatSteam.
also when you install flatpak Steam, you might need to go up to the top right of Discover and switch the source from Arch's package repo to flathub specifically.
I actually did on the re-install and it felt super buggy feeling/delay etc so i uninstalled it then re-installed through CLI on the OS. I agree there is something wrong with the snap version!
I wasn't fully up-to date. I updated no change. I've also opened a thread on their discord server today. It's not entirely a Linux issue cause my friend is playing on linux no issue and streaming it to me in discord D: I might be flagged? Since he can with same runners basically same system.
# System Details Report
---
## Report details
- **Date generated:** 2025-12-13 18:40:33
## Hardware Information:
- **Hardware Model:** iBUYPOWER AMD
- **Memory:** 96.0 GiB
- **Processor:** AMD Ryzen™ 9 9950X3D × 32
- **Graphics:** AMD Radeon™ RX 7900 XTX
- **Graphics 1:** AMD Ryzen™ 9 9950X3D
- **Disk Capacity:** 2.0 TB
## Software Information:
- **Firmware Version:** 1087
- **OS Name:** Ubuntu 24.04.3 LTS
- **OS Build:** (null)
- **OS Type:** 64-bit
- **GNOME Version:** 46
- **Windowing System:** Wayland
- **Kernel Version:** Linux 6.14.0-37-generic
I no have a steam deck ):
Meanwhile old Lance be playing old 90's games on an off-brand miniPC manufactured in China with a 6+ years old chipset.