1. 16 Jun, 2022 4 commits
  2. 15 Jun, 2022 2 commits
    • Simon McVittie's avatar
      Add app-ID-based triggering for steam-runtime-launcher-service · ee4b6c47
      Simon McVittie authored
      The idea here is that Steam would set
      STEAM_COMPAT_LAUNCHER_SERVICE=1628350 to get a way to inject commands
      at the sniper container runtime layer, and so on.
      Signed-off-by: Simon McVittie's avatarSimon McVittie <smcv@collabora.com>
    • Simon McVittie's avatar
      Add basic steam-runtime-launcher-service integration · 8453216b
      Simon McVittie authored
      If run with STEAM_COMPAT_LAUNCHER_SERVICE=container-runtime, we'll
      inject commands at the container layer and they'll run in a "pure"
      soldier/sniper environment. This is appropriate for native soldier/sniper
      games that run with no further compatibility layer, as in
      If run with STEAM_COMPAT_LAUNCHER_SERVICE=scout-in-container, we'll
      inject commands inside the layered scout-on-soldier runtime (or
      potentially scout-on-sniper, if we pivot to that at some point) and
      they'll run in a scout-compatible environment.
      Signed-off-by: Simon McVittie's avatarSimon McVittie <smcv@collabora.com>
  3. 13 Jun, 2022 1 commit
  4. 09 Jun, 2022 1 commit
  5. 08 Jun, 2022 5 commits
  6. 27 May, 2022 2 commits
  7. 11 Mar, 2022 2 commits
  8. 10 Mar, 2022 1 commit
    • Simon McVittie's avatar
      _v2-entry-point: Make sure ./var is not a symlink · a587ac87
      Simon McVittie authored
      Some users might be tempted to redirect ./var to another filesystem,
      but this will make the runtime a lot slower, more space-consuming and
      less reliable, because we rely on being able to make hard links
      between the distributed files and the temporary container root.
      The correct way to relocate the Steam Linux Runtime depot is to set up
      a Steam library on a suitable filesystem (which for best results should
      be a fully-featured Unix filesystem like ext4, btrfs or xfs, although
      NTFS can be made to work with some difficulty), and then use Steam's
      "Properties -> Local Files -> Move install folder..." to move the
      Steam Linux Runtime into it.
      Helps: https://github.com/ValveSoftware/steam-runtime/issues/495
      Signed-off-by: Simon McVittie's avatarSimon McVittie <smcv@collabora.com>
  9. 22 Feb, 2022 1 commit
  10. 14 Feb, 2022 1 commit
  11. 11 Feb, 2022 1 commit
    • Simon McVittie's avatar
      scout-on-soldier: Unpack our own Steam Runtime if necessary · 65ae90fa
      Simon McVittie authored
      This avoids game crashes in some of the unsupported configurations where
      a distribution or end user has either disabled the Steam Runtime with
      STEAM_RUNTIME=0, or switched to a modified, unofficial or otherwise
      out-of-band Steam Runtime with STEAM_RUNTIME=/some/path.
      Normally, when developers and tinkerers are experimenting with new
      Steam Runtime versions, we can assume that they have previously run
      Steam with the supported runtime at least once. In that scenario,
      ~/.steam/root/ubuntu12_32/steam-runtime will be a valid scout runtime:
      it might not be the one the user intended, and it might be out of date,
      but it will probably work.
      However, if someone has been *consistently* setting STEAM_RUNTIME ever
      since the first time they ran Steam, then it will never have had the
      opportunity to unpack the supported runtime, and
      ~/.steam/root/ubuntu12_32/steam-runtime will still be the heavily
      cut-down runtime from the bootstrapper, which is insufficient for
      launching games because it does not implement the whole Steam Runtime ABI
      (in particular, Dota 2 fails to launch because libpng12.so.12 is
      As before, developers and tinkerers can bypass all of this by setting
      setting this variable is unsupported and users who have overridden it
      are responsible for the consequences (do not report bugs). We cannot
      reuse the same variable for this purpose, because of the dual role of
      STEAM_RUNTIME: it's a way for developers to switch to a different
      scout runtime, but it's also a way for libraries inside the runtime
      to detect the location of the runtime environment, which needs to be
      disabled while we are setting up the container runtime.
      Resolves: https://github.com/ValveSoftware/Dota-2/issues/2018
      Signed-off-by: Simon McVittie's avatarSimon McVittie <smcv@collabora.com>
  12. 29 Oct, 2021 1 commit
  13. 28 Oct, 2021 1 commit
    • Simon McVittie's avatar
      scripts: Ignore errors when showing diagnostic messages · afa2a3de
      Simon McVittie authored
      If users of an X11 environment restart it inside a terminal emulator, and
      then close the terminal emulator (which seems to be a somewhat popular
      meme on various forums), we can end up with stdout/stderr pointing to a
      pseudo-terminal that is no longer associated with a terminal emulator.
      All writes to such a terminal fail, and when we're running under
      `set -e`, that will terminate the script. Worse, we can't even diagnose
      what has happened, because any error messages we might have shown are
      also going into the void.
      Mitigate this by ignoring `set -e` when logging diagnostic messages,
      analogous to the behaviour of `g_warning()` and similar C API calls.
      (After all, what would we do about it - log a diagnostic message?)
      Related to <https://github.com/ValveSoftware/steam-for-linux/issues/8069
      Signed-off-by: Simon McVittie's avatarSimon McVittie <smcv@collabora.com>
  14. 16 Sep, 2021 4 commits
  15. 10 Sep, 2021 2 commits
  16. 09 Sep, 2021 2 commits
  17. 17 Aug, 2021 7 commits
  18. 06 Aug, 2021 1 commit
  19. 05 Aug, 2021 1 commit