Page MenuHomeFeedback Tracker

Linux Client Port startup crash
Closed, ResolvedPublic

Description

The initial introduction screen shows but then immediately crashes. {F26904} {F26905}

Details

Legacy ID
499769471
Severity
None
Resolution
Open
Reproducibility
Always
Category
Game Startup
Additional Information
  1. I have built and installed SDL2 32 bit by adding "media-libs/libsdl2 abi_x86_32" to /etc/portage/package.use which apparently resolved Bug #25396 "Crash on startup - Linux port"
  1. Using "--eon_force_display=0" to avoid the game or NVIDIA driver from using the second connected HDMI monitor/display, as reported within the game's logging.
  1. I'm still getting a crash, with no obvious indicators per the game's logging. The game's log and Steam's Wine logging is attached, and likely a developer will be able to discern milder errors within the log for which are critical.

Event Timeline

rogerx edited Additional Information. (Show Details)Sep 1 2015, 9:39 PM
rogerx set Category to Game Startup.
rogerx set Reproducibility to Always.
rogerx set Severity to None.
rogerx set Resolution to Open.
rogerx set Legacy ID to 499769471.May 8 2016, 12:37 PM
Bohemia added a subscriber: rogerx.Sep 1 2015, 9:39 PM

Bingo. I have the game successfully executing using the following method:

Change to the root application/game folder, replacing USER with your login name.
$ cd /home/USER/.local/share/Steam/SteamApps/common/Arma\ 3

Manually execute arma3 binary
$ ./arma3 --eon_force_display=0 -world=empty -skipIntro -window

This "inability to start the game using the Steam application" seems to be an upstream Steam or game specific problem. What's likely happening when executing the game via Steam (using what's provided within the ps output), I get the following stdout error "/home/roger/.local/share/Steam/SteamApps/common/Arma 3/arma3: line 3: ./saferun.sh: No such file or directory" It maybe, saferun.sh (or arma3.i386) is not being found as the Steam client or initial arma3 sh script is being started within another folder. This error is likely being silenced from both the game and Steam logs.

In my opinion, executing everything via the command line shell is by far the best option, unless you're executing an extremely well tested and stable application!

QA_Sec added a subscriber: QA_Sec.May 8 2016, 12:37 PM

Hi, Arma3 Mac/Linux port is supported on Ubuntu and Mint distros. Game is also playable on Debian but it didnt go through QA phase. Your distro (Gentoo) is not listed and is not considered as a similar distribution.

Sorry for any incoveniences in this manner.

It is possible to run Steam via command line shell. You should get normal Steam GUI and play ArmA normally from the Library GUI.

The game needs Steam running. We need to have our content protected by steam ID dependencies. If you will find a way, how to run both together via command line shell, please share your knowledge on our forum https://forums.bistudio.com/forum/196-arma-3-ports/

Thanks for beneficial contribution.

rogerx added a comment.Sep 2 2015, 4:50 PM

lpjtvalka: Hi lpjtvalka. I'm guessing you only translated the description and did not have time to further translate my follow-up descriptions. My follow-up comment stated I was able to run the game directly. I also described the possible cause of the (shell) bug. (Could also be caused by uniquely defined PATH variables by Ubuntu, but overall likely an easily fixed shell bug.)

However, had I not solved it or knew of a workaround, your advice would have helped greatly and the advice would have been timely. ;-)

dedmen closed this task as Resolved.May 18 2020, 11:21 AM