"Failed To Launch Game" error from the EA App on Linux

[MaliciousNine]

For whatever reason, it could be related to a restore I had to do on Pop_OS, it could be related to some other update, I don't know, but whenever I try to boot up the game on Linux, I'll get up to the EA app before it tries to repair the install and says failed to launch. The universal bash fix causes the game to fail to boot at all. Anyone got any tips here?

[SagaP]

super random, it was working fine for a long time and then it gave me "fail to launch", tried various proton versions, deleted the commpadata folder, nothing worked, tried 2 days ago, did not change anything game launched, tried yesterday did not touch anything, "fail to launch again" downloaded a crack same steam files and put them a clean bottle without installing any dependencies, the game launches every time :/

there is a post here that talks about downgrading to origin will try that to see if it works EA app appears to be the problem here

(take note that i have ea app installed in another bottle for ea app games outside steam, that one does not give me any troubles)

[spooky]

i can report same behaviour.
tried many different proton version.
tried deleting and recreating the prefix/bottle (protontricks --gui = 1237970 // https://www.protondb.com/app/1237970)
nothing worked reliably.
for me the fix or problem was the configured DNserver. i have a bit of a special
DNS setup. the DNS servers are round-robin-ed ALL OVER THE WORLD.
it seems, that contacting the configured (forwarding) DNServer, it will get forwarded to EA domain authority server (the DNS server run by EA that resolves all their domains).
this EA DNserver "somehow" creates a shard or something after being asked, it then waits for the EA client to contact.
if the IP of the EA client doesn't "match" with the configured host-system (forwarding) DNS server then it chokes.
for example: IP is country X. configured (forwarding) DNS server is country Y, that goes to authority EA DNserver. After creating the "shard" (or whatnot) after being contacted by the forwarding server, it anticipates a connection from country Y but our IP (from which the EA client is connecting) is X ... *BOOM* mega-puke.
so on linux, if you are using "Network manager", you can make a new connection and configure it with your ISP official DNS server. mine is called "eth0.spy.dns".
now if i want to run EA crap ... errr... app, i select "eth0.spy.dns" as active connection in "Network Manger" which uses my ISP dns server.
Now it works ...

[SagaP]

Originally posted by spooky:

i can report same behaviour.
tried many different proton version.
tried deleting and recreating the prefix/bottle (protontricks --gui = 1237970 // https://www.protondb.com/app/1237970)
nothing worked reliably.
for me the fix or problem was the configured DNserver. i have a bit of a special
DNS setup. the DNS servers are round-robin-ed ALL OVER THE WORLD.
it seems, that contacting the configured (forwarding) DNServer, it will get forwarded to EA domain authority server (the DNS server run by EA that resolves all their domains).
this EA DNserver "somehow" creates a shard or something after being asked, it then waits for the EA client to contact.
if the IP of the EA client doesn't "match" with the configured host-system (forwarding) DNS server then it chokes.
for example: IP is country X. configured (forwarding) DNS server is country Y, that goes to authority EA DNserver. After creating the "shard" (or whatnot) after being contacted by the forwarding server, it anticipates a connection from country Y but our IP (from which the EA client is connecting) is X ... *BOOM* mega-puke.
so on linux, if you are using "Network manager", you can make a new connection and configure it with your ISP official DNS server. mine is called "eth0.spy.dns".
now if i want to run EA crap ... errr... app, i select "eth0.spy.dns" as active connection in "Network Manger" which uses my ISP dns server.
Now it works ...

Oh my good, god work on researching this but, oh my god, i had a feeling it could be network related but is incredible that this apps can crap it's pants this way.

Anyway i came here to say that downgrading to origin did also work, there is a repo called F u c k off EA App by github user p0358 i installed it following their instruction, i ran the executables using proton tricks and choose the titanfall prefix (had to delete titanfall prefix and press play on the game wait for the ea install prompt and then cancel it but now that i seeing spooky's post there seems to be a smarter way to do this)

i also use protontricks and steam as flatpaks so i had to:

 echo "alias protontricks='flatpak run com.github.Matoking.protontricks'" >> ~/.bashrc
echo "alias protontricks-launch='flatpak run --command=protontricks-launch com.github.Matoking.protontricks'" >> ~/.bashrc 

to use protontrics to launch the executable (remember flatpaks needs permissions)

Well there has never been an app that gave me so much trouble as this one, linux OR windows.

I hope i can finally play again know if this ever stop working i will give spooky's solution a try.

(edit: also this launch option

WINEDLLOVERRIDES="version=n,b" %command%

)

[SagaP]

oh, i spoke too soon the game opens and connects to respawn, but if i try to get into a match (online or campaign) it crashes

[spooky]

Originally posted by SagaP:

oh, i spoke too soon the game opens and connects to respawn, but if i try to get into a match (online or campaign) it crashes

there is also a "problem" with SSL (secure socket layer or sumething).
you gotta add/modify some environment variable for that IF you have a new-ish intel CPU (=>11th gen?)

for my steam titanfall2 launch options i have "OPENSSL_ia32cap=~0x20000000 %command%", cause ... gen 13.
this enables the "secure" connection required for multi-player.

i don't know flatpak. i don't use it. i think it's a lazy way to use open-source (source-code is transparent and copy-past is allowed).
it's a bit of a "mess" with all them libraries and dependencies and i can see the "allure" of using some container tech to "solve" it; also since "storage" is cheap and replication and duplication is not a financial problem nowadays...

i will repeat here, that configuring a "Network Manager" entry with DNS server configured as the one from my ISP makes the game launch so far for me, 3/3 times.

if i use my "pi-hole" like local dns server however, configured in another "Network Manager" entry (example: pi-hole-like local server DNS @ 192.168.0.200) EA client craps out mostly.
i use it to enforce a blacklist of domains, mostly ad stuff. Works great and pretty much all website load okay, normally, just without ads.

[SagaP]

well i'm not in a weird network configuration, just standard isp gnat, it didn't gave me problem before, i solve the crashes by disabling dynamic resolution (but it did crash once after that), after a while i when back to the ea app launcher and the game launches again, so i still don't have a clear answer in to what causes the "Failed To Launch Game" at leas for me...

[spooky]

Originally posted by SagaP:

well i'm not in a weird network configuration, just standard isp gnat, it didn't gave me problem before, i solve the crashes by disabling dynamic resolution (but it did crash once after that), after a while i when back to the ea app launcher and the game launches again, so i still don't have a clear answer in to what causes the "Failed To Launch Game" at leas for me...

yes. there's no "logic" to the problems at least i cannot find any.
one more "bug" i think i found is that on my system, if launching the game and it "updates" the EA client ... the bottle/prefix becomes unusable.
if there's a new EA client, and we only know this AFTER launching titanfall2 via steam, and it auto-"updates" itself, the bottle/prefix has to be deleted and recreated.
it seems it cannot reliably auto-update itself inside a bottle/prefix. gotta start new ... *sigh*