Troubleshooting
This page is intended for help debug issues and explain some common errors you may encounter.
To gain further output, run AdwSteamGtk in a terminal with:
flatpak run io.github.Foldex.AdwSteamGtk
Output is prefixed and color coded:
- → Normal output
- ✦ Notification/Warning, but continues running
- ✖ Error, execution failed
The installer patches the steam client's files directly in order to theme the interface.
This means that a steam client update may reset these files, so try reinstalling if an update makes Steam appear unthemed.
Make sure to read: Custom CSS
As the feature can cause breakages, try disabling it while troubleshooting any issues.
Use the provided menu option
The installer looks for a symlink to resolve the steam data directory to install into, this means it was not found.
-
For Native Steam this is:
~/.steam/steam -
For Flatpak Steam this is:
~/.var/app/com.valvesoftware.Steam/.steam/steam
By default both are tested, so seeing this message means that both of these paths were not valid.
Typically they should be pointing to:
-
Native:
~/.local/share/Steam -
Flatpak:
~/.var/app/com.valvesoftware.Steam/.local/share/Steam
Ensure they exist and point to the correct location.
This means both flatpak and native steam data dirs could not be found, so the theme was not installed.
See Failed to Find Valid Symlink
This means the installer has exited with some error. Check the Output for more info.
These errors are related to extracting the latest release zip file. The ZIP is stored here:
~/.var/app/io.github.Foldex.AdwSteamGtk/cache/AdwSteamInstaller/latest.zip
Usually these errors can be resolved by deleting this file and relaunching.
The ZIP file is corrupted, or possibly an incomplete download. See Above.
Some IO Error has occurred, preventing the ZIP from being read.
These errors are related to parsing the latest release ZIP file to get available colorthemes.
They are typically the same as Extract
These errors are related to the initial query to github's API to check for the latest release.
Typically these are an issue on github's end and can be resolved by retrying.
The API returned non-valid JSON.
The API returned valid JSON but it is missing the version and download urls we need.
These errors are related to downloading the actual release zip returned from github's API.
Typically these are an issue on github's end and can be resolved by retrying.