Skip to content

Some Pressure Vessel wrap options from "Launch Options" don't work

Steps to reproduce

  • Set a game launch options as:
PRESSURE_VESSEL_SHELL=instead PRESSURE_VESSEL_SHARE_HOME=0 %command%
  • Set the compatibility layer to Proton 5.13
  • Launch the game

Expected behaviour

In the xterm ls -l ~/ should not contain the user's files from its real home directory.

Actual behaviour

The user's home directory gets mounted in the container anyway.

Additional info

If Steam is launched as PRESSURE_VESSEL_SHARE_HOME=0 steam the home isolation option works as expected.

When we launch a game _v2-entry-point gets called for the preparation steps and its environment doesn't contain the custom "Launch Options" from the game.

Only in a second moment _v2_entry_point is called again, this time to run the actual game executable, and with the "Launch Options" environment variables from the game. But at this point the container was already in place, so having PRESSURE_VESSEL_SHARE_HOME=0 here doesn't have any effect.