Give these a try before opening an issue.

• If you can't run a Native game, try forcing Proton Experimental.
• If you can't run a game installed in another storage device, try installing the game on the default storage device instead.
• If you can't run a game with your dedicated GPU and have an integrated GPU, try using your integrated GPU.
• Connect hardware-observe and system-observe: snap connect steam:hardware-observe, snap connect steam:system-observe.
• Restart your computer (especially after updating packages or snaps relating to Steam or drivers)

You can still open an issue if one of these workarounds fixes a problem, but please include what you've tried in your issue.

You may check the reports discussions for troubleshooting tips with a specific game, and expected results. Also check ProtonDB to see if your game should work based on other's input. If our reports don't contain the game you're experiencing issues with, feel free to add it with the steam.report tool. Some games may also be listed on the Known Workarounds page.

You can also check the PC Gaming Wiki for information on game compatibility, local and cloud game files, and system support.

snap refresh steam --<branch>

Available branches: stable, candidate, beta, edge

See more info with snap info steam.

snap info steam

Run Steam with

snap run steam

Steam and game-related logs will be displayed in the same terminal window.

The most detailed logs can be gathered by compressing the logs found in ~/snap/steam/common/.local/share/Steam/logs and providing the archive.

To create a file with the output of a specific game, add the following to a game's Launch Options:

%command% > $HOME/game_log 2>&1

This will create a text file containing the game's output in /home/$USER/snap/steam/common/game_log.

Credit to thatLeaflet.

Alternatively, just copy/paste the logs from running Steam in the terminal starting from pressing the "Play" button in Steam.

sudo dmesg

Particularly, lines with apparmor="DENIED" and "snap.steam.steam" are most useful.

snap run --shell steam

Then, run cd $SNAP as most directories you want will be here. Other useful directories may be listed in env. Type exit or ctl+D to exit.

You can modify the launch options for a specific game by right-clicking the game in your library > Properties > Launch Options. Any options should end with %command%.

Steam UI frozen or not responding? Try running Steam with snap run steam -vgui to use the old Steam UI, or try snap run steam --reset.

Further reading: https://github.com/canonical/steam-snap/issues/266#issuecomment-1605657472, https://github.com/ValveSoftware/steam-for-linux/issues/9649, https://github.com/ValveSoftware/steam-for-linux/issues/9692

See the GPU section of the FAQ.

Enable HiDPI support in the client by going to Steam > Settings > Interface and check Enlarge text and icons based on monitor size. Then, restart Steam for the changes to take effect.

With PR #34, Steam should correctly display cursors at their right size (and with the right icons!).

The Arch wiki also has some information regarding Steam and HiDPI issues.

Individual games and setups will often face unique issues, which is why it may be useful to report games/your setup to us for review. As of Snap revision 66, a script is included to automatically collect some system data and open a new discussion post for reporting.

As of revision 165 (currently stable), this script has be upgraded to use a GTK-based dialog. To use it, follow the steps below:

1. Ensure system-observe and hardware-observe are connected with snap connect steam:system-observe and snap connect steam:hardware-observe respectfully
2. Right click Steam and select "Report", or run snap run steam.report from a terminal window
   • If the necessary connections aren't connected, you'll see a prompt to do so
   • The report window may take a few seconds to gather information
3. Copy the resulting report, or use the buttons to open a new issue or discussion with your report information auto-filled

Example report dialog:

The CLI version of the report tool can still be used, simply run snap run steam.report --cli.

NOTE: Game report discussions are NOT a replacement for issues. Instead, discussion posts are a way to communicate a game's functionality with your setup and troubleshoot with other users. If the game, your setup, or other users' setups expose a new problem, an issue should be opened. This is to reduce issue clutter, and discuss workarounds to specific games.

Check existing issues for information regarding any issue you may have first. If nothing exists, open a new issue describing your problem here. Helpful information to include would be your Steam Snap and snapd versions, Proton version(s), system/GPU information, and any relevant logs. You may use the Steam Report tool described above to gather most of the needed information for you, just run it with --no-submit.

Unverified builds are UNTESTED and may not be stable.
You probably shouldn't be doing this unless recommended to or are testing a specific fix. Always revert to a verified branch afterwards.

Download the snap artifact you need from its Action. They usually can be found on the "Summary" tab of the Action corresponding to the commit/merge. All action runs can be found here, too.

Unzip the file you downloaded and open up a terminal. Run snap install /path/to/your/steam.snap --dangerous.

Now, run Steam as usual with snap run steam.

After testing the change, you need to revert to a verified branch to get regular updates again.

Run snap refresh steam --amend to switch to a verified branch.