Same here, Star Wars Jedi Survivor will not run. EA app window will flash and disappear about 4 times and then just stops.

@kisak-valve, see my message in [#6765](https://github.com/ValveSoftware/Proton/issues/6765)
I think, this issue can be addressed in a different approach from your side, though:

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
https://www.reddit.com/r/SteamDeck/comments/13mo6to/ea_app/

I managed to get it working by running the installer using Lutris.

This is my lutris config:
Executable
/data/steamapps/common/The Sims 4/__Installer/Origin/redist/internal/EAappInstaller.exe
Wine prefix:
/data/steamapps/compatdata/1222670/pfx
Wine version:
lutris-GE-Proton8-7-x86_64

/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:
https://www.dropbox.com/s/rvyh5uf1jr4jqbg/steam-1222670-2.log?dl=0

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 https://www.reddit.com/r/SteamDeck/comments/13mo6to/ea_app/

I managed to get it working by running the installer using Lutris.

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.

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:
After upgrading my system with Kernel 5.15.x and Mesa 22.5.x, the EA App will now work with Proton 8, too.

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:
Crysis 3

UPDATE: After upgrading my system with Kernel 5.15.x and Mesa 22.5.x, the EA App will now work with Proton 8, too.

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: Crysis 3

I'm on arch and have kernel 6.3.9-arch1 and now it seems to be working properly for me aswell for Sims4.

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 PROTON_LOG output when running on 8.0-3:
https://gist.github.com/stevenre3d/87441f8d044b973f3caab50de0506bc5

(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.)

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.

Confirmed on Mirror's Edge Catalyst

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.

@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:
Also think it's worth it to look at EA App's own logs, it seems to mention some issue not being able to write registry keys + not being able to launch an inter process communication server for telemetry purposes using grpc:

       9  [2023-09-18T15:51:23.876Z]  PID:  1644  TID:  1704  INFO        (eax::foundation::security::allowAllUsersReadWriteAccess)   Allowing all users read write access for path [C:\ProgramData\EA Desktop\machine.ini]   
      10  [2023-09-18T15:51:23.877Z]  PID:  1644  TID:  1448  INFO        (`anonymous-namespace'::registerProtocol)   Updating EA Connect registry keys, protocolValue[URL:Link2EA Protocol], protocolCommandValue["C:\Program Files\Electronic Arts\EA Desktop\EA Desktop\Link2EA.exe" "  %1" "%2" "%3" "%4" "%5" "%6" "%7" "%8" "%9"]
      11  [2023-09-18T15:51:24.004Z]  PID:  1644  TID:  1448  ERROR       (eax::systemUtils::overwriteProtocolAndSdkPaths)    Failed to update registry keys, this may cause launch issues if there was a recent update which erased any of these keys   
      12  [2023-09-18T15:51:24.005Z]  PID:  1644  TID:  1448  ERROR       (eax::services::localStorage::logOnError)   Operation [reading]: Could not find file or could not create containing folder for category "IQ", file path [C:\ProgramData\EA Desktop\530c11479fe252fc5aabc24935b9  776d4900eb3ba58fdc271e0d6229413ad40e\IQ]
      13  [2023-09-18T15:51:24.006Z]  PID:  1644  TID:  2112  INFO        (eax::services::TelemetryDispatcher::Impl::logTelemetryEvent)   Telemetry Event: [{"authenticated":false,"criticalOffline":false,"criticality":false,"disableCulling":false,"enabled":true,"offline":false,"opt  ional":false,"params":{"emsg":"Failed to repair protocol keys","src":"updt"},"taxonomy":"erro.repr.keys","throttleCount":0,"timestamp":"2023-09-18T15:51:24.004","weight":0.0}]
      14  [2023-09-18T15:51:24.046Z]  PID:  1644  TID:  1448  ERROR       (?) [grpc] [server_secure_chttp2.cc:81] {"created":"@1695052284.046000000","description":"No address added out of total 1 resolved","file":"D:\p4\grpc\1.22.1\src\src\core\ext\transport\chttp2\server\chttp2_s  erver.cc","file_line":396,"referenced_errors":[{"created":"@1695052284.046000000","description":"Failed to add port to server","file":"D:\p4\grpc\1.22.1\src\src\core\lib\iomgr\tcp_server_windows.cc","file_line":510,"referenced_errors":[{"created":"@1695052284.046000000","descrip  tion":"OS Error","file":"D:\p4\grpc\1.22.1\src\src\core\lib\iomgr\tcp_server_windows.cc","file_line":201,"os_error":"Unable to retrieve error string","syscall":"bind","wsa_error":10049}]}]}
      15  [2023-09-18T15:51:25.046Z]  PID:  1644  TID:  1448  FATAL       (eax::services::ipc::IpcServerImpl::runInternal)    Unable to start IPC server[bgs]   
      16  [2023-09-18T15:51:25.046Z]  PID:  1644  TID:  1448  ERROR       (eax::services::exception::ExceptionHandlerClient::Notify)  Whoops!   
     
      ************  CRASH DETECTED  ************   

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:

1. Install protontricks >= 1.10.1 from flathub (the older version in ubuntu repos won't work) [2]
2. Delete the proton prefix for the game if it exists due to previous attempts
3. In the compatibility tab select "Force the use of a specific Steam Play compatibility tool" and select proton 8.0-3
4. Start the game
5. If you can, complete the installation from the EA Launcher (click let's go and wait). The game might start , be partially broken or not start at all.
6. Close the game from steam
7. Open protontricks
8. Select the game
9. Select "Select the default wineprefix" and click OK
10. Select "Install a Windows DLL or component" and click ok
11. Select "d3dcompiler_47" and click OK [1]
12. Wait until your are taken back to the protontricks window
13. Select "Install a font" and click OK
14. Select "liberation" and click OK [1]
15. It will take a while, just wait until you are taken back to the protontricks window (if you get an error, click ok and wait, it doesn't matter [1])
16. Click X to close protontricks
17. Start the game
18. Everything should work

I hope this can help.

References:
[1] https://steamdeckhq.com/tips-and-guides/fixing-ea-play-blank-screen-for-ea-games-on-steam/
[2] https://github.com/Matoking/protontricks/issues/236

Replying to https://github.com/ValveSoftware/Proton/issues/6766#issuecomment-1731734674

Appreciate the help. I decided to try this again but I get the same issue. If im not mistaken, d3dcompiler47 fixes the blank screen, included in proton GE.

@riccardobl doesn't work for me for Mass Effect legendary, the only difference is that without the DLL the window is completely blank, but with the DLL it has the header but no content and just freezes right after opening

And with Proton Experimental, it does not render anything at all, there's Link2EA.exe process hanging alone but no windows opened

With Proton 8.0-3, the problem of EA Application not opening seems to have been resolved, but I could not open NFS: Unbound at all. A black screen appears and the application closes after 5-10 seconds. Battlefield 1 and V do not have this problem. If anyone can open NFS: Unbound, can they tell me how and with what configuration to open it?

My most recent attempt to run an EA App game with the latest proton experimental bleeding edge results in this log from EA background services:

     1  [2023-09-24T12:05:34.600Z]      PID:  1124      TID:  1144      INFO            (eax::apps::utils::logAppInfo)  Version: 13.27.0-5540-4ac8828f3
     2  [2023-09-24T12:05:34.600Z]      PID:  1124      TID:  1144      INFO            (eax::apps::utils::logAppInfo)  Command line: [C:\Program Files\Electronic Arts\EA Desktop\EA Desktop\EABackgroundService.exe -start]
     3  [2023-09-24T12:05:34.606Z]      PID:  1124      TID:  1184      INFO            (eax::foundation::security::allowAllUsersReadWriteAccess) Allowing all users read write access for path [C:\ProgramData\EA Desktop\machine.ini]
     4  [2023-09-24T12:05:34.796Z]      PID:  1124      TID:  1144      INFO            (eax::services::TelemetryDispatcher::Impl::setMachineHash)        Machash[876621c748d4dbd7fc542e60a93b2951496fe834]
     5  [2023-09-24T12:05:34.796Z]      PID:  1124      TID:  1144      INFO            (eax::apps::experimentation::ExperimentationSystem::refreshExperiments)   ExperimentsStatus=refreshing
     6  [2023-09-24T12:05:34.798Z]      PID:  1124      TID:  1156      INFO            (eax::apps::experimentation::`anonymous-namespace'::applySplitIoTreatments)       ExperimentsStatus=loaded
     7  [2023-09-24T12:05:34.798Z]      PID:  1124      TID:  1144      INFO            (eax::apps::graphql::init)      GraphQL init: env[url.production], url[https://service-aggregation-layer.juno.ea.com/graphql]
     8  [2023-09-24T12:05:34.799Z]      PID:  1124      TID:  1144      INFO            (eax::apps::graphql::init)      GraphQL service configured.
     9  [2023-09-24T12:05:34.800Z]      PID:  1124      TID:  1188      INFO            (eax::foundation::security::allowAllUsersReadWriteAccess) Allowing all users read write access for path [C:\ProgramData\EA Desktop\machine.ini]
    10  [2023-09-24T12:05:34.800Z]      PID:  1124      TID:  1144      INFO            (`anonymous-namespace'::overwriteOriginRegistryKeys)      Origin Keys have already been set, no need to reset them.
    11  [2023-09-24T12:05:34.801Z]      PID:  1124      TID:  1144      ERROR           (eax::services::localStorage::logOnError)       Operation [reading]: Could not find file or could not create containing folder for category "IQ", file path [C:\ProgramData\EA Desktop\530c11479fe252fc5aabc24935b9776d4900eb3ba58fdc271e0d6229413ad40e\IQ]
    12  [2023-09-24T12:05:34.803Z]      PID:  1124      TID:  1288      INFO            (eax::services::TelemetryDispatcher::Impl::logTelemetryEvent)     Telemetry Event: [{"authenticated":false,"criticalOffline":true,"criticality":false,"disableCulling":false,"enabled":true,"offline":false,"optional":false,"params":{"category":"IQ","ecode":1,"estr":"Storage file doesn't exist","src":"decrypt"},"taxonomy":"user.cache.erro","throttleCount":0,"timestamp":"2023-09-24T12:05:34.801","weight":0.0}]
    13  [2023-09-24T12:05:34.803Z]      PID:  1124      TID:  1288      INFO            (eax::services::TelemetryDispatcher::Impl::send) Telemetry event discarded due to stochastic culling: [user.cache.erro]
    14  [2023-09-24T12:05:34.810Z]      PID:  1124      TID:  1144      ERROR           (?)     [grpc] [server_secure_chttp2.cc:81] {"created":"@1695557134.810000000","description":"No address added out of total 1 resolved","file":"D:\p4\grpc\1.22.1\src\src\core\ext\transport\chttp2\server\chttp2_server.cc","file_line":396,"referenced_errors":[{"created":"@1695557134.810000000","description":"Failed to add port to server","file":"D:\p4\grpc\1.22.1\src\src\core\lib\iomgr\tcp_server_windows.cc","file_line":510,"referenced_errors":[{"created":"@1695557134.810000000","description":"OS Error","file":"D:\p4\grpc\1.22.1\src\src\core\lib\iomgr\tcp_server_windows.cc","file_line":201,"os_error":"Unable to retrieve error string","syscall":"bind","wsa_error":10049}]}]}
    15  [2023-09-24T12:05:34.812Z]      PID:  1124      TID:  1288      INFO            (eax::services::TelemetryDispatcher::Impl::logTelemetryEvent)     Telemetry Event: [{"authenticated":false,"criticalOffline":true,"criticality":false,"disableCulling":false,"enabled":true,"offline":false,"optional":false,"params":{"emsg":"[grpc] [server_secure_chttp2.cc:81] {\"created\":\"@1695557134.810000000\",\"description\":\"No address added out of total 1 resolved\",\"file\":\"D:\\p4\\grpc\\1.22.1\\src\\src\\core\\ext\\transport\\chttp2\\server\\chttp2_server.cc\",\"file_line\":396,\"referenced_errors\":[{\"created\":\"@1695557134.810000000\",\"description\":\"Failed to add port to server\",\"file\":\"D:\\p4\\grpc\\1.22.1\\src\\src\\core\\lib\\iomgr\\tcp_server_windows.cc\",\"file_line\":510,\"referenced_errors\":[{\"created\":\"@1695557134.810000000\",\"description\":\"OS Error\",\"file\":\"D:\\p4\\grpc\\1.22.1\\src\\src\\core\\lib\\iomgr\\tcp_server_windows.cc\",\"file_line\":201,\"os_error\":\"Unable to retrieve error string\",\"syscall\":\"bind\",\"wsa_error\":10049}]}]}","name":"bgs"},"taxonomy":"ipc.strt.erro","throttleCount":0,"timestamp":"2023-09-24T12:05:34.810","weight":0.0}]
    16  [2023-09-24T12:05:35.811Z]      PID:  1124      TID:  1144      FATAL           (eax::services::ipc::IpcServerImpl::runInternal) Unable to start IPC server[bgs]
    17  [2023-09-24T12:05:35.811Z]      PID:  1124      TID:  1144      ERROR           (eax::services::exception::ExceptionHandlerClient::Notify)        Whoops!

        ************  CRASH DETECTED  ************

    18  [2023-09-24T12:05:35.811Z]      PID:  1124      TID:  1144      ERROR           (eax::services::exception::ExceptionHandlerClient::Notify)        Gathering information about the crash - this may take some time...
    19  [2023-09-24T12:05:41.499Z]      PID:  1124      TID:  1144      INFO            (eax::services::exception::ExceptionHandlerClient::Notify)        ... crash information gathered - generating report...
    20  [2023-09-24T12:05:41.499Z]      PID:  1124      TID:  1144      INFO            (eax::services::exception::ExceptionHandlerClient::getCategoryIdString)   Crash Identifier [4C-DBD5]
    21  [2023-09-24T12:05:41.500Z]      PID:  1124      TID:  1144      INFO            (`anonymous-namespace'::startCrashReporter)     *** Crash notification was fired, starting crash reporter.
    22  [2023-09-24T12:05:41.528Z]      PID:  1124      TID:  1144      INFO            (eax::apps::startExecUsingExplorerCred) Starting client using explorer credentials: 'C:\Program Files\Electronic Arts\EA Desktop\EA Desktop\/EACrashReporter.exe' with args: '"C:\users\steamuser\AppData\Local\Electronic Arts\EA Desktop\Logs\temp101620397.tmp"'
    23  [2023-09-24T12:05:41.558Z]      PID:  1124      TID:  1144      INFO            (eax::services::exception::ExceptionHandlerClient::Notify)        ... report generation complete

Of particular interest is line 14 which states issues with attempting to bind a port. Here is line 14 properly formatted:

  "created":"@1695557134.810000000",
  "description":"No address added out of total 1 resolved",
  "file":"D:\p4\grpc\1.22.1\src\src\core\ext\transport\chttp2\server\chttp2_server.cc",
  "file_line":396,
  "referenced_errors":[
    {
      "created":"@1695557134.810000000",
      "description":"Failed to add port to server",
      "file":"D:\p4\grpc\1.22.1\src\src\core\lib\iomgr\tcp_server_windows.cc",
      "file_line":510,
      "referenced_errors":[
        {
          "created":"@1695557134.810000000",
          "description":"OS Error",
          "file":"D:\p4\grpc\1.22.1\src\src\core\lib\iomgr\tcp_server_windows.cc",
          "file_line":201,
          "os_error":"Unable to retrieve error string",
          "syscall":"bind",
          "wsa_error":10049
        }
      ]
    }
  ]
}

I decided to take a look at the referenced file and like the logs suggest, the error is triggered by grpc asserting that the OS could bind a new port.

I would like to try to line up my PROTON_LOG with EA's own logs but im not sure how I can do that from wine's timestamps. Any help from anyone knowledgeable with wine would be greatly appreciated.

I'm excited to say that I have found a temporary band-aid solution to play EA Games by replacing the EA App with Origin.
Here are the steps I took, starting from a clean prefix.

1. Go into the game's files, locate and delete the EA App installer then attempt to run the game. This will create the prefix.
2. Download and install the origin full installer from here to the prefix. I recommend using protontricks for this since it simplifies running programs inside the prefix. You can also use this command to run it WINEPREFIX=<path to prefix> wine <origin installer exe file>.
3. Once its installed, close origin and go into origin's install folder inside the prefix. Paste the following lines inside EACore.ini

[Bootstrap]
EnableUpdating=false

1. Grab version.dll from here and put it inside origin's install folder
2. Use winecfg to add a dll override for "version". Again, I recommend using protontricks for this but you can also run this command WINEPREFIX=<path to prefix> winecfg.

You can now launch the game and it should use Origin. Let me know if it works for anyone else.

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:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash ipv6.disable=1"

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.

@jmit79

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.
EA doesn't like if the total number of characters in environment variables exceeds ~32000.
This was a problem because I'm on a distro which relies on them (NixOS).
Unsetting the few big ones before launching Steam made Titanfall 2 work.

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):

for var in $(printenv | awk -F= 'length($2) > 2000 {print $1}'); do export $var=$(echo ${!var} | rev | cut -c 1-2000 | rev); done ; %command%

The reason there are two revs, is to truncate from the end (Steam appends some paths to some environment variables that it needs in order to load the Steam runtime: can't cut away those).

I have the same (I think!) problem with "Jedi Survivor":

• Game installed normally.
• At first start EA app was installed.
• EA app starts but I see just a black window.
  • this window has at least two editable fields (cursor changes from arrow to "I" beam)
  • I don't know what I'm supposed to enter there

I tried several Proton releases and also @riccardobl suggestion, but nothing worked.
I can post log, if deemed useful.
In some configurations after a few seconds of black window I get an explicit error:
"Something went wrong...
To continue linking your EA Account, head back and start over."

I have limited understanding of underlying structure (especially about interaction with EA
app) so be explicit in advice, please.

Replying to https://github.com/ValveSoftware/Proton/issues/6766#issuecomment-1824630431

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 have issue running Battlefield 5. First launch EA doesnt prompt for linking or anything it just hangs for 2-3secs and closes, I alredy linked my accaunt online. Checking later into steam game prefix "Program files/" EA play isnt installed. I have tried deleting pfx(whole steam prefix in compactdata) with Proton Exp, Proton 8 and 7, tried running it in gnome, no luck. Here is log:

steam-1238810.log

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.

Works for me on GE-Proton8-1. I've tried a couple of other versions and it is the only relatively new version of proton that worked so far.
Well, that makes me feel stupid, literally yesterday I had issues getting it to work in any version over 8-9 (the only one I had installed below that was 8-1)
But today I started increasing the GE-Proton version to see exactly where it breaks and… well, it works all the way up to the newest GE-Proton8-25.
I have no idea what was wrong yesterday >.<
So it appears like the only issue remaining now is, the "preparing game" EA app loading popup grabs focus of the Steam overlay and the game itself can't use it.

• Just a friendly reminder that the servers handling user generated trials will be disabled on 8'th of December… so it's a good moment to do these two achievements that require online features if you haven't done them already.

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.

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 (The Application has failed unexpectly). I've tested with every version of proton, using SteamOS 3.4

@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've had these crashes too. Problem was IPv6. I had disabled it long time ago in GRUB:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash ipv6.disable=1"

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

@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.

@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 prime-run. Every single game in my library requires prime-run to even acknowledge the dGPU's existence, but not TF2; it actually crashes when run with prime-run, and only launches properly when run without prime-run, in which case it still chooses the dGPU over the iGPU (don't know how that even works).

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 OPENSSL_ia32cap=~0x20000000 to the game's launch options.

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

[IPv4]
Address=192.168.178.30
Gateway=192.168.178.1

to my network's iwd.network configuration file (even though my network uses DHCP), the EA App and TF2 would launch properly again. It is beyond me why I need to specify my IP address in my network's iwd.network config if my computer receives this IP from the DHCP server anyway...

uname -rn: archlinux 6.8.2-arch1-1
Proton: 1711655084 experimental-9.0-20240328c
TF2 launch options OPENSSL_ia32cap=~0x20000000 %command% -novid

CPU: Intel i5-11400H
GPU: NVIDIA RTX 3050 (proprietary drivers, GL version 4.6.0 NVIDIA 550.67)

Replying to https://github.com/ValveSoftware/Proton/issues/6766#issuecomment-1731734674

@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've had these crashes too. Problem was IPv6. I had disabled it long time ago in GRUB:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash ipv6.disable=1"

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.

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.

uname -rn archlinux 6.12.1-arch1-1

Proton Experimental Log

lutris-wrapper: EA App
Started initial process 44593 from /home/john/.local/share/lutris/runtime/umu/umu_run.py /media/ssd/Games/ea-app/drive_c/Program Files/Electronic Arts/EA Desktop/EA Desktop/EALauncher.exe
Start monitoring process.
umu-launcher version 1.1.3 (3.12.7 (main, Oct  1 2024, 11:15:50) [GCC 14.2.1 20240910])
steamrt is up to date
Proton: Upgrading prefix from 7.0-100 to 9.0-202 (/media/ssd/Games/ea-app/)
wine: using kernel write watches, use_kernel_writewatch 1.
fsync: up and running.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.

Edit:
Solved moving from Proton 7 to Proton 8.

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:

• https://forum.endeavouros.com/t/ea-app-connection-failed/67260
• https://www.reddit.com/r/SteamDeck/comments/1imrklw/ea_app_connection_failed/

log: steam-1237970.log

If you need any additional info from me please ask!

https://github.com/ValveSoftware/Proton/issues/6729#issuecomment-2622214201 I've still got these results tragically.

steam-1774580.log

Trying to launch Dragon Age: Inquisition.
Says "There was an error on our side. Try again later".

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.

I have it already disabled, same game, but still not working.

I am having the same issue with the error shown by @Robmike27 when I launch Star Wars Battlefront II (2017) through Steam using Proton Hotfix and also when I launch the EA client using Lutris.

I'm on Ubuntu 24.10. Let me know if there is any information I can provide to help resolve this, I had been enjoying Battlefront II online with a friend for nearly a year before this issue cropped up.

@geckofish52 @Robmike27

I am using lutris and with one change the friendlist worked for me again:

1. Lutris
2. search for your "EA App" entry
3. at the bottom click on the arrow then "Wine-Configuration"
4. tab "Staging"
5. enable checkbox for "Hide Wine version from applications"

But that probably means EA is deliberately blocking Wine/Proton. Unfortunately, I don't know if circumventing it like that could lead to a ban.

Manjaro unstable aka Arch Linux
GE-Proton (Latest) from Lutris

Replying to https://github.com/ValveSoftware/Proton/issues/6766#issuecomment-2725725488

Unfortunately this is not enough to make games launch. I guess they are locked behind some drm stuff which wine is not compatible with.

@Galcian79
i play games without any problems.

• Star Wars Battlefront 2*
• Titanfall 2*
• Dragon Age Origins (longer ago)
• Star Wars Jedi: Fallen Order (longer ago)

I start the EA app via Lutris and then the games from there.

*i tested both games with EA App startet via GE-Proton and Proton experimental (from Steam) over past few days. I was able to play with both proton versions. But GE-Proton (with: ~"hide wine version" enabled) allows me to play Star Wars Battlefront 2 in a group with my friend.

Directx 12 uses much more VRAM and sometimes too much and the game crashes. Without DX12 Star Wars Battlefront 2 is running very well.

Replying to https://github.com/ValveSoftware/Proton/issues/6766#issuecomment-2727317014

Dragon Age: Inquisition shows "There was an error on our side. Try again"
Unless i'm missing some Windows components.

@Galcian79
"Dragon Age: Inquisition" also runs perfectly for me with GE-Proton (Latest) and Proton Experimental.
It's included in EAPlus, so I downloaded it today to test it.

I only tested single-player:
Start without "Dragone Age Keep"
Character unchanged
I skipped all video sequences for testing purposes where possible.
I get to the gameplay and can walk around.
I haven't tested any further, though. So far, no problems.

Replying to https://github.com/ValveSoftware/Proton/issues/6766#issuecomment-2727704659

Are you running the steam version or the origin version of the game, i mean downloading the installer from the website and adding it to steam as non steam app.

Hey @Galcian79 ,

non-steam.
I installed the EA App with Lutris (lutris version 0.5.19).

1. Lutris
2. Click the + in the top left corner
3. Search for installation scripts on the Lutris website
4. Search for "ea-app"
5. Install
6. Set the path for the prefix
7. Select the .exe file I previously downloaded using "Select File"
   (probably not necessary, as Lutris usually downloads the latest version)
8. Install
   But it's important not to log in yet and close the login window.

I can then select any Proton version for the EA app.
Either any provided by Steam or GE-Proton (Latest) from Lutris:

1. Search for "EA" in Games
2. Right-click on it
3. Configure
4. Tab: "Launcher Options"
5. Wine Version

If GE-Proton is selected, I can use the "Wine Configuration" option, as described in my previous post, to check the box to hide the Wine version for the applications.
Then the friends list in the EA app also works. Regardless, the games themselves work for me with Proton from Steam, as described, but without the EA friends list.

If GE-Proton is selected try:

1. Select the EA app in Lutris again
2. Stop it if running
3. Click the arrow next to the Wine logo below
4. Wine configuration
5. Tab: "Staging"
6. Check "Hide Wine version from applications"
7. If you want the EA App in Steam Lutris can create a Steam-Shortcut.

Manjaro kernel: Linux 6.13.7-1-MANJARO (unstable)
DE: KDE Plasma 6.3.3
WM: KWin (Wayland)
CPU: Intel(R) Core(TM) i7-4790K (8) @ 4.60 GHz  
GPU: NVIDIA GeForce GTX 1080 Ti [nvidia-dkms](https://archlinux.org/packages/extra/x86_64/nvidia-dkms/)

I'm aware that this doesn't solve the actual problem, but I hope this helps someone play their EA games on Linux or maybe the Proton developers to fix this issue.

Replying to https://github.com/ValveSoftware/Proton/issues/6766#issuecomment-2727317014

I don't get it, how are you starting these games? Do you own them outside of Steam? I can't launch them outside of Steam as they repeatedly tell me that I can only launch through, due to the dodgy EA verification key distribution system that Valve has to use as a third-party.

If I try to install them through Lutris but through Steam games on Lutris, it still raises the usual issues I've got...not sure what's going on there.

Also, the VRAM leak, could that be the same bug about XWayland and NVidia leading to VRAM leaking, that was reported to NVidia a while ago?

Replying to https://github.com/ValveSoftware/Proton/issues/6766#issuecomment-2729665299

This reinforces my suspicion about missing Windows components. I don't use Lutris because i want to avoid middleware if possible. Now i'm trying the Epic version of the game.

EDIT: I managed to launch it with Epic (works with experimental too) so it was DRM stuff afterall, or you have to kill the verify key process, as the Lutris install script suggest.
Anyway controller still diesn't works and it cannot detect d3d12 api.

@darkretailer

*i tested both games with EA App startet via GE-Proton and Proton experimental (from Steam) over past few days. I was able to play with both proton versions. But GE-Proton (with: ~"hide wine version" enabled) allows me to play Star Wars Battlefront 2 in a group with my friend.

Thank you so much for this! GE-Proton and the "Hide wine version from applications" in "Staging" tab in winecfg (ran via prototricks, which runs using the correct wine and prefix) was what I needed as I too was fighting with EA friends bar always showing "Connection failed" and thus being unable to get in groups with friends, while the game itself ran fine and could join random lobbies just fine. Now everything works like a charm! Gaming on Linux just keeps getting better.

I made the two changes:

• switch to Proton GE
• enable checkbox for "Hide Wine version from applications" using protontricks

And I can confirm that I now can connect to EA in order to join a party with my friend in Star Wars Battlefront II (2017) !

How are you launching it with Epic? I can't test this as I've purchased it through Steam, which means I can't move its platform to test. Confirmed they fail through Steam, through gamescope, through Proton Exp, through Proton-GE.

How are you launching it with Epic? I can't test this as I've purchased it through Steam, which means I can't move its platform to test. Confirmed they fail through Steam, through gamescope, through Proton Exp, through Proton-GE.

It works just fine using Heroic Games, but if you add the PROTON_ENABLE_WAYLAND=1 variable it just never start, it crashes when the launcher executes the link2ea wrapper.

Other EA games installed in the same prefix and running in pure wayland works fine, so it is a problem with link2ea and wayland compatibility:

0478:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwlr_data_control_manager_v1 (clipboard functionality will be limited)

0478:err:waylanddrv:wayland_process_init Wayland compositor doesn't support xdg_toplevel_icon_manager_v1 (window icons will not be supported)

Just wanted to chime in here. I was getting CTDs when launching Star Wars Battlefront 2 (the reboot one). I tried VK3D while offline and it worked flawlessly. Tried it online and now the game refuses to launch even while offline.

I bet its due to some cached integrity check. Mind you I was doing this under windows.

I have inconsistent behavior on, for example, Battlefield 4 and 3.
The games work fine for a couple of weeks and then randomly one day refuse to work and require reinstall.

This was on both proton 9 and 10 (GE)

With Mirror's Edge Catalyst in #6452 EA App installs and launches fine under Proton Experimental and GE-Proton-32/34, but once the initial loading screen is up for a few seconds the game crashes.

A "non-EA" copy does not suffer that problem and works just fine, so there's something on the EA App side that broke something.

I got Mirror's Edge Catalyst to launch by doing the following:

1. Set the game to use Proton Experimental
2. Set the following launch options: PROTON_DISABLE_NVAPI=1 PROTON_NO_ESYNC=1 PROTON_USE_XALIA=0 %command%
3. Add this line to my /etc/hosts file: 127.0.0.1 winter15.gosredirector.ea.com
4. When EA App install screen pops up instead of clicking "let's go" click on "customize setup" and uncheck the box "create desktop shortcut"

In case your issue is the environment variable one, a workaround is setting as launch options (from Steam):

for var in $(printenv | awk -F= 'length($2) > 2000 {print $1}'); do export $var=$(echo ${!var} | rev | cut -c 1-2000 | rev); done ; %command%

The reason there are two revs, is to truncate from the end (Steam appends some paths to some environment variables that it needs in order to load the Steam runtime: can't cut away those).

OMG THANK YOU, I spent A WEEK trying to get Mass Effect Legendary Edition working and it finally did :D. I also use NixOS, so maybe that is a bug with the way Steam is packed here? I don't know, but thank you for your workaround :)

OMG THANK YOU, I spent A WEEK trying to get Mass Effect Legendary Edition working and it finally did :D. I also use NixOS, so maybe that is a bug with the way Steam is packed here? I don't know, but thank you for your workaround :)

The issue isn't with Steam's packaging itself, it's https://github.com/NixOS/nixpkgs/issues/126590.

NixOS Unstable (in the future NixOS 26.05) has a partial fix which should be enough for EA App. (Linked in that issue.)
Proton 11 also has a workaround for the same thing: https://github.com/ValveSoftware/wine/commit/a99dc1a779c392980aed0ff12149a2b33966693e.

_{It should also be noted that the issue is technically not in Wine/Proton, but in the EA App itself, as the issue is also reproducible on Windows (though no one is going to naturally have a huge amount of environment variables there). I already tried to contact EA, and I was ignored.}