Table of Contents generated with DocToc
- How do I mount a Samba share to SteamOS?
- 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 PlayOnLinux after adding the extra repositories!
- I can't install [PACKAGE_NAME] after adding the extra repositories!
- Gnome-terminal does not launch on SteamOS Brewmaster!
- Help! My game has frozen and the Guide button does not show the overlay to exit!
Mounting a samba share is immensely useful for adding files such as your music collection on another machine. For more details, please reference the Connecting to Samba shares wiki entry.
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 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).
After using add-debian-repos.sh, or dessktop-software.sh, you may notice that processing the libattr:i386, and libselinux:i386 packages fail when you attempt to install playonlinux. Issuing apt-get install -f does not fix this. You will need to remove the change logs until Valve fixes this.
Remove the change logs and try again
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 playonlinux
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.
Packages that seem to have this issue:
- libatttr1:i386
- libselinux1:i386
The changelog usually lives at /usr/share/doc/PACKAGE/changelog.Debian.gz
This issue is documented on the SteamOS bug tracker:
If you still have trouble with this, make sure you correct your locales:
sudo dpkg-reconfigure -plow locales.
If an application has frozen, you need to find and kill it via another ttv line (CTRL+ALT+F#), where # is another numerical digit besides 7 (the line steamcompmgr runs under). Look for a line that reads:
steam 2614 10.2 1.8 320376 110888 ? Sl 10:21 0:01 /home/steam/.local/share/Steam/steamapps/common/game/game-executable
Kill the application from the example above (if the Steam guide button does not allow you to exit the game):
sudo kill -9 2614
Alternatively, to "reboot" Steam / kill the steamos session, issue:
sudo pkill steam
I made a video detailing some of the common complaints and what I feel about them. Keep in mind this is merely my opinion from usages since the Steam Controller was released to preorder purchasers.
Additionally, a comment on that video by 8BitCerberus sums things up well:
Valve actually described precisely this thought process for the ergonomics back in late 2013 or early 2014 (will have to see if I can dig up the interview or article I saw it in), because it tended to more natural positioning of your thumbs over the pads, but also so they can take a rest without actually touching the pads all the time (and thus constantly sending input). You also might notice with typical controllers, that your hands tend to "roll" inward for proper grip, but with the Steam Controller it encourages them to roll outward. Imagine sitting cross-legged and letting your hands fall palm-up on your knees, that's kind of the position the Steam Controller is going for (though not quite so completely relaxed :) ), the curve of the controller seems to be suggesting this, too.
It's something I noticed immediately with the prototype, how natural and comfortable it felt to hold it, even for extended gaming sessions. And that's carried over to the final build, even if the handles are slightly narrower. With my Xbox 360 and Sixaxis/Dualshock 3 I have to take breaks every few hours because my hands get crampy, and don't even get me started on older NES/SNES controllers... how on earth did we make it past our youth without crippling ourselves with those unergonomic beasts?
