Your EA game launches, the EA App window flashes, and then nothing. Or the login screen loops until you give up. Phoronix reports that Valve's Proton 11.0-2e, built with CodeWeavers, was released to address EA App issues (Phoronix). This guide shows how to switch one game to that build, confirm it is running, and undo the change if things get worse.
Phoronix confirms the release and its EA App focus, but it does not list what changed. For the exact changes, read the official notes on the Proton releases page. Nothing below depends on a specific fix. Every command is untested, and no run output is shown.
Before you change anything
You need the Steam client, Steam Play enabled, and the game installed. On a desktop, open Steam, then Settings, then Compatibility, and confirm Steam Play is on for the titles you own. On Steam Deck, skip straight to the per-game setting.
The commands here assume a native Steam install on any distro, with data in ~/.local/share/Steam. Flatpak Steam keeps the same tree under ~/.var/app/com.valvesoftware.Steam/.local/share/Steam. If your game lives on a second drive, its prefix sits in that library's steamapps folder, not your home directory. On Steam Deck, switch to Desktop Mode and use Konsole for the terminal steps.
Step 1: Find the game's App ID and current Proton
- In Steam, right-click the game and choose Properties.
- Open the Compatibility tab. Note which tool is selected, or whether forcing a tool is off. Write it down; this is your rollback target.
- Find the App ID in the store page URL (
store.steampowered.com/app/NUMBER). Non-Steam EA shortcuts get a long generated ID instead, so check the folder names incompatdataafter one launch.
The prefix is the Windows-like environment Proton builds for each game. It lives at steamapps/compatdata/APPID. Keep that path handy for the next step.
Step 2: Back up the prefix before switching
Switching Proton builds can update the existing prefix in place. A newer build may change a prefix in ways an older build handles badly, so a copy is cheap insurance. Fully quit Steam first (Steam menu, Exit), because a running client can hold files open.
Untested command; replace APPID with your number:
cp -a ~/.local/share/Steam/steamapps/compatdata/APPID ~/compatdata-APPID-backup
Expected result (unverified): a folder named compatdata-APPID-backup in your home directory, containing a pfx subfolder. Check the prefix size first with du -sh ~/.local/share/Steam/steamapps/compatdata/APPID, since an EA App install inside a prefix can be large.
Saves need separate thought. Many Windows games store them inside the prefix under pfx/drive_c/users/steamuser, so the backup covers them. Cloud saves add another layer of safety. Check the game's settings to see which applies to your title.
Step 3: Force the newer Proton for this one game
- Start Steam again and open the game's Properties, then Compatibility.
- Tick "Force the use of a specific Steam Play compatibility tool".
- Open the dropdown and pick Proton 11.0-2e. If it is not listed, pick the newest Proton entry available. Phoronix's report does not say how the build reaches each client, so a missing entry is a gap, not a mistake on your end.
- Close the window and let Steam download the tool if it prompts.
Set this on one game only. A global change affects every title you own, which makes it hard to tell what helped. Steam Deck works the same way: Properties, Compatibility, force a tool, pick from the list. We cover related ground in enable nvidia reflex in proton on linux: setup & checks.
Step 4: Launch and verify the build in use
Launch the game once and let the EA App finish whatever it wants to do. First launches after a switch can take noticeably longer and may include setup prompts. Give it a few minutes before judging the result.
Then verify two ways. First, reopen Compatibility and confirm the forced tool is still your chosen build. Second, check the prefix's version file. Untested command:
cat ~/.local/share/Steam/steamapps/compatdata/APPID/version
Expected result (unverified): a line naming the Proton build that last touched the prefix. This is an inference from how Proton prefixes are commonly laid out, not a documented guarantee. The log in Step 5 is a firmer check because it records the build near the top.
Step 5: If it still fails, capture a log
In the game's Properties, General tab, set Launch Options to:
PROTON_LOG=1 %command%
Launch the game, reproduce the failure, and quit. Proton typically writes the log to your home directory as steam-APPID.log. Untested check: ls ~/steam-APPID.log. If the file is missing, search for it with find ~ -name "steam-APPID.log". Flatpak users should look inside the Flatpak home first; this is an inference. This pairs well with fex vs box64 on arm64 linux: which to use for games? in depth.
Open the file and find the Proton version near the top. Then search for err, fixme, crash, and the EA App executable names. Repeated errors from the same module right before exit are the most useful lead. Remove the launch option when you finish, because logs grow quickly.
Troubleshooting by symptom
| Symptom | Next action |
| --- | --- |
| EA App login loop | Confirm the forced build, relaunch once fully, then capture a PROTON_LOG=1 log and look for network or browser-window errors. Compare with your backup prefix if the loop is new. |
| Black window | Wait a few minutes after the first launch, then check the log for graphics errors. Try the previous Proton to see whether the behavior changes. |
| Instant exit | Enable PROTON_LOG=1, read the last 50 lines for the failing module, and check that Steam was fully restarted after the switch. |
| Worked, then broke after the switch | Roll back using the steps below, then report the log to the Proton issue tracker. |
| Prompts repeat every launch | Check that the prefix folder is writable and that the drive has free space. |
Roll back without losing the prefix
First, set the Compatibility tool in Steam back to the entry you noted in Step 1, or untick the force option. If the prefix itself seems damaged, quit Steam and restore the backup. Untested commands:
Also read: how to check your amd p-state driver mode on linux — background
mv ~/.local/share/Steam/steamapps/compatdata/APPID ~/compatdata-APPID-broken
cp -a ~/compatdata-APPID-backup ~/.local/share/Steam/steamapps/compatdata/APPID
Expected result (unverified): the original prefix returns, and the failed one stays in the broken folder for inspection. Delete the broken copy only after the game runs again.
What to expect next
A single release will not fix every EA title, and Phoronix does not claim it will. If your game works, leave the per-game setting in place and watch the release notes for follow-up builds. If it still fails, keep the log and the Proton version together and include both when you report the problem.
