Just like it happened with Wild Hearts and probably any other EA game the log is huge and even compressed can not be put here on github. @kisak-valve here is an external link with it https://mega.nz/file/K49VAKYS#n0qZ71MahtG9H3KL3jhIViV6mF5khD1S9MYskFeNAYE.

I think that what I'm seeing is a problem in the RX 7900 XT driver

[  144.136413] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=647, emitted seq=648
[  144.136591] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process JediSurvivor.ex pid 5658 thread JediSurvivor.ex pid 5917
[  144.136719] amdgpu 0000:03:00.0: amdgpu: GPU reset begin!
[  145.153243] [drm:sdma_v6_0_ring_test_ib [amdgpu]] *ERROR* amdgpu: IB test timed out
[  145.153409] amdgpu 0000:03:00.0: amdgpu: IP block:sdma_v6_0 is hung!
[  145.154480] amdgpu 0000:03:00.0: amdgpu: IP block:sdma_v6_0 is hung!
[  145.154480] amdgpu 0000:03:00.0: amdgpu: soft reset failed, will fallback to full reset!

drm:amdgpu_job_timedout

Or could it be that the game is doing something weird that is taking so long to finish that the driver is restarting the gpu as a last resort?

I think that what I'm seeing is a problem in the RX 7900 XT driver

[  144.136413] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=647, emitted seq=648
[  144.136591] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process JediSurvivor.ex pid 5658 thread JediSurvivor.ex pid 5917
[  144.136719] amdgpu 0000:03:00.0: amdgpu: GPU reset begin!
[  145.153243] [drm:sdma_v6_0_ring_test_ib [amdgpu]] *ERROR* amdgpu: IB test timed out
[  145.153409] amdgpu 0000:03:00.0: amdgpu: IP block:sdma_v6_0 is hung!
[  145.154480] amdgpu 0000:03:00.0: amdgpu: IP block:sdma_v6_0 is hung!
[  145.154480] amdgpu 0000:03:00.0: amdgpu: soft reset failed, will fallback to full reset!

Did your desktop crash and brought you back to login screen?

Did your desktop crash and brought you back to login screen?

No. As surprising as it may seem the full gpu reset is working flawlessly and I was not forced to logout. The desktop just freezes for a few seconds and after that I can open gnome process manager to kill the game and try again. It usually works in the third try.

Any one else having this issue?

No. I have one of those generic xbox controllers and at least on wire it is working. I did not try its bluetooth connection with this game yet. But it works on others.

I am under the impression that there is controller settings in there, but because I can't get into it I can't check the settings.

I do not remember having seen controller settings there.

@sp1ne7 Looking at your specs I see we have very different kernel versions. Maybe the old kernel is the problem.

Try to take a look at the output of sudo journalctl -b | grep -i steam after starting the game with the controller plugged. Maybe it will show something about it.

Here you go.
How is my kernel version older if my Ubuntu is up to date? I just updated like half hour ago.

outputcontroller.txt

How is my kernel version older if my Ubuntu is up to date? I just updated like half hour ago.

The current stable kernel version is 6.3.1. As I use Arch Linux I do not know if there is a PPA providing it for a LTS Ubuntu release. In any case the problem may or may not be the kernel version. So at this moment I would not try to take drastic approaches to upgrade the kernel.

Unfortunately I did not see anything in the journaltcl output that could help to fix your problem. But I see that steam used the PROTON_LOG variable you set. Are you sure no proton log file was created in your user home folder?

It generated one this time. But its like 1.3GB large it won't let me upload it.

protonlog.txt

I copied like the first 10000 lines or so of it at least. I scrolled through a huge portion of it and it looks like it just repeats a of the same things after a certain point so maybe this will be okay.

I also still had it on Proton 8 ge from when I was testing. I put it back to experimental

Hi there.
Don't spend too much time troubleshooting this. I may be wrong about my controller being the issue after all.
Jedi Survivor was an exclusive for PS5, XBOX and PC only. Therefore my Dualshock 4 PS4 controller may not be natively supported, hence why it may also not be working on Linux.

I'm picking up a DS5 controller today and testing it when I get home, so I'll let you know if it works sometime today and then you can close out this issue.

Hi there,

I have confirmed that my Dualshock 4 controller was the issue. My Dualshock 5 controller I just purchased is working just fine, but you have to disabled steam input.

Forgive me for not considering that my controller could have been the issue. This is not a compatibility issue with proton, but was an issue between the dualshock 4 controller and this game.

You can close this issue, but please keep it documented so it can help others solve this issue. Thank you.

I can't launch Jedi Survivor today. It was working fine a few days ago. Is EA APP broken again? It doesn't even seem to launch. Here's my Proton log:
steam-1774580.log

I can't launch Jedi Survivor today. It was working fine a few days ago. Is EA APP broken again? It doesn't even seem to launch. Here's my Proton log:

Try to delete the proton prefix folder. I had to do this after the game update that was released this week. Just deleting the shader cache was not enough for it to stop crashing.

Thanks! Yeah I just tried that, it hung at 100% progress completion during the EA app install, but I clicked Close and Cancel Install, and it proceeded through and launched the game! Works every time I launch it now. Weird how the Proton prefix just broke like that though.

Weird how the Proton prefix just broke like that though.

Considering that many windows users are complaining about crashes caused by the latest game update I think that Proton is not the one to blame. By deleting the prefix we probably removed some kind of game configuration or cache that is not compatible with the latest update.

Sometimes, it just doesn't launch, though it might be just the EA app itself
steam-1774580.log

https://github.com/ValveSoftware/Proton/issues/6396

@YamiYukiSenpai It wouldn't launch for me after the latest updates (Proton Experimental and SteamOS Beta), I deleted the proton files and that fixed it

I can't launch Jedi Survivor today. It was working fine a few days ago. Is EA APP broken again? It doesn't even seem to launch. Here's my Proton log:

Try to delete the proton prefix folder. I had to do this after the game update that was released this week. Just deleting the shader cache was not enough for it to stop crashing.

This +1

Came across a similar issue: 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!

Proton Experimental bleeding-edge seems to break the game while the regular Proton Experimental works as expected. The game freezes while compiling shaders and sometimes during the intro video (probably compiling during the intro video)

Yesterday's Patch 6 broke the game again, cannot launch it with any Proton, including the Proton-GE. EA app is not even trying to start, going directly from Starting -> Stopped. Don't see any obvious issue in the console output

Yesterday's Patch 6 broke the game again, cannot launch it with any Proton, including the Proton-GE. EA app is not even trying to start, going directly from Starting -> Stopped. Don't see any obvious issue in the console output

Try clearing the proton prefix. Experimental works for me :)

Yesterday's Patch 6 broke the game again, cannot launch it with any Proton, including the Proton-GE. EA app is not even trying to start, going directly from Starting -> Stopped. Don't see any obvious issue in the console output

Try clearing the proton prefix. Experimental works for me :)

Hm, maybe I've removed the wrong one yesterday? Anyway it helped, thanks, it's the EA app that's acting up again...

Since, we're talking, people with AMD GPU, do you also experience following issue, like I do: https://gitlab.freedesktop.org/mesa/mesa/-/issues/8934#note_1891809 ? I found a video online with another 7900 XTX which does show same issues and some recordings of nVidia 4090 on linux without said issues. I'm wondering if it's all AMD GPUs or only 7000-series.

Since, we're talking, people with AMD GPU, do you also experience following issue, like I do: gitlab.freedesktop.org/mesa/mesa/-/issues/8934#note_1891809 ? I found a video online with another 7900 XTX which does show same issues and some recordings of nVidia 4090 on linux without said issues. I'm wondering if it's all AMD GPUs or only 7000-series.

Looked like that on my 6800XT at launch but running the latest mesa-git seems to fix it for me

Since, we're talking, people with AMD GPU, do you also experience following issue, like I do: gitlab.freedesktop.org/mesa/mesa/-/issues/8934#note_1891809 ? I found a video online with another 7900 XTX which does show same issues and some recordings of nVidia 4090 on linux without said issues. I'm wondering if it's all AMD GPUs or only 7000-series.

Looked like that on my 6800XT at launch but running the latest mesa-git seems to fix it for me

Yeah, I've just tried latest mesa-git and it seems to be much better at least in a opening scene, will retest tonight, thanks for the input @ErikReider

I just want to leave this here because it might be something proton can do something about, but mainly because it can help others troubleshoot:
When I FPS limit the game with mangohud, it significantly increases load times. It takes literal minutes to load a level when capped at 40 FPS. However if I remove the FPS limit on the load screen, it takes only seconds. Hope the word gets around, because I have not found anyone else reporting this so far.

The game was running just fine on my RTX 4070 with the "high" graphics preset and DLSS, but I just reached the Forest Array on Koboh, and performance is now under 10fps, making it unplayable.
I've tried lowering the details ("medium" then "low"), it barely helps, making me thing something else is at play.
I know this game has terrible performance in general, but this seems really bad and running way worse on Proton than on Windows.
Is there any known workaround?

Replying to https://github.com/ValveSoftware/Proton/issues/6729#issuecomment-1860022229

I had the same thing and I highly suspect it's those particles flying around there. Their performance seems to be CPU-bound. I went through it by lowering my resolution and turning everything to low settings for that part. Also it seemed like the AMD upscaler did a better job in that part than the NVidia one.

Interesting behavior:
Jedi: Survivor won’t finish starting up if Proton 8.0-5 is set as the default version of Proton for all games, but the game will start & run OK if Experimental remains the default (using 8.0-5 for J:S only). The game runs fine under Experimental (the latest build from 1/11/24, I believe).
OS: Arch Linux running Gnome 45.3 in Wayland (so Steam games in Xwayland), vanilla kernel 6.7, Mesa 23.3.3, MangoHud 0.7.0, Gamemode 1.7 (NOT latest 1.8.1, which seems to have no effect & tests crash; separate issue).
Steam client: system package (not flatpak; none of above packages are), latest updates. Yes, running multilib so I have the necessary 32-bit packages.
Hardware: 9700K, RX 6600 XT, 32GB 3600MHz DDR4 RAM running XMP

Game seems to crash for me after a few minutes with Proton Experimental on my Steam Deck OLED. Happened before the latest Experimental update too, so I don't think it's tied to that. Used to run without crashing, performance issues aside.

Just launched for the first time today; I've tried Proton Experimental as well as GE 8-16. Running with -d3d11 because I got a dx12 error the first try.

On start I get this confusing error message:

About my AMD driver being wrong even though it's nvidia.

Then the game launches to a black screen (with my desktop cursor), stays there for a while, then crashes with:

LowLevelFatalError [File:Unknown] [Line: 1024] 
Rendering thread exception:
LowLevelFatalError [File:Unknown] [Line: 258] 
Direct3DDevice->CreateShaderResourceView failed 
 at D:/depot/r8branches/r8release/Engine/Source/Runtime/Windows/D3D11RHI/Private/D3D11UAV.cpp:249 
 with error E_INVALIDARG




0x00000001421e78f7 JediSurvivor.exe!UnknownFunction []
0x00000001421d9901 JediSurvivor.exe!UnknownFunction []
0x0000000143845021 JediSurvivor.exe!UnknownFunction []
0x00000001438456be JediSurvivor.exe!UnknownFunction []
0x0000000143843db3 JediSurvivor.exe!UnknownFunction []
0x0000000141c143fd JediSurvivor.exe!UnknownFunction []
0x0000000141c14483 JediSurvivor.exe!UnknownFunction []
0x0000000142dc7f42 JediSurvivor.exe!UnknownFunction []
0x0000000142dc8bd3 JediSurvivor.exe!UnknownFunction []
0x0000000141d65557 JediSurvivor.exe!UnknownFunction []
0x0000000141d605a1 JediSurvivor.exe!UnknownFunction []
0x00006fffffed473d kernel32.dll!UnknownFunction []

NixOS 23.11, updated, RTX3060

nvidia-smi 
Fri Mar 15 18:30:20 2024       
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 545.29.02              Driver Version: 545.29.02    CUDA Version: 12.3     |
|-----------------------------------------+----------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |         Memory-Usage | GPU-Util  Compute M. |
|                                         |                      |               MIG M. |
|=========================================+======================+======================|
|   0  NVIDIA GeForce RTX 3060        Off | 00000000:01:00.0  On |                  N/A |
|  0%   44C    P8              19W / 170W |   1924MiB / 12288MiB |     20%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+

Has anyone all of a sudden.. maybe in the past couple of weeks run into a problem where the game won't even launch from the EA APP? I get the message about unable to launch from our end. I didn't play the game much just made sure it launched and worked which it did and it ran nicely a couple months back. Now all of a sudden it won't launch from the EA APP.. GRR. I tried removing the pfx as well as the whole game.. Tried multiple proton versions and no dice. Any thoughts/suggestions. I'm on Endeavouros (arch)

Update on this comment. I re-installed and chose the proton version beta 9. I don't know if this was the issue.. part of the issue or what.. or if it was "truly a problem on their end" EA.. SIGH

@77boaz Does it still work for you? Bought it this week and have had no luck so far with any proton version. Game did open one or two times (via the EA app launched by Steam) but controller was not working so I exited, and haven't been able to get back in since :/

@ammgws It's actually interesting you ask this because I just fired it up yesterday and now it won't launch! It looks like EA changed their app yet again.. it looks very different from before.. it's super annoying...

Strangely I tried installing on my Steam Deck and it opened and played first time :/
Nuked the game dir on PC and tried redownloading but still the same launch error message from the EA app

I've tried yesterday on my freshly re-installed Desktop and it worked out of the box without issues

So it's interesting.. I have not yet tried again, but I was able to get it to launch back again when it did not launch by blowing everything away, and when I mean everything I mean.. the prefix.. PFX and the common folder(s).. Reinstalling it. I guess I'm wondering at what level we would have to delete the whole thing. Obviously blowing away the prefix (pfx) is not that big of a deal, but it will/would stink if we have to blow away the entire game and then re-download and re-install for it to keep working lol. Especially since it's one of the biggest; if not the biggest game I currently have size wise. :)

So it's interesting.. I have not yet tried again, but I was able to get it to launch back again when it did not launch by blowing everything away, and when I mean everything I mean.. the prefix.. PFX and the common folder(s).. Reinstalling it. I guess I'm wondering at what level we would have to delete the whole thing. Obviously blowing away the prefix (pfx) is not that big of a deal, but it will/would stink if we have to blow away the entire game and then re-download and re-install for it to keep working lol. Especially since it's one of the biggest; if not the biggest game I currently have size wise. :)

You can always backup game files and restore them, this will "Install game" from local files, not the internet, so you can backup (Game -> Properties -> Local Files -> Backup game files) -> delete -> cleanup pfx -> Restore and that would be a clean install.

So it's interesting.. I have not yet tried again, but I was able to get it to launch back again when it did not launch by blowing everything away, and when I mean everything I mean.. the prefix.. PFX and the common folder(s).. Reinstalling it. I guess I'm wondering at what level we would have to delete the whole thing. Obviously blowing away the prefix (pfx) is not that big of a deal, but it will/would stink if we have to blow away the entire game and then re-download and re-install for it to keep working lol. Especially since it's one of the biggest; if not the biggest game I currently have size wise. :)

You can always backup game files and restore them, this will "Install game" from local files, not the internet, so you can backup (Game -> Properties -> Local Files -> Backup game files) -> delete -> cleanup pfx -> Restore and that would be a clean install.

Oh sweet DUH.. I have done that in the past but only on Windows.. I guess I wasn't sure how much of an 'actual' complete install it was. I don't know if there are any inner workings online vs. offline which could be any different. I will try that thanks!

Yeah I am getting a failure to launch as of 5/7/2024 as well:

EDIT: Completely uninstalling and reinstalling did not fix the issue for me.

Okay, seems like no matter what I do with Proton Experimental it will show the "Error on our end" failure. But if I switch to Proton 9.0-1 and clear my prefix, I can get the game to launch once. Subsequent launches just crash and the Steam play button turns green again.

I tried re-installing and blowing everything away last night and I still get the same error you're getting above.. "Problem on our end" I tried the most recent proton and some older ones.. even the latest Proton GE and no dice. I got this message before.. Maybe it truly is a problem on their end.. Before I remember it just seemed to suddenly one day start working. Fortunately I've shelved the game to play later as this is definitely annoying... :)

I also get this with Star Wars Battlefront 2. I wonder if it's broken for all EA games...?

Well, I just tried it right now. Blew away the proton prefix, selected Proton Experimental and lo and behold it magically started working again, even across multiple launches. So strange.

I reinstalled the game recently and cannot get it to work. I've tried different proton versions, and removing my prefix.
Here is the proton log:
steam-1774580.log

Specs:

~ >>> neofetch                                                                            [127]
██████████████████  ████████   mikaka@stacjonarny 
██████████████████  ████████   ------------------ 
██████████████████  ████████   OS: Manjaro Linux x86_64 
██████████████████  ████████   Host: MS-7D96 2.0 
████████            ████████   Kernel: 6.9.2-1-MANJARO 
████████  ████████  ████████   Uptime: 5 hours, 31 mins 
████████  ████████  ████████   Packages: 2458 (pacman), 75 (flatpak), 27 (snap) 
████████  ████████  ████████   Shell: zsh 5.9 
████████  ████████  ████████   Resolution: 2560x1440 
████████  ████████  ████████   DE: Plasma 6.0.5 
████████  ████████  ████████   WM: kwin 
████████  ████████  ████████   WM Theme: Materia-Dark 
████████  ████████  ████████   Theme: Materia Dark [Plasma], Materia-dark [GTK2/3] 
████████  ████████  ████████   Icons: Papirus-Dark [Plasma], Papirus-Dark [GTK2/3] 
                               Terminal: konsole 
                               Terminal Font: Noto Mono 10 
                               CPU: 13th Gen Intel i5-13600K (20) @ 5.100GHz 
                               GPU: Intel Raptor Lake-S GT1 [UHD Graphics 770] 
                               GPU: AMD ATI Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT 
                               Memory: 10201MiB / 31860MiB 

EDIT: I was able to fix this myself. I had to use protontricks to install EAApp in the prefix. After that the game works fine.

Sometimes the game doesn't want to run. The PLAY button, after a short time, became green again without any game windows.

Proton log: steam-1774580.zip

Basically unplayable on my Nvidia GPU.
The game happily allocated VRAM even when there is none to allocate, my RTX 2080 on 555.58.02 has 8GB of VRAM, when the game is nearing this amount (checked via mangohud), the video freezes up, game still gets input as audio is playing.
Checking dmesg I see the error: [drm:nv_drm_gem_alloc_nvkms_memory_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to allocate NVKMS memory for GEM object
Tried to limit the max VRAM with a dxvk.conf entry dxgi.maxDeviceMemory = 3840 but the issue still persist. (I also tried different Proton versions)

System Information

• GPU: AMD Radeon 7900XTX
• Video driver version: Mesa 24.3 devel
• Kernel version: 6.11-rc6, 6.10.6
• Link to full system information report as Gist: https://gist.github.com/matte-schwartz/ed9686721d69e7dc1a88138d70b0e0ec
• Proton version: experimental-bleeding-edge-9.0-117156-20240904-p825585-w322ce67-dd0ea5a-v0d0e1b (Proton 9-02 also does not work anymore)

steam-1774580-crash.log

Symptoms

After shutting down my PC last night, turning it on, and then attempting to switch Proton versions, I can't seem to get past the point of the EA App launcher briefly appearing before the game crashes without ever launching. So far no amount of clearing Prefixes or trying other Proton versions has helped, even the same proton version as last night. Mesa version hasn't changed since it was working, neither has my kernel. Frankly I'm a bit baffled... I will keep tinkering to see if maybe I can coax the EA Launcher into working again.

Reproduction

No idea how to make this consistently reproable if I'm being honest. It happened after several hours of perfect gameplay last night with zero issues. Launching within gamescope or Plasma desktop makes no difference either.

EDIT: I've figured out the issue (or at least what I think the issue is). I am able to reliably trigger the game failing to launch if I launch the game on one Linux kernel and then attempt to switch to another Linux kernel. Whenever I do this, the EA Play app seems to decide to get rid of my cached license files in pfx/drive_c/ProgramData/Electronic Arts/EA Services/Licensepfx/drive_c/ProgramData/Electronic Arts/EA Services/License. I was able to find this after diffing a "good" pfx folder that I saved earlier and a "bad" pfx folder once I switched kernels.

Relevant new logs:

Notably, the game itself seems to activate just fine, it's only the EA App that complains.

EAapp_OnlineActivation_Log.html: https://gist.github.com/matte-schwartz/4b2cf8facb41e3b4449b1d5fac818f86

JediSurvivor_198300_OnlineActivation_Log.html: https://gist.github.com/matte-schwartz/e728618011385fceaf3f9921049b1a9c

~/Desktop/1774580-boot/pfx/drive_c/ProgramData/Electronic Arts/EA Services/License
❯ ls
.rwxr-xr-x 2.5k matt  4 Sep 18:27  198300.dlf
.rw-r--r-- 2.5k matt  4 Sep 18:27  198300_cached.dlf

vs

~/Desktop/1774580-noboot/pfx/drive_c/ProgramData/Electronic Arts/EA Services/License
❯ ls

Manually dropping the License files into place does not work - the EA app just gets rid of them again.

Specs

OS: Debian GNU/Linux trixie/sid x86_64
Kernel: 6.11.10-amd64
DE: GNOME 47.2
CPU: Intel i9-9900K (16) @ 5.000GHz
GPU: NVIDIA GeForce RTX 2080 Ti Rev. A

Issue

I can't seem to get the EA App to work at all, I've launched the game via steam probably over 100 times now and have not once managed to get the EA App to launch successfully.

I have tried useing the following Proton versions:

• Proton Experimental
• Proton 9.0-3
• Proton 8.0-5
• Proton 7.0-6
• GE-Proton9-20
• GE-Proton9-11

I have tested with deleting the prefix before switching versions, not deleting before switching versions, running the init in Proton 7.0-6 then switching to Experimental to run the game. I've tried a bunch of different launch options suggested on ProtonDB.

At this point I'm not really sure what else to try, I just can't get passed this:

Which then closes and shows this:

(Sometimes with a helpful message telling me "The EA app has minimised").

At this point I have almost an hour in game recorded on steam and the game hasn't successfully launched once.

Any help or suggestions would be massively appreciated <3.

After 15 hours of play time the game stopped working on my both my Pop!OS and Bazzite installations for whatever reason, probably something to do with EA App. For Pop!OS I simply had to delete the the game's Proton prefix (1774580) in the compatdata folder and make Steam run through the first-time setup again. In Bazzite the EA app installer would always instantly close during setup so I had to manually install it to the prefix with Protontricks.

Edit: Used Proton Experimental in case that's a factor.

I've got these logs to match any EA app launch - "failed to launch the game."

steam-1172380.log

(I should note the picture is just jedi fallen order but is the exact same for jedi survivor.)

Weirdly, this issue wasn't happening two or three months ago. It might be a regression as usual. That or an update to EA DRM and how crap it is. Using Wayland btw.

The install script to install the EA App during the game launch seems to open and then close immediately before continuing on with setting up the prefix on my Intel Lunar Lake handheld. This leads to Steam thinking that the game is set up properly, but attempting to launch the game fails with 3862.780:0020:0024:err:steam:run_process Failed to execute L"link2ea://launchgame/1774580?platform=steam&theme=applejack", ret 31. in the Proton log.

steam-1774580.log from experimental-9.0-20250218

System:
  Host: msi-claw8-a2vm Kernel: 6.14.0-rc4-3-cachyos-rc-claw arch: x86_64 bits: 64 compiler: clang
    v: 19.1.7
  Console: pty pts/1 DM: SDDM Distro: CachyOS base: Arch Linux
CPU:
  Info: 8-core model: Intel Core Ultra 7 258V bits: 64 type: MCP arch: Lunar Lake rev: 1 cache:
    L1: 832 KiB L2: 14 MiB L3: 12 MiB
  Speed (MHz): avg: 2124 min/max: 400/4700:4800:3700 cores: 1: 2124 2: 2124 3: 2124 4: 2124
    5: 2124 6: 2124 7: 2124 8: 2124 bogomips: 52838
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Lunar Lake [Intel Arc Graphics 130V / 140V] vendor: Micro-Star MSI driver: xe
    v: kernel arch: Xe2 ports: active: eDP-1 empty: DP-1,DP-2 bus-ID: 00:02.0 chip-ID: 8086:64a0
  Display: server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6 compositor: Gamescope driver:
    gpu: xe tty: 202x64
  Monitor-1: eDP-1 model: PN8007QB1-2 res: 1920x1200 dpi: 284 diag: 203mm (8")
  API: EGL v: 1.5 platforms: device: 0 drv: iris device: 1 drv: swrast gbm: drv: iris
    surfaceless: drv: iris inactive: wayland,x11
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 25.1.0-devel note: console (EGL sourced)
    renderer: Mesa Intel Graphics (LNL), llvmpipe (LLVM 19.1.7 256 bits)
  API: Vulkan v: 1.4.303 surfaces: N/A device: 0 type: integrated-gpu driver: N/A
    device-ID: 8086:64a0 device: 1 type: cpu driver: N/A device-ID: 10005:0000
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
    gpu: gputop, intel_gpu_top, lsgpu, lact wl: wayland-info x11: xdpyinfo, xprop, xrandr

Can confirm it still occurs. Unable to play ANY EA-launcher games, in general. Anything that launches through EA's stupid DRM-launcher will fail. Confirmed when bypassing for Jedi: Fallen Order with the shipping EXE. Given how they keep patching out old Origin launcher fixes, and forcing their launcher, I'm uncertain we're likely to get any support on this issue from them. Pretty much can't even contact their support, given their shitty website, that literally never lets you connect to a help agent. Hopefully we get some fix with this, because gamescope doesn't work on this either :(

How can I launch this game now? I've tried so many proton versions. Including proton-ge, proton-catchyos, proton experimental, proton-hotfix and proton 9.0-4.

Game just won't start after "preparing game..."

How can I launch this game now? I've tried so many proton versions. Including proton-ge, proton-catchyos, proton experimental, proton-hotfix and proton 9.0-4.

Game just won't start after "preparing game..."

I didn't tried it again, but some time ago I fixed the game not running by manually installing ea play, as said in this comment:
https://github.com/ValveSoftware/Proton/issues/6729#issuecomment-2147848694

I didn't tried it again, but some time ago I fixed the game not running by manually installing ea play, as said in this comment: [#6729 (comment)](https://github.com/ValveSoftware/Proton/issues/6729#issuecomment-2147848694)

can you play it now?

I didn't tried it again, but some time ago I fixed the game not running by manually installing ea play, as said in this comment: [#6729 (comment)](https://github.com/ValveSoftware/Proton/issues/6729#issuecomment-2147848694)

can you play it now?

I can check, but downloading will take about 3 hours, so I will know then.

I can check, but downloading will take about 3 hours, so I will know then.

I managed to get it to work. I downloaded the EAapp from the EA site and installed it manually with protontricks. Then it asked me to repair or launch ea app. I said repair. After install was complete the ea app launched and asked me to login. I logged in and tried to start the game from there. Nothing would happen. But I closed everything and just started normally through steam, with proton experimental. The game launched after "preparing game..." tested it a few times and it works.

Does it work for you out of the box or do you have to manually install EA app again to play.

Replying to https://github.com/ValveSoftware/Proton/issues/6729#issuecomment-3094655210

Worked fine out of the box today, but I remember having to install EA Play manually some months ago, so it might be worth a try for others.

Replying to https://github.com/ValveSoftware/Proton/issues/6729#issuecomment-3094663661

what proton version are you using also?

Whatever is automatically selected, I have the checkbox to use specific version unchecked, but from the process list it seems it's proton experimental.

Whatever is automatically selected, I have use the checkbox to use specific version unchecked, but from the process list it seems it's proton experimental.

Ok. same as mine then. Thats my default. It worked with experimental again and installed the EA app again manually. I also tried GE-proton10-8 and it worked first time but when I tried more times after it wouldn't start. Changing back to experimental and it looks like it's working everytime I start again now.

Not sure if installing the EAapp manually again had anything to do with the fix but thanks for letting me know.

This game is a mess on every platform, but crashes on Linux are more frequent than on Windows. It crashes almost every time there is a map transition or when the game transitions from a cutscene to gameplay.

at the least it's a different issue to the bloody drm. I suppose now we can somewhat work on the game's stability.

This game is a mess on every platform, but crashes on Linux are more frequent than on Windows. It crashes almost every time there is a map transition or when the game transitions from a cutscene to gameplay.

Have you tried running it within Gamescope? And any differences with patched versions such as GE or cachyos forks? Not a plug, just curious as to your results if you do that, to work out whereabouts the display-chain it might be failing. Logs would be useful too, if you had PROTON_LOG=1 %command% in the launch options when playing to provide a log up to a crash.

@KawaiiDinosaur can you give more information about your setup? hardware, drivers, proton version you've tried, frequency of the crashes, graphics settings.

Also attach a proton log, you add PROTON_LOG=1 %command% to the game's launch parameter and play until the game crashes, and upload the resulting steam-1774580.log that will be in your home folder. Compress it if needed.

Sorry, I got frustrated with the game and uninstalled it. I totally forgot about extracting logs or trying gamescope. It's a 130gb download, it will take me a while to install again. Here are my hardware settings, if it helps:

OS: Arch Linux
KERNEL: 6.18.2-arch2-1
CPU: AMD Ryzen 7 5700X3D 8-Core
GPU: AMD Radeon RX 9070 XT (radeonsi, gfx1201, LLVM 21.1.6, DRM 3.64, 6.18.2-arch2-1)
GPU DRIVER: 4.6 Mesa 25.3.2-arch1.1
RAM: 16 GB

I get a pretty stable experience using the manual ea app download trick and running through GameScope, even on proton patched for Wayland support :] I only encountered any erroring when not using gamescope and having accidental frame resizes and only really saw the issue in titanfall 2. And the frame rate being absolutely atrocious outside of gamescope as usual of course!

Hi, does anyone else not have only their Xbox One/Series controller work in this game? I've tried Steam Input enabled and disabled, multiple proton versions (GE 10-27, Experimental, 9.0.4), wired and wireless, and each combination of these variables. A DS4 controller works without issue, just not the Xbox controller which works in every single other game I've ever tried, and on the same Proton version. I was playing Jedi Survivor with this Xbox controller just back in October, as my last achievement was from then. I don't know what's change except maybe Proton version. Nobara Linux 43. Thank you.

@KawaiiDinosaur your setup and mine are similar, I have a zen 4 cpu but my gpu is also rdna4 (9060xt), same kernel, and same mesa version and what I played of the game was fine. So there's a chance it's down to graphics settings. I didn't do anything manual like install EA separately or anything like that.

@1031Vulcan Tried with proton 10 and experimental, with steam client stable and beta, with the xbox series controller and 8bitdo ultimate controller and they worked fine.

This is my first comment but I've found some things out. For starters:

System Information

• GPU: NVIDIA RTX 3080 Ti
• CPU: Ryzen 9 5900X
• Video driver version: NVIDIA 580.105.08 via nvidia-open-dkms
• Kernel version: linux-cachyos 6.18.3-2
• Proton version: proton-cachyos-slr 1:10.0.20251222-2

TL;DR installing Jedi Survivor on an NVMe SSD borks it

I use CachyOS installed on a WD SN850X NVMe SSD. I previously used a Samsung 980 Pro until it went bad a week or so ago. This is important: I initially installed Jedi Survivor on a 2TB 7200 RPM HDD from Seagate and played for hours with no real issues except texture pop-in, so I moved the game to my root drive, the Samsung SSD, to try and fix the pop-in, but after moving it to the SSD the game wouldn't launch past the EA launcher. That drive ended up dying recently, so I figured it was just a bad drive and tried it again with the SN850X SSD; same story. It wouldn't launch past the EA launcher and Steam's default Proton is now stuck to Proton Experimental no matter what I set it to in the settings. Ironically, forcing Proton Experimental on Jedi Survivor allowed me to play the game, but HDR didn't work, it stuttered bad, and texture pop-in was worse than it was on the HDD. I also found that Proton GE 10-4 gets HDR working, but I can't use my controller (PS5 DualSense) so I can't speak on gameplay. I have tried almost all driver versions from 575 up to the latest 590 (which has a lot of issues atm); Proton 9, 10, Experimental, and GE 9-27, 10-4, 10-15, 10-17, 10-27, and 10-28; I reinstalled the game three times; reinstalled my system once; nothing worked consistently until I moved the game back to my Seagate HDD and set PROTON_LOG=1. I don't know why, but since I did both, I can now use Proton CachyOS which means my controller and HDR both work. If I break those by either moving it to my SSD or disabling logging, it borks the game. I've also found that disabling GPU Hardware Scheduling (WINE_DISABLE_HARDWARE_SCHEDULING=1) makes the game more stable. Come to think of it, I don't think my game has crashed even once since setting that envvar.

I unfortunately don't have a SATA SSD to test this out with.

ETA: I forgot to say that I've moved the game back and forth between my SSD an HDD three times and I can reproduce this every time

Edit 1/14/2026: the latest Proton CachyOS (1:10.0.20260101-1) lets me at least play with the game on my SSD, but it won't work through Lutris. I have to launch the game from Steam directly or it gets stuck trying to connect to EA.

I have a samsung 990 pro, it's where my root and the game are installed and the game works correctly with proton experimental. Your message confuses me

it wouldn't launch past the EA launcher and Steam's default Proton is now stuck to Proton Experimental no matter what I set it to in the settings.

From this, it sounds like the game doesn't work on experimental, but the next line says the opposite.
Bear in mind that if the upstream proton is working, but third party versions aren't, those issues should be reported to the ones maintaining those forks.

I apologize for any confusion. Let me clarify: if the game is installed on my NVMe SSD, the only Proton versions that work are Proton CachyOS 1:10.0.20260101-1, Proton GE 10-4, and Proton Experimental, although HDR doesn't work for me on Experimental. If I install the game on my HDD and set PROTON_LOG=1, I can use any Proton version from 9 up to the latest Experimental and it works (almost) every time, but again, HDR doesn't work for me on Experimental and, like I said in my last comment, it's got some really bad stutters that aren't present in third-party versions. So, to summarize, my issue is that third party versions are working while this one is not, at least not completely.

As for the comment you quoted, what I mean is that after launching Jedi Survivor for the first time, something in Steam breaks for me and the default compatibility tool in Steam Settings gets stuck on Proton Experimental; even if I set it to something else, like Proton CachyOS, games launch with Proton Experimental by default (checked with PROTON_LOG=1). The only way around this I've found is to go into the Properties for each individual game and set Force the use of a specific Steam Play compatibility tool to the Proton I want. I understand that this sounds far-fetched, but it happened to me twice in a row on separate installations, so I figured I'd mention it.

@dablenparty HDR is expected to not work on upstream proton currently, it requires wayland support (OR using gamescope). Third party versions have extra patches on top to enable wayland support, so you get HDR as a result.

The only way around this I've found is to go into the Properties for each individual game and set Force the use of a specific Steam Play compatibility tool to the Proton I want.

Oh, I get you now. This is normal for this title, the game is set to use proton experimental by default valve side, you can see this by clicking "show game details" button in the game's library page while "Force the use of a specific Steam Play compatibility tool" is unchecked. For games that don't have a default, which is most of them, they'll use whatever you have set in settings > compatibility.

I recently installed this, and I'm seeing regular stuttering using Proton 10.0-4 and Experimental. Basically while moving around I'll get a frame time jump to ~30-35ms (with a 60fps lock and V-Sync on). I've tried dropping to the lowest graphics settings, using gamemoderun, disabling V-Sync and disabling MangoHUD, but the problem doesn't go away. There is still some traversal stutter on Windows using the same hardware and graphics settings, but it's not nearly as regular.

Setup for reference: AMD 5700X3D, AMD 7800XT, 32GB RAM, Ubuntu 24.04.3.

@seadowg the game itself has stutter issues, this was showcased by some reviewers at launch and even after the last update many users complain about unstable frametimes. Have you compared against windows to see if there are significant differences?

@simifor yup! See the last sentence of my comment:

There is still some traversal stutter on Windows using the same hardware and graphics settings, but it's not nearly as regular.

@seadowg oh sorry, I glossed over that, can you give more information about your setup? where is the game installed? ssd or hdd? what format is it? have you noticed anything jumping on mangohud when the spikes happen?

where is the game installed? ssd or hdd?

SSD.

what format is it?

ext4.

have you noticed anything jumping on mangohud when the spikes happen?

Yeah the frame time graph has a quick spike. The ~30-35ms frame time I'm referencing is from looking at the max in MangoHUD.

@seadowg but what I meant was what else is accompanied by the spike. Abrupt changes to cpu or gpu usage? or I/O activity?

@seadowg but what I meant was what else is accompanied by the spike. Abrupt changes to cpu or gpu usage? or I/O activity?

Ah ok. Nothing obvious, but I only have a very lightweight MangoHUD config (in terms of what's displayed). Do you have a suggested config I could use to get you more info?

Abrupt changes to cpu or gpu usage? or I/O activity?

@simifor I had another look with core_load configured as well as GPU and CPU usage and couldn't see anything suspicious. There were frame time spikes in the section I played around with, but didn't see anything max out. Here's a log with spikes.

Just to compare performance as well: in the small section I used for grabbing those logs, on Windows my avg/1% lows was 60/60 an on Ubuntu it was 60/38.

Hello,
The game still won't launch. Do you have any advice?

A consistent issue I have with Jedi: Survivor is RAM leaks. My computer has 32GB and after 30-60 minutes it'll freeze and crash with a "program terminated due to excess RAM usage" message or something to that affect.

Several reviewers using Crossover to play the game on Mac report the same problem.

However, my brother and my friend who both play on Windows with only 16GB of RAM have no problems.