System info
OS: Pop!_OS 24.04 LTS (Linux)
Desktop: GNOME on X11
GPU: NVIDIA RTX 4060 (driver 580.126.18)
Steam: latest
Proton: GE-Proton10-34 / Proton Hotfix (both tested)
BF4 install location: NTFS partition (/media/humberto/Windows-C/SteamLibrary)
Problem description
Battlefield 4 launches via Steam/Proton but the EA Desktop App crashes approximately 60 seconds after launch with the message "La aplicación falló de forma inesperada" (The application failed unexpectedly). When the EA App crashes, it terminates the BF4 process as well, returning the user to the desktop.

The game itself loads and runs correctly (menu visible, FPS normal). The crash originates in the EA App, not in BF4.

Error log (from PROTON_LOG=1)

ERROR: network_change_notifier_win.cc(224) WSALookupServiceBegin failed with: 0
ERROR: PersistenceService > The persistence service is not initialized yet
ERROR: PersistenceContainerUpdateJob > Failed to update container because the Persistence Service is not initialized
ERROR: DirtySDKConnectDetectionJob > Timeout, DirtySDK is not at online, offline or trying to connect at the time of job timeout.
The DirtySDK network timeout (60 seconds) kills the EA App, which in turn kills BF4.

Steps to reproduce
Install BF4 via Steam on Linux with Proton
Launch BF4 — EA App opens, user logs in, BF4 starts loading
After ~60 seconds the EA App shows crash dialog and closes
BF4 closes with it
What was tried (none resolved the issue)
Proton Experimental, GE-Proton10-34, Proton Hotfix — all tested
Deleted and recreated the Proton prefix
Installed vcrun2022, vcrun2019, dotnet48 via protontricks
Set Windows version to win10 via protontricks
Various WINEDLLOVERRIDES for EADesktop.exe
Cleared EA App cache and stale backgroundservice.ini PID
Set user.offlinemode=1 in EA App user config
Blocked EA servers via Wine hosts file
Wrapper script to kill EA App after BF4 launch (workaround, not a fix)
Expected behavior
EA App should fall back to offline mode gracefully when the DirtySDK network check fails, without crashing and without terminating the game process.

Notes
This worked previously on the same hardware with a prior Pop!_OS installation
GTA V Enhanced (also requires a third-party launcher — Rockstar Games) works correctly under the same Proton setup
The issue appears specific to the EA App's DirtySDK network initialization under Wine/Proton