Steam install on Fedora 17

Here’s how you can get Steam working on Fedora 17, even while using the dreaded fglrx proprietary driver for ATI Radeon cards. If you’re using another video card, or already have a proprietary driver installed, that’s ok too. This method will work with any properly-installed video driver.

Preparation for Steam install

Regardless of what video card you’re using, you will need a fully functional proprietary driver installed for it. Steam relies on some graphics capabilities that the default ‘radeon’ and ‘nouveau’ drivers just don’t have. So install the proper drivers before proceeding.

Steam install on Fedora 17

1. Install RPMfusion repos.

sudo yum localinstall --nogpgcheck\
 http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm \
http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm

2. Install Steam game dependencies.

sudo yum -y install libtxc_dxtn.{i686,x86_64} mesa-libGL-devel.{i686,x86_64}\
 openal-soft.i686 mate-dialogs mesa-libGLU.{x86_64,i686} xorg-x11-fonts-100dpi

3. Ensure the 100dpi fonts are in your fontpath.

(This works around the error:
ILocalize::AddFile() failed to load file “public/steambootstrapper_english.txt”.

vim ~/.xinitrc
    xset +fp /usr/share/fonts/X11/100dpi

4. Go to Suse’s Steam site and grab the Fedora 17 rpm.

wget http://download.opensuse.org/repositories/games/Fedora_17/x86_64/steam-1.0.0.18-1.1.x86_64.rpm

5. Disable SELinux temporarily.

Since Steam is not yet supported on Fedora, it can be tricky to get it running with SELinux enabled. Disable it for the initial install.

sudo setenforce 0

6. Install steam.

sudo yum localinstall steam*.rpm

7. Run it.

steam

8. Configure your system to use the Steam game libraries

When you install a game through Steam, you might need to tell your system where to find the libs for it. (This was necessary for Trine 2, but not for TF2.)

sudo vim /etc/ld.so.conf.d/steam.conf
    /home/dakini/.local/share/Steam/SteamApps/common/Trine 2/lib/lib32

ldconfig

And that’s all there is to it! Any game-specific issues can usually be sorted out by running the game binary via command-line and looking for errors. Running ‘ldd’ on some of the executables will tell if you if there are any more library issues to resolve. And running ‘strace’ on any of the game launchers can give you feedback about missing files and other errors.