Dennis HilkLinux diagnosticsDE

Linux Gaming Repair Center

Steam Flatpak cannot see the game library

Trace sandbox filesystem visibility without globally disabling isolation.

Editorial source review: Open the diagnostic assistants
On this page
  1. Identify the failing layer
  2. Collect discriminating evidence
  3. Compare safely and record limitations
  4. Gather evidence
  5. A controlled test
  6. Related diagnostics
  7. Sources & limitations

Identify the failing layer

A Steam Flatpak application sees a different filesystem namespace from an unsandboxed Steam installation. An externally mounted Steam library can be present and writable in the host shell yet invisible within Flatpak. Distinguish a portal-mediated file chooser, an explicit filesystem grant and a mount that is not active when Steam starts. Do not infer missing game files merely because the Flatpak process cannot reach the host path.

Collect discriminating evidence

Inspect the exact Flatpak app identity, active overrides and library path; do not paste a blanket access grant from an unrelated distribution. Mounts under /run/media and custom directories can have different behavior. Even after permission is corrected, a second problem may remain in the library's ownership or execution policy. Steam's own download errors and Proton prefix errors need their own evidence rather than being attributed automatically to Flatpak.

Compare safely and record limitations

For a controlled comparison, inspect visibility from the host and inside the Flatpak environment before changing permissions. If a narrow path-specific override is needed, document precisely which library is shared, and test one game. Avoid filesystem=host and disabling the sandbox as default advice; those greatly expand access and can hide a separate mount problem. Revert any trial override before deciding whether the permission was causal.

Gather evidence before changing the system

Run one command at a time in the relevant host or game environment. Read its requirements and interpretation first. The website displays commands and never runs them.

Read-only observation

flatpak list --app

Requirements: Run in the relevant host/session; compare with the actual game environment and redact private paths before sharing.

Identify the actual Steam Flatpak app ID; this is not a permissions test.

Read-only observation

flatpak override --user --show com.valvesoftware.Steam

Requirements: Run in the relevant host/session; compare with the actual game environment and redact private paths before sharing.

Read user-level overrides; system-level permissions may differ.

A controlled test with a way back

Compare the same library path in the host and the Flatpak file chooser, then try one narrowly scoped permission via normal Flatpak settings.

Rollback: Remove only the specific test override and restore the original Steam library setting.

What this test cannot establish: An absent override does not prove the sandbox lacks portal-based access.

Sources and scope

This editorial review uses primary project and distribution references. It does not establish that a fix has been reproduced on your hardware. Installed versions, the game runtime and the selected graphics API can change the result.