Looking for assistance with installing EA App or Origin on Linux?
Looking for assistance with installing EA App or Origin on Linux?
I recently purchased Plants vs Zombies gw2 on Steam, but when attempting to start it via proton experimental, the system tries to fetch the EA App, Microsoft DirextX, and fails to launch, returning to the green play button. Using proton 8.0-3 unlocks what seems like an EA App installer, which after clicking 'lets go' opens Link2EA but displays a graphical error. I can still navigate the window normally, though it appears as a solid color (see image below). When trying to install Origin or the EA app using Lutris, both methods produced identical errors—spitting out an unclear code. The main concerns I noted are:
1. Warning: You're running winetricks-20220411-next; the latest upstream is winetricks-20230212.
2. Warning: Your system uses a 64-bit WINEPREFIX. Many commands only support 32-bit packages. Updating via your distribution's package manager or manually resolving this seems necessary, though I'm unsure how to fix it.
3. Warning: Executing load_arial grep flagged a stray character in a path—possibly a file path issue.
4. Warning: The checksum for /home/cringe_master/.var/app/net.lutris.Lutris/cache/winetricks/corefonts/arial32.exe didn't match after using --force, so I ignored it and proceeded.
5. Warning: Cabextract reported missing a file at /home/cringe_master/.var/app/net.lutris.Lutris/cache/winetricks/corefonts/arial32.exe; no valid cabinets found.
6. Warning: Command cabextract returned status 1 and exited with code 256, indicating a serious issue.
I'm not sure how to switch to a 32-bit WINEPREFIX, as I'm new to Linux and have only been using it for a short time.
Log from Lutris indicates the system is running winetricks-20220411-next. A warning about needing an updated version via package manager was noted. The script initialized monitoring and created a directory structure for games. There were warnings regarding checksum mismatches and a failed cabextract operation, suggesting potential issues with file locations or corrupted data. The process ended with an exit code of 256 due to a monitoring process termination.
Review the documentation at https://www.protondb.com/app/1922560. The updates from mint are likely more useful, but test the proton versions that are confirmed to function (real ones, not just prototypes). Disregard this suggestion. Perhaps it’s best to move on. Recently I encountered this issue (possibly a recent grep improvement?), though my script handled it and fixed it afterward. Before proceeding further, try "protontricks" – it’s a tool that identifies the correct wine prefix for your Steam app ID. If you have any wine versions installed, the automatic update feature may fail next time the package is updated. Previously, I resolved a similar problem by installing the fonts from https://corefonts.sourceforge.net, which made the app appear fully functional on my system. This solution worked outside of Proton and Ariel, so it might not apply here. *If you need to use a specific GE Proton version listed as working: exit Steam, download the desired version from https://github.com/GloriousEggroll/proto...m/releases, ensure the ~/.local/share/Steam/compatibilitytools.d directory exists, create it if needed, and extract the entire GE-ProtonX-yy folder into that directory using your preferred archiver. Restart Steam. If the file appears corrupt, go back to earlier steps and reinstall the fonts via protontricks with the 1922560 font set.*