Skip to content
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

Open
palsone opened this issue Mar 29, 2024 · 17 comments
Open

EA app launch issue #5390

palsone opened this issue Mar 29, 2024 · 17 comments

Comments

@palsone
Copy link

palsone commented Mar 29, 2024

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

@strycore
Copy link
Member

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.
While I did manage to launch EA app in game mode, I didn't manage to launch any game. When I returned to desktop mode, I was still able to launch EA app and I could launch games as well.

@strycore
Copy link
Member

If I enable Wine debug messages, I can see the launcher is stuck in a loop and keeps spamming messages like

026c:fixme:netprofm:list_manager_GetConnectivity 0000000002E00420, 00000000054EFA9C
04d8:fixme:netprofm:list_manager_GetConnectivity 0000000002061260, 000000000438FA9C
026c:fixme:netprofm:list_manager_GetConnectivity 0000000002E00420, 00000000054EFA9C
0058:fixme:nsi:ipv6_forward_enumerate_all not implemented
0058:fixme:nsi:ipv6_forward_enumerate_all not implemented
0058:fixme:nsi:ipv6_forward_enumerate_all not implemented
0058:fixme:nsi:ipv6_forward_enumerate_all not implemented
04d8:fixme:netprofm:list_manager_GetConnectivity 0000000002061260, 000000000438FA9C
026c:fixme:netprofm:list_manager_GetConnectivity 0000000002E00420, 00000000054EFA9C
0058:fixme:nsi:ipv6_forward_enumerate_all not implemented
0058:fixme:nsi:ipv6_forward_enumerate_all not implemented
0058:fixme:nsi:ipv6_forward_enumerate_all not implemented
0058:fixme:nsi:ipv6_forward_enumerate_all not implemented
04d8:fixme:netprofm:list_manager_GetConnectivity 0000000002061260, 000000000438FA9C
026c:fixme:netprofm:list_manager_GetConnectivity 0000000002E00420, 00000000054EFA9C
04d8:fixme:netprofm:list_manager_GetConnectivity 0000000002061260, 000000000438FA9C
026c:fixme:netprofm:list_manager_GetConnectivity 0000000002E00420, 00000000054EFA9C

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.

@strycore
Copy link
Member

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.

@1sad
Copy link

1sad commented Apr 4, 2024

coming from the just linked issue to reply.
i think its this
Screenshot_20240404_031109
and in lutris settings it said (system) so im assuming it was installed differently. it was pre installed on the distro.

since it didnt work on 3 different distros till i switched it to nobaras wine, someone suggested it might be due to my cpu instructions missing or how wine was complied or something, they suggested i report this so im here. if i can provide any more info. im going to try test it some more to see if non nobara staged wine will work too.

@strycore
Copy link
Member

strycore commented Apr 4, 2024

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.
On Nobara, I did succeed to install EA App with Wine Staging 9.5 like you did but this is not a supported use case for us and games should launch with Wine-GE since it's still our default build until we have more complete Proton integration.

@1sad
Copy link

1sad commented Apr 4, 2024

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
on Mint i tried installing wine 7.34 and 7.24 with protonup-qt, cause someone linked issue from 2023 where that helped, but that didnt help in my case. though it made an eaapp progress bar pop up like it was installing, but it still failed.
on the default more updated wine there was only a black square where the eaapp installer was supposed to pop up during install

also it didnt work on bottles either. but when i switched to the same nobara wine it worked there too.

@strycore
Copy link
Member

strycore commented Apr 4, 2024

it didnt work on mint either

I would rather not add Mint into this equation, technically we don't officially support Mint.

i tried installing wine 7.34 and 7.24 with protonup-qt

You shouldn't use Wine 7 to run games in Lutris.

though it made an eaapp progress bar pop up like it was installing, but it still failed

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

@1sad
Copy link

1sad commented Apr 4, 2024

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

@strycore
Copy link
Member

strycore commented Apr 4, 2024

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.

@strycore
Copy link
Member

strycore commented Apr 4, 2024

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.

@madscientist16
Copy link

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

@1sad
Copy link

1sad commented Apr 6, 2024

not sure if useful but didnt work on endevouros with normal lutris and wine staging 9.6 from chaoticaur (couldnt find 9.5 anywhere)
and default GE one that comes with lutris complains about freetype fonts even though its installed?..
image

on flatpak beta with GE it installs without error (though no login pops up), lets me login after install if i press the head icon, but still says missing and doesnt launch or load any games, same thing on system 9.0
screen
dont know how to install staging into flatpak beta

@strycore
Copy link
Member

strycore commented Apr 7, 2024

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.

@strycore
Copy link
Member

strycore commented Apr 7, 2024

still says missing and doesnt launch or load any games

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.

@1sad
Copy link

1sad commented Apr 7, 2024

no eaapp files in the folder it creates in home/games
no game files cause game not installed, but when it works it detects games from the account

@strycore
Copy link
Member

strycore commented Apr 7, 2024

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.

@1sad
Copy link

1sad commented Apr 8, 2024

usually it does, but not in that case

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants