EA APP games not working #6766
Comments
|
Same here, Star Wars Jedi Survivor will not run. EA app window will flash and disappear about 4 times and then just stops. |
|
Hello @stixholder, same as #6765, please add |
|
@kisak-valve, see my message in #6765 You could try out Proton 7.0-6 (to my experience the best working Proton version so far with many games, also in Steam) with the "EA APP", trying to reproduce and fix the problem of the black UI rendering. I have reason to believe, that EA games might just run pretty well with it, like Ubisoft games do - in contrast to 8.0-2, for which you could too try out "EA APP" with "Crysis 3" or "Dead Space" (an EA freebeer game) and reproduce the general issues of this particular Proton version with this setup. Both will not run on my system. |
|
I also see this problem with Battlefield 1, the EA app won't even install any longer. Update: The problem solved itself a day ago, the EA app now installs correctly again. |
|
Just had an issue where Jedi Survivor wouldn't launch. I cleared the prefix, but then EA app installation hung at 100%. Clicking the X button and Cancelling install still allowed it to go through for some reason and the game launched properly. Something weird going on with the EA app installer I think. |
|
Related to #4174 as I have same error |
|
Jedi Survivor - For what it's worth: I had to verify game files seven times for it to finish the patch installation. It would get to 100% verifying and then change to "Update Paused". Once that got sorted, I had to remove mangohud from launch options, otherwise EA app would crash. Double checked by adding it again, for whatever reason mangohud crashes EA app. Once removed, game launched correctly. |
|
I had a problem where I were unable to get EA launcher installed after I removed my compat-data folder to start over with fresh data. I constantly got this error when trying to start Sims4 I managed to get it working by running the installer using Lutris. This is my lutris config: /data is my steam installation folder. After I managed to get the EA launcher installed again I no longer get that error, however I now get that the launcher appears and then dies after a few seconds. logs: |
I'm having the same problem. Had it for about 1 1/2 weeks now. It worked fine before then. I did not try to run Sims but other EA games. Probably some update on the EA App side broke things, but I wonder why only some people suffer from this problem. I already tried installing the EA App separately with the appropriate Wine prefix which did not help, but I will try your Lutris workaround as soon as I have the time. |
|
I managed to get EA desktop running in Lutris but Sims4 wasn't shown as installed so I installed it and it's starting correctly, however the addons bought in Steam is ofcourse not added :( |
|
While I have seen this issue again during the past two days, I could workaround it by installing proton-experimental and install Battlefield 1 / EA app with that and use my custom proton-ge-custom for that game afterwards. |
|
I'm on Proton experimental here, using it for Battlefront 1 + 2 and Battlefield 1 and 5. All games stopped launching a few days ago, silent crash of the EA app it seems. I followed the suggestions here and deleted the prefix folder for each game, and after relaunching each game Steam reinstalled the EA app and now everything works again as intended. All games launch and play fine online now. Thanks! |
|
Like others here, deleting the Proton prefix works to get EA App launching again, but the problem will randomly come back occasionally. Not sure what triggers it. |
What happens if you use Proton 8.0-2? I tried using that with Battlefront and Battlefield 1 the other day, but had issues connecting to online matches with that version of Proton. |
|
UPDATE: I could also run Dead Space and the game will run with video settings everything maxed out. Of course, there's the problem of non-remappable key bindings, which make the title kind of unplayable, as standard key bindings won't work for me. Crysis 3 on the other hand will not start at all with an error "...on our side, please try again later". Right, probably when the solar flare has passed... (as if EA ever fixed anything). Well, there's already another thread on that topic: |
I'm on arch and have kernel 6.3.9-arch1 and now it seems to be working properly for me aswell for Sims4. |
|
I've noticed that the EA app remains black and Battlefield 1 won't start if I compile my custom Mesa-git with Clang. If I compile Mesa with GCC, the EA app has some graphical quirks but works. I wonder if that has something to do with the workaround using the software rasterizer. As my CFLAGS are different and rather aggressive between GCC and Clang, that could also be a compiler or Mesa issue. The output I get with journalctl: |
|
The EA app bundled with Mass Effect Legendary Edition and Mirror's Edge Catalyst do not work at all. It installs, but shows a blank screen and prevents the games to load. At this point, EA is just being predatory. |
|
I am also experiencing this with Star Wars Jedi: Fallen Order. It crashes on launch (creates a UE crash feedback report) on Proton 7.0-6, 8.0-3, and Experimental. It does work with Proton 6.3-8, though. Here's the (the log was 1GB and was hard to fit the whole thing in a gist, but most of it was a bunch of unwinding calls, so I cut those out. lmk if they're important.) |
Confirmed on Mirror's Edge Catalyst |
Ran into this today with newest experimental as well. |
|
My EA Games have randomly stopped working with the ea app crashing right after the link2ea window pops up on my desktop pc but not on my steam deck. I have tried with NFS Heat, Unbound and Hot Pursuit Remastered. Here is a PROTON_LOG dump after attempting to run with an older GE version. |
|
From my own experience, and as @stixholder said as well, switching back to Proton 7.x for the broken game brought it back from the dead. Seems to be a regression going from 7.x to 8.x. |
|
As a follow up, I still can't launch any EA app games due to the launcher crashing. EA App works fine in lutris so this problem is on proton's side. (This is getting really annoying, seriously considering refunding all my EA games) |
|
@asier-ochoa I've had success clearing the Proton prefix and then using Proton Experimental. It's worked for me with both Jedi Survivor games. |
I have done this numerous times and nothing fixes it. Whenever I change proton versions I always delete the prefix since sometimes steam forgets to correctly change it's dll simlinks. If it helps, the install process crashes when redoing the prefix. Edit: |
|
I've managed to get EA Desktop, the EA Overlay and Mirrors Edge Catalyst, Unravel Two and Dead Space 3 (+ Friend list) to work. My system is ubuntu 22.04.3, nvidia drivers 530.30.02, linux 6.2.0-33-generic. This is the step to step guide:
I hope this can help. References: |
|
This is so anti-consumer. Really wanted to play some titanfall 2, game runs perfectly under Arch but I can't load it because the EA launcher crashes... If I wanted the EA app, I would have bought the game from Origin/EA. Deleting compatdate of the game lets steam reinstall the EA Shht and games launch. |
|
@d3vilguard It's very anti-consumer. Kneecaping a piece of software that works perfectly fine just cause they want to run spyware that doesn't work on your computer. For the time being, you should replace it with origin, it worked fine for me. |
|
I've had these crashes too. Problem was IPv6. I had disabled it long time ago in GRUB:
After removing the boot parameter the EA launcher works again. I knew it had to do something with my PC because it worked fine on the Steamdeck. |
|
Wow. I've been trying for years to get EA games working. Every few weeks I'd delete my prefix and try various Proton versions and they'd all fail. With other people saying they worked fine. This was my problem. I also had ipv6 disabled as a kernel parameter. Removed that and the games launch fine. Thank you so much for posting this. |
|
To me, the issue was completely different. I reported the issue: https://answers.ea.com/t5/Bug-Reports-Technical-Issues/Fail-to-launch-game-if-long-environment-variable-is-set/m-p/13193748 Though, do note that on Windows it's impossible to have more than 32760 characters in total in the environment variables block. |
|
In case your issue is the environment variable one, a workaround is setting as launch options (from Steam): The reason there are two |
|
I have the same (I think!) problem with "Jedi Survivor":
I tried several Proton releases and also @riccardobl suggestion, but nothing worked. I have limited understanding of underlying structure (especially about interaction with EA |
For my issue mentioned in this thread with a Clang-compiled Mesa, I found that the environment variable "MESA_LOADER_DRIVER_OVERRIDE=zink" helps to overcome this problem, but each re-install of the EA app, it needs several tries to get it to work eventually. |
|
Archlinux 6.6.2-arch1-1 I5-1235u; i3 virtual enviroment. |
|
|
I got it working: https://gist.github.com/xrtxn/7dd87400eaab765f076c46d28c1272c0 |
|
Also, if I don't do this, it refuses to install under a wayland compositor. I switched to kde x11 and it installs fine using proton. |
|
It worked for me with Titanfall 2 using Proton experimental. It a little slow to the EA app appears so I can accept the EULA and log in, but besides that works great. |
What version of SteamOS are you using @mhalano? I'm unable to get titanfall 2 running 😭 It seems like launcher can not connect or run failing with this error ( |
|
@tonivj5 I was playing on my Linux machine. I will try on my Steam Deck later and I let you know. |
|
@tonivj5 I tested on my Steam Deck and worked fine. I'm using SteamOS 3.5, not 3.4 with Proton experimental. Why don't you upgrade to SteamOS 3.5? I think it's already on the stable branch. I'm using the preview branch, so I can't tell for sure. |
|
This EA app is absolutely terrible. I bought NFS Heat during the winter sale, and upon trying to play it on my Deck, encountered "Something went wrong... / To continue linking your EA Account, head back and start over." So I thought I would try going to desktop mode to fix it. And somehow, there, it's even worse, because you can't close the window. You can't move it, either. And it steals focus and stays on top, which means you can't hit the stop button in Steam. You can't even open the application launcher to invoke xkill. I had to SSH in to my deck and manually kill the process for the EA App. The app does not work with Proton 8.0. It does not work with Experimental. It doesn't work with 7.0. It doesn't work with the latest GE. Why are these launchers always such hot garbage, and why do you allow these garbage AAA publishers to make them mandatory parts of the experience on your store, impacting their playability on your platform? They are too big for their britches and it's long past time you started flexing the power you have over them. |
|
Tried all manner of bullshit dancing around the EA launcher, one thing though one of the layers no one seems to mention here and it always gets it working under proton 8.02 - is if i stop my lan/wifi from vodafone connection and switch to mobile hot spot - boom connects every time - then jus fall back to lan on fiber. I have tried all numerous port forwards, DNS changes, trouble shooting the EA app install in dekstop mode (reinstall) and 99% of the time the issue i think lies with akamai IP ranges in Amazon which is where the EA subnets are nested and rotated. Tested with ISP and they can see the traceroutes drop to the IP ranges for EA ( first and last attempted on /22 network) Weird but there ya go. PS i love Battle field, starwars on the deck - pure awesomness. |
|
Can't link to ea account in unravel two |
I don't know how I missed this comment. I had the same problem and just discovered the same thing on my own the hard way... In my case the IPv6 support was simply not compiled into the kernel. After enabling it, things got much better, however not yet perfect. But I was able to finally run Squadrons. |
|
Does anyone still have this issue ? Need for Speed Unbound keeps failing to start when reaching the "link2ea" step, so if anyone got a fix to this, I'll gladly take any advices |
@mhalano thanks for your advice, yeah, once I uograded to steamos 3.5 I was able to play the game without any problem with the EA launcher. Very aprecciated for your help 😊 |
|
Thanks to @jmit79's useful hint I finally got my EA game (Titanfall 2) up and running :) Before EA switched to the EA App I never had any problems running TF2 on my laptop, so I knew for a fact that EA was to blame and not my hardware or my snowflake Arch Linux setup. After enabling IPv6, the EA App installer and the installed EA App stopped complaining about background services crashing unexpectedly, though TF2 still would not launch. As it turns out, TF2 dislikes Next problem: TF2 can't find any game servers... Fortunately, I already know this problem and that it has something to do with a bug in the OpenSSL SHA implementation for 10th and 11th gen Intel processors (i5-11400H in my case), which can be fixed by adding the environment variable FINALLY, I can play TF2 again... ... so I thought! TF2 would start properly and let me play multiplayer as long as I was connected to my dad's router. But when I got back home from my weekend visit and connected to my own router, the EA App would start to crash again! The only difference between our two routers being that my dad uses statically assigned IP addresses and I use DHCP with preferred IP addresses. Once I added to my network's
CPU: Intel i5-11400H |
@riccardobl, can confirm your steps work for Debian Bookworm with nvid driver v525 and a 6.1.0 kernel (Xwayland). I installed protontricks from package manager and used proton 7 without needing to delete the prefix. Did it with Sims 4, the EA launcher was a blank rectangle on my screen before so I couldn't launch the game until now. |
i managed to install EA Launcher and log in with Lutris using wine-ge-8-26 and enabling IPV6, but for some reason when i try to use proton 7 it gives me the error "Background services crashed", and the launcher does not open with proton experimental.
Proton Experimental Log Edit: |
|
Hey all, I had the same issue for ages. Lots of back and forth trying various things, turns out that I had to disable the Family View/disable parental controls on the account where I was trying to get it to work. Hopefully this helps others. Edit: It was Need for Speed: Heat that I was trying to get to work. |
|
EA Launcher currently shows this connection failed error in the friends tab. Titanfall 2 runs in this case but it's impossible to join your friends in matches currently. Restarting the app also doesn't help. I have also verified it not to be a network outage as everyone running Windows could use it, as well as two recent posts about it:
log: steam-1237970.log If you need any additional info from me please ask! 
|
|
#6729 (comment) I've still got these results tragically. |
|
Trying to launch Dragon Age: Inquisition. |
and others
EA APP starts and seems to work with Proton 8.0-2 at first. But after downloading a game from the library, it's not possible to run it. As I remember, I required Experimental to install EA APP as external program at first and needed to switch to 8.0-2 afterwards.
When switching to Proton 7.0-6 (which seems to be the only working stable version for Ubisoft games), the APP window UI will render as black (with invisible buttons clickable), which is useless, as is 8.0-2 ultimately, since EA games like Crysis 3 won't start with it.
After switching back to 8.0-2, the downloaded and "installed" EA game is then vanished from EA APP, and stays so, even after switching back to 8.0-2.
In addition, the Steam client will grey out and block the Proton version drop down box, once EA APP (or any externally installed game/program for that matter) was launched, until Steam was completely closed and restarted.
Originally posted by @stixholder in #6617 (comment)
UPDATE: after switching to Proton 8.0-5 (and possibly some system updates involved), the "EA App" will now start after showing buttons "Start App" and "Repair" (repair what/how?) - at least, until the next "Update" has taken place. Let's see.
Proton 9.0-1 or Experimental did not work. After switching back "of course" I have to completely re-download all games, due to EA's incompetence of recognizing the games already installed under their corresponding prefixes, unlike the "UbisoftConnectLauncher" can and will.
Crysis 3 will now run (again), but after the latest re-download, I get "greeted" with a request for "Administrator rights" every time the game is started - EA WTF ?!?
That being said, it shows, how (Online-)DRM is evil, because it forms a barrier for alternative platforms, by locking everything into a wall, that may not even build up (i. e. run) and force-binding all walled content into a single environment (optimized for the DRM tooling), which may not even be compatible to single titles.
What do you get in turn? Maybe undocumented updates, wanted or not. Often additional technical and security issues. Mostly, painstaking personal profiling, loss of privacy, a patronizing regime of enforced rules, lengthy startups and a bloated UX.
Also, it mostly prevents any different approaches and self-employed workarounds to solve technical issues with platforms.
Which in turn may result in a complete or partly dysfunctional game portfolio of the corresponding vendor - for Linux, as well as for other, even legacy Windows platforms.
Of course, this more or less holds true for all Online-DRM vendors, unless perhaps, to what may be possible, if you get access to DRM-free game installers, e. g. from GOG.
The text was updated successfully, but these errors were encountered: