Autoconnect mount-observe for Steam

[ashtonn]

---

• name: steam
• description: Steam snap
• snapcraft: steam-snap/snap/snapcraft.yaml at main · canonical/steam-snap · GitHub
• upstream: PRIVATE
• upstream-relation: Snap is published by Canonical, not directly supported by Valve
• interfaces:
  • mount-observe:
    • request-type: auto-connection
    • reasoning: Newer snapd versions seem to require this to be connected for Steam to function properly. We’ve had many issue reports for this ( Steam can't launch: Steam now requires user namespaces to be enabled · Issue #519 · canonical/steam-snap · GitHub , Steam stopped working · Issue #500 · canonical/steam-snap · GitHub, Steam Snap fails to start: “user namespaces must be enabled” error on Ubuntu · Issue #508 · canonical/steam-snap · GitHub). This is reasonable for Steam since mount-observe is a common functionality for Steam, anyway.

[store-requests-bot]

This request has been added to the queue for review by the @reviewers team.

[jslarraz]

Hey @ashtonn

Given that steam snap

• already plugs steam-support interface, which is highly privileged. Granting auto-connection to the mount-observe snap does not increase the attack surface
• snap snap already had access to /proc/self/mountinfo, this is a regression introduced by snapd that is likely affecting a big number of users

I’m going ahead and granting steam snap auto-connection to the mount-observe interface without waiting for the regular review process to fix the regression asap.