found another user experiencing EAC games not launching with this update @ https://steamcommunity.com/groups/SteamClientBeta/discussions/3/803470345661279686/
Not sure why this was moved from Steam-for-Linux to Proton as I generally always use Proton Experimental. In both aforementioned cases where EAC failed/passed (workaround) Proton Experimental was used... the deciding factor for the fail case is the latest Steam Beta Client that was released today.
Try the new Steam Client Beta update that just got released.
Thank you for the report - you're right that this is the right spot.
Confirmed 1775946595 resolves the issue... Both Elden Ring and W40K Space Marine 2 launched normally after opting back in to the new Linux Client Beta
Thank you for the quick fix.
For transparency, the initial transfer was because we generally track issues affecting games run with Proton in the Proton issue tracker.
Thanks for the triage. Closing per the last couple comments..
Your system information
tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]Please describe your issue in as much detail as possible:
Tried playing two games that use EAC after applying this update, and they failed to launch... both these games worked fine 30 minutes ago before applying the update.
Note: SteamRT3 is disabled, games installed on an external SSD, steam and proton installed under default HOME paths
Steps for reproducing this issue:
Games That now fail to launch
Any that use EAC... one's I've been playing today are:
Snippet from console-linux.txt mentions Xalia issue?
[2026-04-11 15:48:13] fsync: up and running.
[2026-04-11 15:48:17] chdir "/data/steamlibrary/SteamLibrary/steamapps/common/Space Marine 2/client_pc/root/bin/pc"
[2026-04-11 15:48:17] Game Recording - would start recording game 2183900, but recording for this game is disabled
[2026-04-11 15:48:17] Adding process 2610031 for gameID 2183900
[2026-04-11 15:48:17] Adding process 2610032 for gameID 2183900
[2026-04-11 15:48:17] Adding process 2610033 for gameID 2183900
[2026-04-11 15:48:18] Adding process 2610194 for gameID 2183900
[2026-04-11 15:48:19] fsync: up and running.
[2026-04-11 15:48:19] Adding process 2610196 for gameID 2183900
[2026-04-11 15:48:19] Adding process 2610210 for gameID 2183900
[2026-04-11 15:48:19] Adding process 2610267 for gameID 2183900
[2026-04-11 15:48:19] Adding process 2610270 for gameID 2183900
[2026-04-11 15:48:19] Adding process 2610273 for gameID 2183900
[2026-04-11 15:48:19] Adding process 2610276 for gameID 2183900
[2026-04-11 15:48:19] Adding process 2610285 for gameID 2183900
[2026-04-11 15:48:19] Adding process 2610290 for gameID 2183900
[2026-04-11 15:48:19] Adding process 2610297 for gameID 2183900
[2026-04-11 15:48:21] Adding process 2610464 for gameID 2183900
[2026-04-11 15:48:21] Adding process 2610474 for gameID 2183900
[2026-04-11 15:48:21] Adding process 2610476 for gameID 2183900
[2026-04-11 15:48:21] Adding process 2610482 for gameID 2183900
[2026-04-11 15:48:21] System.PlatformNotSupportedException: Video driver not supported
[2026-04-11 15:48:21] at Xalia.Sdl.WindowingSystem.Create () [0x0003e] in <743e8bdcd9c54484ad89463ed4e626f6>:0
[2026-04-11 15:48:21] at Xalia.Sdl.WindowingSystem.get_Instance () [0x00007] in <743e8bdcd9c54484ad89463ed4e626f6>:0
[2026-04-11 15:48:21] at Xalia.Ui.UiMain..ctor () [0x00027] in <743e8bdcd9c54484ad89463ed4e626f6>:0
[2026-04-11 15:48:21] at Xalia.MainClass.Init (Xalia.Gudl.GudlStatement[] config) [0x0001b] in <743e8bdcd9c54484ad89463ed4e626f6>:0
[2026-04-11 15:48:22] Adding process 2610492 for gameID 2183900
[2026-04-11 15:50:04] pid 2610268 != 2610267, skipping destruction (fork without exec?)
[2026-04-11 15:50:05] Game Recording - game stopped [gameid=2183900]
[2026-04-11 15:50:05] Removing process 2610492 for gameID 2183900
[2026-04-11 15:50:05] Removing process 2610482 for gameID 2183900
[2026-04-11 15:50:05] Removing process 2610476 for gameID 2183900
[2026-04-11 15:50:05] Removing process 2610474 for gameID 2183900
[2026-04-11 15:50:05] Removing process 2610464 for gameID 2183900
[2026-04-11 15:50:05] Removing process 2610297 for gameID 2183900
[2026-04-11 15:50:05] Removing process 2610290 for gameID 2183900
[2026-04-11 15:50:05] Removing process 2610285 for gameID 2183900
[2026-04-11 15:50:05] Removing process 2610276 for gameID 2183900
[2026-04-11 15:50:05] Removing process 2610273 for gameID 2183900
[2026-04-11 15:50:05] Removing process 2610270 for gameID 2183900
[2026-04-11 15:50:05] Removing process 2610267 for gameID 2183900
[2026-04-11 15:50:05] Removing process 2610210 for gameID 2183900
[2026-04-11 15:50:05] Removing process 2610196 for gameID 2183900
[2026-04-11 15:50:05] Removing process 2610194 for gameID 2183900
[2026-04-11 15:50:05] Removing process 2610033 for gameID 2183900
[2026-04-11 15:50:05] Removing process 2610032 for gameID 2183900
[2026-04-11 15:50:05] Removing process 2610031 for gameID 2183900
Note: In case it's important, my system has an AMD iGPU and dGPU, so to ensure the dGPU is used with all games "DRI_PRIME=1 %command%" is the base/default launch options set for every game.
Workaround
As I do not know how to downgrade Steam Linux Client Beta (I thought about restoring a nightly backup, but didn't want to make things worse) I opted out of the beta...
Steam => Settings => Interface => Client Beta Participation = No Beta Chosen
After the Steam client "re-installed" both EAC games resumed working normally as they had before.