Table of Contents generated with DocToc
- Please take note! Getting SteamOS help
- What is the purpose of SteamOS-Tools?
- Do I have to run everything I want to install through desktop-software.sh?
- Script [NAME] doesn't work! Fix it!
- Can I take script X for my own?
- I can't install [PACKAGE_NAME] after adding the extra repositories!
- Kodi crashes frequently for me!
For all typical (non-SteamOS tools focused) SteamOS-specific help, How-To's, and more, please see the SteamOS Wiki
SteamOS ships with a decent set of basic software. Most of this software is included only with the intention of supporting what is needed for SteamOS, the Steam client, and supporting software, to run. Some packages not installed are available in the SteamOS package pool, but not much. SteamOS-Tools aims to help supplement, automate, and help along software users may want to augment their experience, test, or experiment with SteamOS. Users are strongly advised to read the disclaimer in the main directory.
No, not at all! While desktop-software.sh can be used to install Debian packages, once the appropriate sources are added via that same script, or add-debian-repos.sh, standard Debian software and Libregeek packages can be installed with typical apt-get install commands. Apt package manager pinning helps ensure this is possible. If you run into a conflict, please check with me first via an issues ticket before notifying Valve of the conflict. While I do my best to ensure proper priority is in place to prevent such a thing, mistakes and unforeseen issues can always occur.
While I have had some great help from people in recent times, there are bound to be mistakes and even unfinished scripts in this repository. If you find one, please report it. If you know how to fix it, pull requests are very welcome. When I have an idea of something I want to do here, it may not be complete yet, but I try to maintain some semblance of balance, stability, and structure. For this reason, the testing-a and testing-b repository branches exist to server as testing grounds for SteamOS Alchemist, and SteamOS Brewmaster, respectively.
I do ask that people be patient with me. I have many other distractions to keep me busy, but you're still free to shout at me :)
While the script content I use and make has come form many places, if the AUTHORS.md file notes a specific person that contributed code, I do ask you take time to review and add that name to your script header to ensure they get fair credit for their work. While is is sometime difficult (see: Google), I do want to highlight community members who have helped me here. This is also why there is no license file. But, in all fairness, take anything form this repository that you wish to use, as long as it is not for world domination (See: Skynet and other dangers to the Galaxy).
The same issue that often affects i386 packages needed for applications like PlayOnLinux and PCSX2 require that you remove the changelog files manually for now.
The changelog usually lives at /usr/share/doc/PACKAGE/changelog.Debian.gz
Since the time of writing, the libselinux1:i386 conflict has been resolved. and libattr:i386 have been resolved with Brewmaster beta 2.55 onward . Please note the Debian approach only works if both the amd64 and i386 packages are the exact same version.
If you still experience this, legacy instructions for correcting this are below (example libattr1).
sudo rm -f /usr/share/doc/libattr1/changelog.Debian.gz
sudo rm -f /usr/share/doc/libselinux1/changelog.Debian.gz
sudo apt-get install -f
sudo apt-get install PKGNAME
Please see issue #91 for this matter. This commonly is reported by users with AMD hardware utilizing FGLRX proprietary drivers. While Kodi can* work to a degree, FGLRX (the default drive used under SteamOS) is not supported. Also note that software decoding (i.e. turning off vaapi and vdpau) will work fine on fglrx. Usually gaming rigs have more then enough power for that.
To enable/disable software decoding, please see the Kodi wiki
