Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

STEAM_COMPAT_LIBRARY_PATHS documentation doesn't match implementation

クローズ
  • 何か問題がありますか？
#856 コメント 7 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
52/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
c, linux, python
領域
documentation, operating-systems

調査の方向性

Start with docs/steam-compat-tool-interface.md at the cited lines, then compare the path handling in bin/launch-options.py lines 1660-1664 with steam_helper/steam.c around line 796. Confirm the expected STEAM_COMPAT_LIBRARY_PATHS convention for both SLR and Proton, then update the documentation and relevant implementation so the convention is consistent and libraryfolders.vdf remains usable.

索引モデルが issue の本文から書いたものです。

説明

Your system information
  • Steam Runtime Version: 4.0
  • Distribution (e.g. Ubuntu 18.04): CachyOS
  • Have you checked for system updates?: Yes
  • What compatibility tool are you using?: Steam Linux Runtime / Proton 5.13+
  • What versions are listed in steamapps/common/SteamLinuxRuntime/VERSIONS.txt?
#Name   Version         Runtime Runtime_Version Comment
depot   1.0.20260618.246542                     # Overall version number
LD_LIBRARY_PATH 1.0.20260618.246542     scout   1.0.20260618.246542     # steam-runtime/
scripts 0.20260618.0                    # from steam-runtime-tools
  • What versions are listed in steamapps/common/SteamLinuxRuntime_soldier/VERSIONS.txt?
#Name   Version         Runtime Runtime_Version Comment
depot   2.0.20260805.254767                     # Overall version number
pressure-vessel 0.20260805.0
pressure-vessel-arm64   0.20260805.0
scripts 0.20260805.0                    # from steam-runtime-tools
soldier 2.0.20260805.254767     soldier 2.0.20260805.254767     # soldier_platform_2.0.20260805.254767/
  • What versions are listed in steamapps/common/SteamLinuxRuntime_sniper/VERSIONS.txt?
#Name   Version         Runtime Runtime_Version Comment
depot   3.0.20260805.254768                     # Overall version number
pressure-vessel 0.20260805.0
pressure-vessel-arm64   0.20260805.0
scripts 0.20260805.0                    # from steam-runtime-tools
sniper  3.0.20260805.254768     sniper  3.0.20260805.254768     # sniper_platform_3.0.20260805.254768/
  • What versions are listed in steamapps/common/SteamLinuxRuntime_4/VERSIONS.txt?
#Name   Version         Runtime Runtime_Version Comment
depot   4.0.20260805.254769                     # Overall version number
pressure-vessel 0.20260805.0
pressure-vessel-arm64   0.20260805.0
scripts 0.20260805.0                    # from steam-runtime-tools
steamrt4        4.0.20260805.254769     steamrt4        4.0.20260805.254769     # steamrt4_platform_4.0.20260805.254769/
Please describe your issue in as much detail as possible:

There seems to be a mismatch between what exact paths are expected relative to extra Steam Libraries for the STEAM_COMPAT_LIBRARY_PATHS environment variable:

  • SteamRT expects these paths to be set to <path>/SteamLibrary, without the steamapps child path. Here it joins the path with the steamapps folder when building SLR/compat tool search paths.

  • Proton expects these paths to be set to <path>/SteamLibrary/steamapps. Here it strips the last directory when building the main libraryfolders.vdf.

So, if you set STEAM_COMPAT_LIBRARY_PATHS and don't include the steamapps part, SteamRT will have the appropriate search paths, but Proton will generate a broken libraryfolders.vdf. In practice, this would break launcher programs made for Windows that use this file to locate where a Steam game is located. On the other hand, if you include steamapps, SteamRT will have incorrect search paths (though I couldn't get this to break anything in my testing).

The current behavior of Steam when running a program as a non-Steam app and selecting the SLR or Proton as a compat tool, at least on my system, aligns with the Proton behavior of including steamapps in the paths, which is why I'm reporting this as an SLR bug instead of a Proton bug.

This came up as a bug in the Linux launcher for me3, a FromSoftware mod loader. We followed docs/steam-compat-tool-interface.md, which seemed to indicate that we had to populate this env var with <path>/SteamLibrary, and this ended up breaking a mod that relied on parsing libraryfolders.vdf.

What I think should be done about this

docs/steam-compat-tool-interface.md should be updated to precisely state which of these two paths is expected, and the relevant Proton or SteamRT code mentioned above should be patched to conform. In my opinion, since Steam follows what Proton expects when launching non-Steam games, it's the one that should be considered "correct".

Steps for reproducing this issue:

N/A

主要言語
Shell
スター
1.5k
フォーク
98
30日以内にマージされた PR はありません

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

ValveSoftware/steam-runtime のほかの issue

ValveSoftware/steam-runtime の issue をすべて見る

似ている issue

Shell/Bash の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。