Closed ZyanKLee closed 3 years ago
just tested it with PRESSURE_VESSEL_SHARE_HOME=1 steam
as well - the game still crashes
disabling the Linux Steam Runtime reverts the game to be playable
Segmentation fault (core dumped)
Can you find out which process segfaults: the game itself, or some helper process like pressure-vessel-wrap? (The last few lines of dmesg
after the crash should give you a clue.)
It is starting fine for me on a Manjaro system. However I noticed that while the 7DaysToDie.x86_64
process is running in a container setup, the bwrap
binary has exited.
The command line executed by the steam client is "/home/timo/.local/share/Steam/SteamApps/common/7 Days To Die/7DaysToDie.sh" -from-steam
Which executes a 7dLauncher.x86_64
launcher that will start the actual game .. I assume bwrap
is exiting when that terminates.
(the steam client does not do any restarting via IPC like we had initially suspected)
bwrap
exiting is not necessarily such a bad thing: the actual container will stay alive as long as it's referenced by at least one process. bwrap
exits after its direct child process exits, even if there is an indirect child process that is running in the background and has been reparented to the nearest subreaper or to init (similar to the standard daemonize/double-fork trick), but that shouldn't result in the mount namespace being cleaned up.
To tell whether a process is in the container, look at /proc/PID/root
where PID
is its process ID. It's a "magic symlink": if you use ls -l
it will appear to be a symlink to /
, but if you dereference it (for example ls /proc/PID/root/
or cat /proc/PID/root/usr/lib/os-release
) you'll see whatever is in that process's root filesystem. For games in a Steam Runtime container, os-release
says ID=steamrt
.
Having said that, some unrelated changes in progress in pressure-vessel (related to locking) are likely to result in there being a subreaper process inside the container, which will mean that background processes become its children and the process tree stops being misleading.
Segmentation fault (core dumped)
Can you find out which process segfaults: the game itself, or some helper process like pressure-vessel-wrap? (The last few lines of
dmesg
after the crash should give you a clue.)
sadly nothing appears in dmesg output
This games works for me with SLR enabled.
@ZyanKLee Can you please try it again? A lot has changed in the past couple of years since you first reported this issue. And I also see that in the initial log that you posted you had CClientJobGatherRuntimeInformation: container read output failed
, meaning that the Steam Linux Runtime was not working correctly on your system.
Closing pending feedback.
PRESSURE_VESSEL_SHARE_HOME=0 steam