Open stixholder opened 1 year ago
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 PROTON_LOG=1 %command%
to the game's launch options, reproduce the regression and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam
-> Help
-> System Information
) and put it in a gist, then include a link to the gist in this issue report.
@kisak-valve, see my message in #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.
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:
Jul 30 22:53:56 klx99 plasmashell[9864]: fsync: up and running.
Jul 30 22:53:56 klx99 plasmashell[9864]: wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
Jul 30 22:53:56 klx99 plasmashell[9872]: ERROR: ld.so: object '/home/marcus/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Jul 30 22:53:56 klx99 plasmashell[9874]: ERROR: ld.so: object '/home/marcus/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Jul 30 22:53:56 klx99 plasmashell[9879]: ERROR: ld.so: object '/home/marcus/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Jul 30 22:53:56 klx99 plasmashell[9890]: ERROR: ld.so: object '/home/marcus/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Jul 30 22:53:56 klx99 plasmashell[9903]: ERROR: ld.so: object '/home/marcus/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Jul 30 22:53:56 klx99 plasmashell[9911]: ERROR: ld.so: object '/home/marcus/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Jul 30 22:53:57 klx99 plasmashell[9303]: ThreadGetProcessExitCode: no such process 9872
Jul 30 22:53:57 klx99 plasmashell[9303]: ThreadGetProcessExitCode: no such process 9863
Jul 30 22:53:57 klx99 plasmashell[9303]: ThreadGetProcessExitCode: no such process 9859
Jul 30 22:53:57 klx99 plasmashell[9928]: ERROR: ld.so: object '/home/marcus/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Jul 30 22:53:57 klx99 plasmashell[9303]: Game process updated : AppID 1238840 "RADV_PERFTEST=sam,bolist DXVK_ASYNC=1 DXVK_GPLASYNCCACHE=1 /home/marcus/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=1238840 -- >
Jul 30 22:53:57 klx99 plasmashell[9861]: Setting breakpad minidump AppID = 1238840
Jul 30 22:53:57 klx99 plasmashell[9861]: Steam_SetMinidumpSteamID: Caching Steam ID: 76561198090414751 [API loaded no]
Jul 30 22:53:57 klx99 plasmashell[9953]: ERROR: ld.so: object '/home/marcus/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Jul 30 22:53:58 klx99 kded5[3182]: Registering ":1.112/StatusNotifierItem" to system tray
Jul 30 22:53:58 klx99 kded5[3182]: Service ":1.112" unregistered
Jul 30 22:53:59 klx99 plasmashell[9303]: Game process added : AppID 1182480 "", ProcID 9953, IP 0.0.0.0:0
Jul 30 22:54:03 klx99 plasmashell[10456]: ERROR: ld.so: object '/home/marcus/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Jul 30 22:54:03 klx99 kwin_x11[3183]: kwin_core: XCB error: 152 (BadDamage), sequence: 10024, resource id: 14741400, major code: 143 (DAMAGE), minor code: 3 (Subtract)
Jul 30 22:54:03 klx99 plasmashell[10456]: info: Game: EABackgroundService.exe
Jul 30 22:54:03 klx99 plasmashell[10456]: info: DXVK: v1.10.1-1318-g6be1f6d7bd5f8320
Jul 30 22:54:03 klx99 plasmashell[10456]: info: Vulkan: Found vkGetInstanceProcAddr in winevulkan.dll @ 0x2d4ad4500
Jul 30 22:54:03 klx99 plasmashell[10456]: info: Built-in extension providers:
Jul 30 22:54:03 klx99 plasmashell[10456]: info: Win32 WSI
Jul 30 22:54:03 klx99 plasmashell[10456]: info: OpenVR
Jul 30 22:54:03 klx99 plasmashell[10456]: info: OpenXR
Jul 30 22:54:03 klx99 plasmashell[10456]: warn: OpenXR: Unable to get required Vulkan instance extensions size
Jul 30 22:54:03 klx99 plasmashell[10456]: info: Enabled instance extensions:
Jul 30 22:54:03 klx99 plasmashell[10456]: info: VK_EXT_surface_maintenance1
Jul 30 22:54:03 klx99 plasmashell[10456]: info: VK_KHR_get_surface_capabilities2
Jul 30 22:54:03 klx99 plasmashell[10456]: info: VK_KHR_surface
Jul 30 22:54:03 klx99 plasmashell[10456]: info: VK_KHR_win32_surface
Jul 30 22:54:03 klx99 plasmashell[10456]: warn: OpenXR: Unable to get required Vulkan Device extensions size
Jul 30 22:54:03 klx99 plasmashell[10456]: info: AMD Radeon RX 6950 XT (RADV NAVI21):
Jul 30 22:54:03 klx99 plasmashell[10456]: info: Driver : radv 23.2.99
Jul 30 22:54:03 klx99 plasmashell[10456]: info: Memory Heap[0]:
Jul 30 22:54:03 klx99 plasmashell[10456]: info: Size: 32074 MiB
Jul 30 22:54:03 klx99 plasmashell[10456]: info: Flags: 0x0
Jul 30 22:54:03 klx99 plasmashell[10456]: info: Memory Type[2]: Property Flags = 0x6
Jul 30 22:54:03 klx99 plasmashell[10456]: info: Memory Type[5]: Property Flags = 0xe
Jul 30 22:54:03 klx99 plasmashell[10456]: info: Memory Type[6]: Property Flags = 0xe
Jul 30 22:54:03 klx99 plasmashell[10456]: info: Memory Type[8]: Property Flags = 0xc6
Jul 30 22:54:03 klx99 plasmashell[10456]: info: Memory Type[10]: Property Flags = 0xce
Jul 30 22:54:03 klx99 plasmashell[10456]: info: Memory Heap[1]:
Jul 30 22:54:03 klx99 plasmashell[10456]: info: Size: 16368 MiB
Jul 30 22:54:03 klx99 plasmashell[10456]: info: Flags: 0x1
Jul 30 22:54:03 klx99 plasmashell[10456]: info: Memory Type[0]: Property Flags = 0x1
Jul 30 22:54:03 klx99 plasmashell[10456]: info: Memory Type[1]: Property Flags = 0x1
Jul 30 22:54:03 klx99 plasmashell[10456]: info: Memory Type[3]: Property Flags = 0x7
Jul 30 22:54:03 klx99 plasmashell[10456]: info: Memory Type[4]: Property Flags = 0x7
Jul 30 22:54:03 klx99 plasmashell[10456]: info: Memory Type[7]: Property Flags = 0xc1
Jul 30 22:54:03 klx99 plasmashell[10456]: info: Memory Type[9]: Property Flags = 0xc7
Jul 30 22:54:04 klx99 plasmashell[10540]: ERROR: ld.so: object '/home/marcus/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Jul 30 22:54:04 klx99 plasmashell[10567]: ERROR: ld.so: object '/home/marcus/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Jul 30 22:54:04 klx99 plasmashell[9953]: LLVM ERROR: Unable to allocate section memory!
Jul 30 22:54:07 klx99 pressure-vessel-wrap[10752]: i386-linux-gnu-capsule-capture-libs: warning: we are assuming "__gnu_lto_slim" to be public, but it's just a guess
Jul 30 22:54:07 klx99 pressure-vessel-wrap[10752]: i386-linux-gnu-capsule-capture-libs: warning: we are assuming "__gnu_lto_slim" to be public, but it's just a guess
Jul 30 22:54:07 klx99 pressure-vessel-wrap[10752]: i386-linux-gnu-capsule-capture-libs: warning: we are assuming "__gnu_lto_slim" to be public, but it's just a guess
Jul 30 22:54:09 klx99 pressure-vessel-wrap[10968]: i386-linux-gnu-capsule-capture-libs: warning: we are assuming "__gnu_lto_slim" to be public, but it's just a guess
Jul 30 22:54:09 klx99 pressure-vessel-wrap[10968]: i386-linux-gnu-capsule-capture-libs: warning: we are assuming "__gnu_lto_slim" to be public, but it's just a guess
Jul 30 22:54:09 klx99 pressure-vessel-wrap[10968]: i386-linux-gnu-capsule-capture-libs: warning: we are assuming "__gnu_lto_slim" to be public, but it's just a guess
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:
0) Install protontricks >= 1.10.1 from flathub (the older version in ubuntu repos won't work) [2] 1) Delete the proton prefix for the game if it exists due to previous attempts 2) In the compatibility tab select "Force the use of a specific Steam Play compatibility tool" and select proton 8.0-3 3) Start the game 4) 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. 5) Close the game from steam 6) Open protontricks 7) Select the game 8) Select "Select the default wineprefix" and click OK 9) Select "Install a Windows DLL or component" and click ok 10) Select "d3dcompiler_47" and click OK [1] 11) Wait until your are taken back to the protontricks window 12) Select "Install a font" and click OK 13) Select "liberation" and click OK [1] 14) 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]) 15) Click X to close protontricks 16) Start the game 17) 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?
Hello @onurbbr, that reads like game-specific feedback which would be better off on #6502.
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.
WINEPREFIX=<path to prefix> wine <origin installer exe file>
.[Bootstrap]
EnableUpdating=false
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 rev
s, 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":
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:
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.
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.
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 https://github.com/ValveSoftware/Proton/issues/6617#issuecomment-1543262465
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.