-
-
Notifications
You must be signed in to change notification settings - Fork 677
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EA app launch issue #5390
Comments
Right now I'm having a lot of issues with EA App. It doesn't run at all on any Fedora based OS. I did managed to get it running on Ubuntu and Steam Deck. |
If I enable Wine debug messages, I can see the launcher is stuck in a loop and keeps spamming messages like
ipv6_forward_enumerate_all and list_manager_GetConnectivity seem to indicate something related to internet connectivity. I tried disabling IPv6 or connecting via a VPN but it didn't change anything. |
After more troubleshooting, I think the network stuff is a false lead and I'd be more inclined to think this is a windowing issue. I've managed to start EA App when disabling DXVK / VKD3D but still nothing reliable. |
On my side, I've had the most issues with Nobara (and Fedora). On SteamOS and Ubuntu, I was able to install EA App without issue. |
it didnt work on mint either, but im going to try installing arch now and see if i can make it work there too. i think i forgot to mention that i tried on Mint 21.3, CachyOS 240401, and nobara 39 is where it worked with their system installed wine staging 9.5 also it didnt work on bottles either. but when i switched to the same nobara wine it worked there too. |
I would rather not add Mint into this equation, technically we don't officially support Mint.
You shouldn't use Wine 7 to run games in Lutris.
Yes, that's what I'm getting as well. Please note that the goal of this issue is to get EA App working with Wine-GE. Every other Wine build is unsupported and should not be used in Lutris (expect for troubleshooting etc). |
just giving you all info i have. only just getting into linux gaming and spent all day trying to figure out why it wasnt working. and seeing that it didnt work on 3 distros of different linux versions im not sure where to go from here. if you need me to provide any specific info, or what to try to see if it works, just tell me how |
Right now, I'm thinking that the way forward would be to try a more recent build of Wine-GE based on Wine 9.5, like Wine Staging. I have spent a lot of time trying to figure this out as well and it seems we're at an impasse. |
I managed to get EA App running on Nobara with Wine GE using the Flatpak version of Lutris (from flathub-beta). So whatever is causing issues with EA App is not affecting the Flatpak version. |
EA App is working for me using Wine GE with both native and Lutris beta from Flathub. It failed to install when I used the stable Flatpak Lutris, but after I installed it using the beta version it works on the stable just fine. I haven't tested to see if games launch or not. OS: Arch Linux |
Update on the EA App mess: after getting it to run in Lutris Flatpak, I'm able to run the fresh install of EA App with native Lutris in Nobara using Wine-GE. I was able to play Crysis 3 Remastered, Red Alert 2 and Anthem (with HDR enabled). The older EA App installed in another prefix will simply not launch no matter what and at this point it's important to acknowledge some things. Switching from one Wine version to another may cause permanent damage to your Wine prefix. For example, when you switch from Wine-GE to Proton to Wine Staging back to Wine-GE, it is perfectly possible that the changes made by Proton would prevent things from running with Wine-GE. It used to work in Wine-GE and now it will not and won't until a new prefix is created. It is possible that an OS glitch prevented EA App from installing on Fedora based systems. I will have to confirm this on my Fedora VM. It is possible this glitch has no relation with Fedora at all I have experienced issues with Fedora but not on Flatpak. For others it seems to be the opposite. We still haven't figured out what is the cause of the issue here. |
Verify that the game files are actually where Lutris expects them to be. If Lutris completed the EA App without an error this is because there is a directive in the installer script that ignores errors. |
no eaapp files in the folder it creates in home/games |
So the install didn't complete. You should at least see a message at the end of the install telling you the executable wasn't located. |
usually it does, but not in that case |
I have this strange issue with EA app using Steam Deck.
Installation and login process seems to be fine but as soon as I go into gaming mode, EA app would never start again. It just constantly crushes on startup no matter what I do. It even stops working on desktop so I assume it's not a Steam problem. Logs gives me this:
Started initial process 155 from gamemoderun /home/deck/.var/app/net.lutris.Lutris/data/lutris/runners/wine/wine-ge-8-26-x86_64/bin/wine /home/deck/Games/ea-app/drive_c/Program Files/Electronic Arts/EA Desktop/EA Desktop/EALauncher.exe
Start monitoring process.
gamemodeauto:
Monitored process exited.
Initial process has exited (return code: 256)
All processes have quit
Exit with return code 256
The text was updated successfully, but these errors were encountered: