Steam

This repository contains the latest steam package for connecting to the Steam network from Valve. This package cannot be included in the main Fedora repository as it’s not free and is not shipped in source form. Since the Steam license allows package redistribution with a specific note for repacking in Linux distributions; the package is now available in RPMFusion.

This repository requires that the RPMFusion or multimedia repository be enabled on your system for the VA-API Intel driver (libva-intel-driver).

Along the main Steam package for Fedora are SteamOS session files and binaries for running a Steam-only session in Big Picture Mode.

Package information

This packages try to comply as maximum to the Fedora Packaging Guidelines; this means they have debuginfo packages, default Fedora’s GCC compile time options (where possible) and standard locations for binaries, data and docs.

The main Steam package is 32 bit only, so also on 64 bit systems the package will be 32 bit based. On the contrary, the xpad kernel module and SteamOS files are native to each architecture.

Supported distributions:

  • Fedora – i686/x86_64
  • CentOS/RHEL – x86_64

Installation of the Steam client

To install the repository on a supported Fedora distribution, run as root the following commands to install the client and the joystick/gamepad drivers:

dnf config-manager --add-repo=https://negativo17.org/repos/fedora-steam.repo dnf -y install steam kernel-modules-extra

For CentOS, substitute dnf commands and paths where appropriate; i.e.:

yum-config-manager --add-repo=https://negativo17.org/repos/epel-steam.repo
yum -y install steam

If you are running a 64 bit desktop with proprietary Nvidia or AMD drivers; make sure you have the appropriate 32 bit OpenGL libraries installed; otherwise Steam will throw a “GLX error” when starting and games will not work.

Big Picture Mode

To make “Big Picture” work in Fedora or CentOS/RHEL, enable this SELinux boolean as root:

setsebool -P allow_execheap 1

Moving the Steam client installation

I often poke around with the client, check folder sizes in my home folder, etc. Running a du -hs * in my home folder to check how much space my Pictures or Music folder take it’s very fast. But since the Steam client is installed in a hidden subdirectory it’s not really clear how much space it does take, especially when it reached nearly 70% of my whole drive.

To move the Steam installation (for example in your home folder), simply issue the following command:

$ mv ~/.local/share/Steam ~/Steam

And launch the client again, it will adjust all the symlinks for folders, saves, etc. by itself. Even the desktop / system shortcuts for the games work because they launch Steam (which is in the path) with the appropriate Steam game ID.

Screenshot from 2014 06 09 154226
Screenshot from 2014 06 09 154226

Additional hardware support

There are packages for additional hardware devices:

In-Home streaming configuration

Valve has supported In-Home streaming (both as a server and as a client) in Linux for quite some time. According to the documentation, streaming uses UDP ports 27031 and 27036 and TCP ports 27036 and 27037.

The package includes the required service definitions for FirewallD. If you have installed a default desktop, FirewallD should be your firewall solution. To make sure that Steam can listen on the required ports through your firewall software, execute the following commands as root.

You should then be able to see the word “steam” by running:

firewall-cmd --get-services | grep steam

Then get the firewall zone you are in, and enable the service for it. For example, on my system, to get the firewall zone I’m using:

# firewall-cmd --get-active-zones 
public
  interfaces: em1

Then enable it permanently (i.e. at reboot) and immediately with these commands:

firewall-cmd --zone=public --add-service=steam-streaming --permanent
firewall-cmd --zone=public --add-service=steam-streaming

Now start up two Steam clients with your user on the same network, and you should see games installed on both systems as available for playing in both Steam clients.

In-Home Streaming (hardware decoding/encoding)

In-Home Streaming hardware decoding is exposed through different backends, depending on the hardware you are running. These are detected at runtime, and are all 32 bit libraries also on 64 bit systems, as the client is 32 bit only.

These are the following backends, depending on what you are running on your system you should use something different:

VendorDriverEncodingDecoding
IntelintelVA-APIVA-API
NvidianvidiaNVENC/NVFBCNVDEC/VDPAU
AMDradeonVA-APIVA-API/VDPAU
Nvidianouveau-VA-API/VDPAU
AMDamdgpuVA-APIVA-API/VDPAU

The various components required for the hardware decoding are pulled in automatically as dependencies by the steam package. After installing the steam package, you can enable hardware support for decoding/encoding the video stream, like in the following picture:

During streaming, additional details can be seen by pressing F6. This will display stream statistics along with the encoder and decoder used on the server and client.

Additional controller configuration

The package contains the UDEV rules for lots of gamepads as presented in the Steam devices repository.

Appropriate support for the Nvidia controllers has been added and also to make them appear as a Game Pad and not as a mouse where a touchpad is present (this prevents the “ghost” keypresses in Steam Big Picture mode).

Detection for drawing tablets and multimedia keyboards has been modified to have them properly detected as mice/keyboards and not joysticks due to a bug in the Linux kernel. This as well prevents the “ghost” keypresses in Steam Big Picture mode.

SteamOS session

Inside the repository there are packages specific for the SteamOS customization that have been implemented by Valve for their Debian based distribution. It is now possible to install all files and packages required to launch a Steam only session from the login manager. This will bring up Steam in SteamOS mode (-steamos switch) and allows you to configure all system aspects directly in the Steam interface.

To enable the SteamOS session and enjoy the same experience provided by Valve’s SteamOS; install all the above packages plus the additional SteamOS packages:

yum -y install steamos-compositor

On a 64 bit system:

yum -y install steamos-compositor steamos-modeswitch-inhibitor.i686

This will install the following components on your system:

  • The modeswitch inhibitor, a library that is used to ignore the Xrandr resize requests performed by games.
  • The SteamOS compositing manager, which takes care of scaling the output to your native resolution, providing a seamless transition between games with different resolutions than your native monitor/TV resolution.
  • The required support files for the SteamOS session (binaries, cursor, scripts, etc.).
  • The PolicyKit policies that are required to configure additional permissions on the system compared to a normal user, as it is in Valve’s SteamOS (for example for configuring network, resolution, etc.).

These are samples of the additional screens you get with Steam Big Picture in SteamOS mode, most of them on the right side, under “System”:

Example of the packages installed:

$ rpm -qa steam*
steamos-modeswitch-inhibitor-1.10-2.fc29.x86_64
steamos-compositor-1.35-1.fc29.x86_64
steamos-base-files-2.58-1.fc29.noarch
steam-1.0.0.59-7.fc29.i686

If you have ever installed SteamOS from Valve’s provided media, you will get the same behaviour for the installation. Login once with your user, complete the user Steam installation (with the system icon or by running Steam from the command line) and logout. Now you can login back again using the SteamOS session and experience the SteamOS interface on your Fedora system.

After logging in, if you want to experience Steam on a TV, make sure to go to the audio settings and configure audio output through the HDMI connector of your video card. After testing it and getting back to your normal account, remember to switch back to your normal audio output as Gnome will keep track of your last used audio device, that after testing SteamOS is always the HDMI output.

If you want to make SteamOS start immediately after powering up the system, make sure to enable auto login for your user and all should be fine.

SteamOS appliance

An alternative to configure SteamOS with your user and then switch to autologin, is to install a minimal Fedora system and enable autologin directly from the beginning.

To create such experience, proceed as follows:

  • Install Fedora Workstation, selecting the Minimal configuration.
  • Make sure that when partitioning the majority of the space on the system is allocated to the /home mountpoint, as this is where all the games will reside.
  • Create a user called steam with a password set.
  • Then execute as root the following commands to get the base system up and running:
# dnf group install hardware-support
# Xorg xorg-x11-drv-evdev libglvnd-egl vulkan-loader.x86_64 vulkan-loader.i686 lightdm flatpak NetworkManager-wifi kernel-modules-extra bluez
# dnf config-manager --add-repo=https://negativo17.org/repos/fedora-steam.repo
# dnf install steam steamos-compositor steamos-modeswitch-inhibitor.x86_64 steamos-modeswitch-inhibitor.i686
# setsebool -P allow_execheap 1
# systemctl enable sshd.service
# systemctl enable lightdm.service
# systemctl set-default graphical.target
  • After this, edit /etc/lightdm/lightdm.conf from LightDM to allow autologin:
pam-service=lightdm-autologin
pam-autologin-service=lightdm-autologin
user-session=steamos
autologin-user=steam
autologin-session=steamos
  • Then create /var/lib/AccountsService/users/steam with the following content:
[User]
Session=steamos
XSession=steamos
Icon=/home/steam/.face
SystemAccount=false
  • If you also need the Nvidia drivers:
# dnf config-manager --add-repo=https://negativo17.org/repos/fedora-nvidia.repo
# dnf install kernel-devel akmod-nvidia nvidia-driver-libs.x86_64 nvidia-driver-libs.i686

Known issues

The following list of issues are related to the fact that the SteamOS system is designed around Debian, so there are a couple of things that are not supported by this setup:

  • Checking for system package updates (not the Steam client updates themselves) from the interface is broken. The Steam client binary calls dpkg directly.
  • There is no bug reporting tool installed, as this is not a configuration supported by Valve.

Bugs

The address for contacting me is in the package’s changelog.

249 thoughts to “Steam”

  1. Hi, I install steam from this repo on Fedora 24 + nvidia. Steam client is starting with “Updating Steam… Checking for available update…” window and this window just stuck without any result… I restart it several times, wait about half an hour, but nothing just happened… So, how to fix it?

    Reply

    1. The client itself is download at first start. If you never did, and want to retry, you can delete the .steam folder as depicted in the repository page.

      Reply

  3. It wasn’t running for me. I got:

    $ steam
    Running Steam on fedora 23 64-bit
    STEAM_RUNTIME is enabled automatically
    Installing breakpad exception handler for appid(steam)/version(1459463254)
    libGL error: No matching fbConfigs or visuals found
    libGL error: failed to load driver: swrast

    This was fixed by installing the below package:

    yum install xorg-x11-drv-nvidia-libs.i686

    Reply

  4. Hello, hardware decoding lno longer works in Fedora 23 64bit. Steam searches for wrong path, when i symlink it it looks like incompatible version.

    Reply

  5. I have followed the steps above and now my screen is messed u and steam does not work at all . My resolution is fine, but windows are 10x larger and icons are huge, every single app is somehow zoomed in…..

    Reply

    1. Seems like a graphic driver problem, the screen was not reset to the correct resolution when it should have switched mode back.

      Reply

  6. For anyone else looking for the package to install the 32 bit libraries when using the negativo17 nvidia repos, it’s:

    dnf install nvidia-driver-libs.i686

    Reply

  7. I’ve installed the latest Steam package from RPMfusion, but it seems like the uinput permissions for the Steam Controller are still not being set properly.

    getfacl returns this:

    getfacl: Removing leading ‘/’ from absolute path names
    # file: dev/uinput
    # owner: root
    # group: root
    user::rw-
    group::—
    other::—

    I still have to manually chmod /dev/uinput in order to get gamepad emulation to work.

    Reply

      1. Yeah I am using that version.

        Turns out I had to modprobe uinput on boot in order for the rules to take effect. Modprobing after boot does nothing.

        I am not sure why I have to modprobe uinput at all though. The /dev/uinput file is already there and usable regardless.

        Reply

        1. I had the same problem as Benjamin Xiao. I had to modprobe uinput during boot for the udev rule to work. I’d suggest adding the following file to the steam package to workaround this recent kernel/systemd bug.

          File: /etc/modules-load.d/uinput.conf
          Contents:
          uinput

          You can probably easily guess or know that this simply tells systemd to load the uinput module during boot and fixes the permission problem. I don’t think there is any issue doing this since it’s the udev rule already installed by valve giving additional access not this module load and also the module is kind of loaded already at boot just not the right way (maybe too early for udev?)

          Reply

  8. Hi guys, here’s a workaround after I poking here and there trying to fix segmentation fault for Dota 2 after applying
    steam-noruntime package…

    On your terminal:
    STEAM_RUNTIME=1 steam
    cd ~/.steam/bin32/steam-runtime/amd64/lib/x86_64-linux-gnu/
    mv -v ./* ~/.steam/bin64/
    STEAM_RUNTIME=0 steam

    It seems that segmentation fault is caused by 64bit libs required by Dota 2 not properly located? (or something else?)

    Can we do anything about this? Is this Valve problem?
    I don’t really know how Steam works on managing its runtimes location upon receiving STEAM_RUNTIME var.

    Reply

    1. Hello, thanks for the information, I will look if there’s something that I can apply to the noruntime package to make it work (I have Dota 2 as well, but not yet installed).

      Valve is also working with Redhat to make sure all the client programs (gcc libraries, etc.) are fixed when running under Fedora or RHEL. Having said that, as reported in the repository page, Valve does not support running Steam without the runtime and will just bounce you back and turn down any bug that is disabling it. Valve’s supported configuration is only the one offered with the basic Steam package; so with the Ubuntu runtime enabled. Also in SteamOS is enabled.

      Reply

    1. They have been added. Thanks for reporting.
      They are not easy to get as they are 99% installed by other applications or Gstreamer audio package.

      Reply

  10. I have a question, or maybe someone knows how to do, and more specifically – how to use steam broadcast on fedora 23 ?

    Reply

  11. So, this happened when I tried to run steam or steam games in Fedora 23,

    undefined symbol: _XEatDataWords optirun in /usr/lib64/libXv.so.1

    but it will work perfectly when i install it with no runtime option

    Reply

  13. After a system update I got a

    “You are missing the following 32-bit libraries, and Steam may not run: libc.so.6”

    Any clue??

    Reply

    1. Nevermind, it is working. After removing the package and deleting any steam folder in my home directory, I reinstalled the package on working again. Although I have to reinstall my games off course 😀

      Reply

  14. hi all,
    i have this error:

    ~]$ steam
    Running Steam on fedora 22 64-bit
    STEAM_RUNTIME is enabled automatically
    Installing breakpad exception handler for appid(steam)/version(0)
    /home/bid/.local/share/Steam/steam.sh: line 756: 4026 Segmentation fault (core dumped) $STEAM_DEBUGGER “$STEAMROOT/$STEAMEXEPATH” “$@”

    do you know what is the problem?
    tnx for the help

    NDR: fedora 22 x86_64, Official Nvidia drivers 32bit + 64bit
    STEAM_DEBUG output -> http://pasted.co/22f9f03c

    Reply

  15. Hi,

    I need help with a little problem here. After installing steam-noruntime the command ‘dnf autoremove’ reports:

    Error: problem with installed package SDL2_image-2.0.0-7.fc22.i686.
    problem with installed package SDL2_mixer-2.0.0-7.fc22.i686.
    problem with installed package SDL2_net-2.0.0-2.fc22.i686.
    problem with installed package SDL2_ttf-2.0.12-4.fc22.i686.
    problem with installed package SDL_image-1.2.12-11.fc22.i686.
    problem with installed package SDL_mixer-1.2.12-7.fc22.i686.
    problem with installed package SDL_ttf-2.0.11-6.fc22.i686.
    problem with installed package alsa-plugins-arcamav-1.0.29-1.fc22.i686.
    [...]
    problem with installed package pangox-compat-0.0.2-5.fc22.i686
    (try to add '--allowerasing' to command line to replace conflicting packages)

    If I run ‘dnf autoremove –allowerasing’ the steam-noruntime and its dependencies get uninstalled.

    Reply

    1. Don’t know what this is due to, but happens on my system as well for other i686 packages. It seems dnf is telling you (in a very obfuscated way) that those are 32 bit libraries on a 64 bit system. Btw, if you want to return to the state where steam-noruntime and its dependencies are not installed, the command is dnf history.

      1) dnf history info, and get the transaction number where the package and its dependencies have been installed

      2) dnf history rollback , where the transaction number is the one previous to the one of the installation (i.e. the state where it was not installed).

      You can even point to previous points in time.

      Reply

      1. Thx for the help. I guess I’ll just ignore autoremove then 🙂

        Didn’t know about the history functionality though. Will try it next time if I’ll need it 🙂

        Reply

  17. Hi. I think the Fedora 22 package is missing dependencies on:

    libXtst-i686
    pulseaudio-libs.i686

    Please could you correct?

    Reply

    1. Hello, sorry for the late reply. According to a dependency run in the client, these are only needed if you run the client without the Steam Runtime, and those are already part of the steam-noruntime package requirements.

      $ rpm -q --requires steam-noruntime | egrep "pulseaudio-libs|libXtst"
      libXtst(x86-32)
      pulseaudio-libs(x86-32)

      May I ask you how did you get that these are missing (i.e. you installed a minimal desktop and then installed the client, etc.). Thanks.

      Reply

  18. Can you try to install only the 32 bit library prior to installing Steam?

    dnf install heimdal-libs.i686

    Reply

    1. Looks like that did the trick. Must stem from the same bug where they both provide a dependency. Thanks again for the help

      Reply

  19. I had figured since fedora likes the MIT that it wouldn’t be needed but the dnf install steam-noruntime pulled in both the 64 and 32 libraries. That means I can’t uninstall the 64 bit library as it isn’t installed

    Reply

  20. I am getting a dnf error.

    Error: Transaction check error:
    file /etc/ld.so.conf.d/heimdal.conf conflicts between attempted installs of heimdal-libs-1.6.0-0.10.20150115gitc25f45a.fc22.x86_64 and heimdal-libs-1.6.0-0.10.20150115gitc25f45a.fc22.i686

    when I run dnf install steam-noruntime it tries to pull in both 64 and 32 bit libs for heimdal-libs but there is a conflict there. There is a bug in the tracker for this error https://bugzilla.redhat.com/show_bug.cgi?id=1244316

    Does anyone know a way around this problem and or run into it yet? Thanks

    Reply

    1. Yes I did. The Heimdal package is not well done, it had that bug since forever. Heimdal is not required by almost nothing as Fedora uses the MIT implementation, so you can just remove the x86_64 package.

      Reply

  21. Hey!!!
    Thank you guys, for a awesome jobs and countless hours. Here it is. I was back in linux longtime and trusted Valve too much. Stuck on tf2.
    Fedora 22, NVIDIA 8600GS.
    TIMO

    http://rpmfusion.org/Howto/nVidia#GeForce_8.2BAC8-9.2BAC8-200.2BAC8-300.2BAC8-405

    32bit this site comments…
    Mustafa
    June 27, 2015 at 1:27 am
    I found!
    For 304x driver you have to give this command:

    sudo dnf install xorg-x11-drv-nvidia-340xx-libs.i686

    For newer driver:

    sudo dnf install xorg-x11-drv-nvidia-libs.i686

    And steam,
    dnf config-manager –add-repo=http://negativo17.org/repos/fedora-steam.repo
    dnf -y install steam

    kiitostimo

    first time no sound, no game yet i have to wrote this first.:)

    Reply

    1. And what’s the difference? Same output here.
      Also, -D is not documented in the man page. Is it debug?

      [root@buko ~]# modprobe -D xpad
      insmod /lib/modules/4.0.7-300.fc22.x86_64/extra/drivers/input/joystick/xpad.ko.xz
      [root@buko ~]# modprobe -r xpad
      [root@buko ~]# modprobe -v xpad
      insmod /lib/modules/4.0.7-300.fc22.x86_64/extra/drivers/input/joystick/xpad.ko.xz
      [root@buko ~]#

      Reply

  23. Alas, I keep getting 404 errors for both the fedora-steam repo and the fedora-spotify repo. when I run dnf update.

    Downloading Packages:
    [MIRROR] steam-1.0.0.50-3.fc22.i686.rpm: Status code: 404 for http://negativo17.org/repos/steam/fedora-22/x86_64/steam-1.0.0.50-3.fc22.i686.rpm
    [FAILED] steam-1.0.0.50-3.fc22.i686.rpm: No more mirrors to try - All mirrors were already tried without success
    Error: Error downloading packages:
    Cannot download steam-1.0.0.50-3.fc22.i686.rpm: All mirrors were tried

    This has been going on for three days. Issues on your end? Thanks!

    Reply

      1. Thank you, that cleared up the steam repo. Can’t seem to synchronize the cache to install spotify-client. Will examine further.

        Reply

  24. Hi,

    I’m trying this repo with no luck. This is what I got on a terminal:

    Running Steam on fedora 22 64-bit
    STEAM_RUNTIME is enabled automatically
    Installing breakpad exception handler for appid(steam)/version(0)
    /home/twsh/.local/share/Steam/steam.sh: línea 756: 11196 Violación de segmento (`core’ generado) $STEAM_DEBUGGER “$STEAMROOT/$STEAMEXEPATH” “$@”

    The same result when I tried with the rpmfusion nonfree repo.

    Any idea on what is wrong??

    Thanks in advance.

    Reply

    1. Don’t know if you looked, but the package is the same on here and RPMFusion.
      Can you run it from the terminal with STEAM_DEBUG set?

      $ STEAM_DEBUG=1 steam

      Do you have all required 32 bit libraries if you’re running proprietary drivers?

      Reply

      1. I could have sworn I chose to install the 32 bit libs when I installed the propietary drivers for my nvidia card. After reinstall the drivers and make sure it install the 32 bit libs the steam cliente is now working.

        Thanks a lot.

        Reply

  25. Any idea why I wouldn’t be able to get past the following in Fedora 22:

    $ steam
    Running Steam on fedora 22 64-bit
    STEAM_RUNTIME is enabled automatically
    Installing breakpad exception handler for appid(steam)/version(0)
    libGL error: unable to load driver: swrast_dri.so
    libGL error: failed to load driver: swrast

    It will just hang at this point and never load. The EULA loaded initially on the first run, but then it too would hang. I’m using pretty standard repo’s and the NVIDIA repos from here. (Best way to install CUDA and OpenCL support–thank you!)

    Reply

    1. Have you installed 32 bit libraries for the drivers? Are you using a reduced desktop (like i3 tiling window manager, etc.) that does not pull in all generic desktop dependencies?

      Reply

      1. Gotcha… Yup, it was the 32-bit dependency. I wasn’t aware of the bug in dnf where 32-bit packages do not show up in searches on 64-bit systems and wasn’t sure it was available. An explicit argument to dnf install though took care of it. Thank you!

        Reply

        1. I found!

          For 304x driver you have to give this command:

          sudo dnf install xorg-x11-drv-nvidia-340xx-libs.i686

          For newer driver:

          sudo dnf install xorg-x11-drv-nvidia-libs.i686

          Reply

  26. I get the following error when trying to use your repo —

    Failed to synchronize cache for repo ‘fedora-steam’ from ‘http://negativo17.org/repos/steam/fedora-22/x86_64/’: Yum repo downloading error: Downloading error(s): repodata/f50d52f00d28605ed173997b7f629fec35564f2dd83134e8a1ef98b86325c666-filelists.xml.gz – Cannot download, all mirrors were already tried without success; repodata/abc63a5fcbd6c2dce2c8ee06f2c61031be32b8216939174d03b9aa85cbf5b789-primary.xml.gz – Cannot download, all mirrors were already tried without success, disabling.

    Reply

  27. DNF commands as ROOT:

    dnf config-manager –add-repo=http://negativo17.org/repos/fedora-steam.repo

    dnf install steam

    Reply

  28. So I installed Fedora 22 on my PC for the first time. I used Arch Linux in the past. Anyways, I just want to play a nice and lovely game of CS:GO with my friends on Steam, but no I can’t do that. I have to search around on the web for 3 hours just to get Steam working. Whenever I try to run the command: “yum-config-manager –add-repo=http://negativo17.org/repos/fedora-steam.repo”
    I get this:
    [root@fedora dead385]# yum-config-manager –add-repo=http://negativo17.org/repos/fedora-steam.repo

    Yum-utils package has been deprecated, use dnf instead.
    See ‘man yum2dnf’ for more information.

    adding repo from: http://negativo17.org/repos/fedora-steam.repo
    YumRepo Error: All mirror URLs are not using ftp, http[s] or file.
    Eg. http://dummy
    Traceback (most recent call last):
    File “/usr/bin/yum-config-manager”, line 222, in
    grabber = repo.grabfunc; del repo
    File “/usr/lib/python2.7/site-packages/yum/yumRepo.py”, line 697, in
    grabfunc = property(lambda self: self._getgrabfunc())
    File “/usr/lib/python2.7/site-packages/yum/yumRepo.py”, line 687, in _getgrabfunc
    self._setupGrab()
    File “/usr/lib/python2.7/site-packages/yum/yumRepo.py”, line 631, in _setupGrab
    urls = self.urls
    File “/usr/lib/python2.7/site-packages/yum/yumRepo.py”, line 875, in
    urls = property(fget=lambda self: self._geturls(),
    File “/usr/lib/python2.7/site-packages/yum/yumRepo.py”, line 872, in _geturls
    self._baseurlSetup()
    File “/usr/lib/python2.7/site-packages/yum/yumRepo.py”, line 838, in _baseurlSetup
    self.check()
    File “/usr/lib/python2.7/site-packages/yum/yumRepo.py”, line 558, in check
    self.ui_id, repo=self)
    yum.Errors.RepoError: Cannot find a valid baseurl for repo: dummy

    I am in su right now, so I don’t need to use sudo all the time. Anyways, any ideas on how to fix this?

    Reply

  29. To install the repo on Fedora 22 we need to do:

    dnf config-manager –add-repo=http://negativo17.org/repos/fedora-steam.repo

    Right?

    Reply

  30. Sir, something not working properly.

    [anis@localhost yum.repos.d]$ sudo dnf install steam
    Last metadata expiration check performed 0:33:34 ago on Mon May 25 21:15:50 2015.
    Error: package steam-1.0.0.50-1.fc22.i686 requires nss(x86-32), but none of the providers can be installed

    Anis

    Reply

    1. It seems related to dnf resolver, it happens here as well but on other packages. Try to install nss.i686 and install steam afterwards.

      Reply

  31. Hi
    Using Fedora 22, I have this error using negativo17’s Steam.

    Could you help me please ?

    $ steam –reset ; steam
    shell-init : erreur de détermination du répertoire actuel : getcwd : ne peut accéder aux répertoires parents : Aucun fichier ou dossier de ce type
    chdir : erreur de détermination du répertoire actuel : getcwd : ne peut accéder aux répertoires parents : Aucun fichier ou dossier de ce type
    chdir : erreur de détermination du répertoire actuel : getcwd : ne peut accéder aux répertoires parents : Aucun fichier ou dossier de ce type
    mv: impossible d’évaluer « /home/michael/.steam/registry.vdf »: Aucun fichier ou dossier de ce type
    Installing bootstrap /home/michael/.local/share/Steam/bootstrap.tar.xz
    Reset complete!
    shell-init : erreur de détermination du répertoire actuel : getcwd : ne peut accéder aux répertoires parents : Aucun fichier ou dossier de ce type
    chdir : erreur de détermination du répertoire actuel : getcwd : ne peut accéder aux répertoires parents : Aucun fichier ou dossier de ce type
    chdir : erreur de détermination du répertoire actuel : getcwd : ne peut accéder aux répertoires parents : Aucun fichier ou dossier de ce type
    Running Steam on fedora 22 64-bit
    STEAM_RUNTIME is enabled automatically
    Installing breakpad exception handler for appid(steam)/version(0_client)
    /home/michael/.local/share/Steam/steam.sh : ligne 730 : 5937 Erreur de segmentation (core dumped)$STEAM_DEBUGGER “$STEAMROOT/$STEAMEXEPATH” “$@”
    mv: impossible d’évaluer « /home/michael/.steam/registry.vdf »: Aucun fichier ou dossier de ce type
    Installing bootstrap /home/michael/.local/share/Steam/bootstrap.tar.xz
    Reset complete!
    Restarting Steam by request…
    Running Steam on fedora 22 64-bit
    STEAM_RUNTIME has been set by the user to: /home/michael/.local/share/Steam/ubuntu12_32/steam-runtime
    Installing breakpad exception handler for appid(steam)/version(0_client)
    /home/michael/.local/share/Steam/steam.sh : ligne 730 : 6072 Erreur de segmentation (core dumped)$STEAM_DEBUGGER “$STEAMROOT/$STEAMEXEPATH” “$@”

    Reply

    1. You’ve screwed your profile somehow:

      shell-init : erreur de détermination du répertoire actuel : getcwd

      Reply

  32. So, it looks like you need the rpmfusion (free and non-free) repos in order to install libtxc_dxtn. But currently these repositories are not working with F22 (I think it has something to do with the upcoming beta release and an infra-structure migration being done by the maintainers). Also, I can’t seem to find a libtxc_dxtn .rpm file for F22.

    Any workarounds?

    Reply

    1. Hi. Again, in answer to my own question: I was able to install the libtxc_dxtn 32 bits and libtxc_dxtn 64 bits from FC21 packages. Just download libtxc_dxtn-1.0.0-4.fc21.i686.rpm and libtxc_dxtn-1.0.0-4.fc21.x86_64.rpm from http://www.rpmfind.net/linux/rpm2html/search.php?query=libtxc_dxtn , and install using either the command line or a graphical package manager like Yumex (recommended).

      After that I was able to install Steam from this repository, with no dependency complaints. On a side note, it seems that at least under F22-Gnome and/or the current Steam version, Big Picture Mode and store videos (maybe Steam is now using HTML 5?) are working out of the box, with no need to install Flash or change the SELinux configuration.

      Reply

  33. Hi. I’m trying to install the package under Fedora 22. Apparently there’s a dependency issue:

    [user@notebook ~]$ sudo dnf install steam
    Using metadata from Sat Apr 18 13:39:14 2015 (0:00:41 hours old)
    Error: nothing provides libtxc_dxtn(x86-32) needed by steam-1.0.0.49-4.fc22.i686

    Reply

  34. Hi, I’m using your steam package on Fedora-21-x86_64. I can launch Steam games manually (e.g. Kerbal Space Program) but cannot launch them from the Steam App. Additionally, the Steam app doesn’t recognize that I have direct rendering enabled (glxinfo says that it is).

    Do you have a bug tracking page for this?

    Reply

  35. Many thanks for these instructions. It’s the weekend after Christmas here and I was just looking for something useful to do (other than raking leaves in the back yard, which I really wanted to avoid). Installing Steam on the Fedora 21 HTPC in the living room was just what I needed to redeem the day.

    Reply

    1. I’m waiting on RPMFusion support for CentOS/RHEL enablement, but this is still not there.

      If you need CentOS/RHEL 6 support, you might try this repository:

      https://soyuz.asia/repos/el/6/scx-el6-steam/

      I was contacted by the author to integrate the changes in mine (or eventually RPMFusion) but had not time to give it a deep look.

      Reply

  37. It was just because Steam games wouldn’t have rumble (Dust, Cave, Portal), witout me changing perms for the js and event devices, that I ended up generating the rules for the js and event devices managed by the xpad driver as the parent directive. Note that I only use the last two sets of rules in order to not tie the rules to a specific device, in this case vendor and product id’s are for an original Microsoft XBox360 Wireless Controller which are the 045e vendor and product 0291. Odd… the version of Steam from rpmfusion does not install such rule, hence me needing to create one.

    Reply

    1. Ok… My bad, apparently the rule IS there, only not under /etc/udev/rules.d/, as I would have expected, but as you did point out (though I apparently read /etc/ instead) in /usr/lib/udev/rules.d…
      However, for some reason these rules are being overlooked when creating the devices for my particular configuration… apparently due to the vendor id (Valve’s controller?)… Maybe creating a secondary rule for xpad devices as 99-joystick-xpad-perms.rules?

      Reply

  38. Quick correction, in the example above I used /dev/inpu/by-id/, which as it is a symbolic link does not work, since the symlink is already world readable/writeable even if its objective node file isn’t, in my case the event node was /dev/input/event20, but still the udev rules do apply and the device nodes get the correct parameters!

    Reply

  39. Just a last minute comment on the xpad driver thingy :D… So it turns out that the driver works WONDERFULLY and rumble and all is supported, as long as the device event driver is WRITEABLE, so if you simply:

    sudo chmod o+w /dev/input/by-id/*event*joystick

    You’ll get the desired functionality, however upon reboot you’ll lose that, so I wrote a quick and dirty hack to have udev do this for me, in a rule (92-xpad.rules; gotta love the name :D), like so:

    KERNEL=="event*", SUBSYSTEMS=="usb", SUBSYSTEM=="input", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="0291", MODE=="0666"

    This does work on my system, however I do reckon that different pads will not work even if they do work with this driver, which is why I thought of formulating it in a different way so that the actual DRIVER does the detection for us, like so:

    KERNEL=="event*", SUBSYSTEMS=="usb", SUBSYSTEM=="input", DRIVERS="xpad", MODE="0666"

    Indeed works!! Still this makes the node writeable by anyone, which could theoretically imply a security concern, so I decided to instead leave it like so:

    KERNEL=="event*", SUBSYSTEMS=="usb", SUBSYSTEM=="input", DRIVERS=="xpad", GROUP="games", MODE="0660"
    KERNEL=="js*", SUBSYSTEMS=="usb", SUBSYSTEM=="input", DRIVERS=="xpad", GROUP="games" MODE="0664"

    This however requires manual addition of the current user to the games group, which I’m not sure could be automated by a scriptlet in the akmod rpm or simply be a requirement to do manually and have permanent permisons on the device across reboots; my 2¢ 🙂

    Reply

    1. Many thanks for the information, I’m considering adding this to the package. I have an x-box 360 clone controller which is working fine in Steam without your UDev rule. Currently the Steam package sets this:

      $ cat /usr/lib/udev/rules.d/99-steam-controller-perms.rules 
#USB devices
SUBSYSTEM=="usb", ATTRS{idVendor}=="28de", MODE="0666"
# Oculus HID Sensor naming and permissioning
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="2833", MODE="0666"

      What are vendor 045e and product 0291? If you use Steam, do you have the same rumble functionality without adding your UDev rule?

      Reply

  40. Nice, by the way, the driver works mazingly well. I hope Valve keep on improving Linux input device (aka) joystick and gamepad support and that THAT work will eventually make its way upstream to the kernel. In the mean time I enjoy that xpad driver does provide accurate rumble_ff feedback in actual games (well, at least those I’ve tested, like Dust), on this gamepad I explicitly bought for Steam and native games alike in steam games… As soon as Valve makes a Steam Controller final version available, I’m sure as heck I’ll be getting one!

    Reply

  41. Is the improved xpad driver from the kmod and akmod installed onto the same path? I ask, because even though I installed it, and ran depmod, and rebooted, the driver loaded is still from extra/drivers/joystick path under /lib/modules/`uname -r`/ for the latest F20 3.15.6 kernel, and I don’t get the extra/xpad path, I’ve thought of manually rebuilding the src.rpm

    Reply

    1. Hello,

      if you add akmox-xpad you get the new module under extra, and that will take precedence over the installed one. On my system:

      # rpm -ql kmod-xpad-3.15.6-200.fc20.x86_64
/usr/lib/modules/3.15.6-200.fc20.x86_64/extra
/usr/lib/modules/3.15.6-200.fc20.x86_64/extra/xpad
/usr/lib/modules/3.15.6-200.fc20.x86_64/extra/xpad/xpad.ko
# find /lib/modules/3.15.6-200.fc20.x86_64/ -name "*xpad*"
/lib/modules/3.15.6-200.fc20.x86_64/extra/drivers/input/joystick/xpad.ko
/lib/modules/3.15.6-200.fc20.x86_64/extra/xpad
/lib/modules/3.15.6-200.fc20.x86_64/extra/xpad/xpad.ko
# modprobe xpad
# modinfo xpad | grep file
filename:       /lib/modules/3.15.6-200.fc20.x86_64/extra/xpad/xpad.ko
      Reply

      1. For some odd reason, and this is a newly installed Fedora 20, akmod did not install the kernel-devel package, and I have installed the Nvidia blob as well as its akmod… that turned out to be the reason why the module was not being built, odd….

        Reply

        1. You should open a bug on akmod, it is pulling in “kernel-devel” as a dependency, but kernel-devel is also provided by “kernel-debug-devel”, and since it comes alphabetically first it’s installed in place of the normal one.

          I’ve updated the guide to install “kernel-devel” explicitly.

          Reply

  42. Great to see the xpad modules! i noticed in your installation instructions you gave the commands yum -y install dkms-steam and yum -y install akmod-steam, where in your repo they are named akmod-xpad and dkms-xpad. Thanks for the great work 🙂

    Reply

  43. Failed to run steam through bumblebee
    steam from rpmfusion

    bash-4.2$ optirun steam
    Running Steam on fedora 20 64-bit
    STEAM_RUNTIME is enabled automatically
    /home/wencan/.local/share/Steam/steam.sh: line 755: 6625 Segmentation fault (core dumped) $STEAM_DEBUGGER “$STEAMROOT/$PLATFORM/$STEAMEXE” “$@”
    mv: cannot stat ‘/home/wencan/.steam/registry.vdf’: No such file or directory
    Installing bootstrap /home/wencan/.local/share/Steam/bootstrap.tar.xz
    Reset complete!
    Restarting Steam by request…
    Running Steam on fedora 20 64-bit
    STEAM_RUNTIME has been set by the user to: /home/wencan/.local/share/Steam/ubuntu12_32/steam-runtime
    /home/wencan/.local/share/Steam/steam.sh: line 755: 6875 Segmentation fault (core dumped) $STEAM_DEBUGGER “$STEAMROOT/$PLATFORM/$STEAMEXE” “$@”
    bash-4.2$

    Reply

  44. Went through all the steps and the videos of the games aren’t playing. I just get a black background instead ;/

    Reply

    1. Unfortunately Flash videos are not played with the Steam Runtime disabled, Steam does not load the Flash Plugin. Please use the Steam package as provided by RPMFusion or enable the Steam Runtime through STEAM_RUNTIME=1.

      Reply

  45. Is there any chance you could build the steamos xpad dkms driver to your package or to rpmfusion until it gets moved upstream to the kernel? I hear it has a lot of fixes, including no more blinking LED on the wireless Xbox controller. I found some packages at https://launchpad.net/~mdeslaur/+archive/steamos which seems to include the source file.

    Reply

    1. Hello, I downloaded the original xpad.c file from kernel version 3.12.6 and from git; it is quite different from the one that is available at the link you posted. Since I don’t own a Wireless X-Box 360 controller, will you be able to make some tests for me if I build the package kernel module (DKMS/aKMOD)?

      Reply

      1. The other 2 packages are for the compositor + Steam session file and the other for a library that inhibits games from resizing the screen. The compositor takes charge of expanding the game window fullscreen, so even if the TV set does not support the game resolution you will get a “nice” experience.

        Do you think that there would be any interest in running those packages on Fedora for getting a similar experience to SteamOS?

        Reply

        1. Hi, I would be willing to test the package for you, I managed to add the xpad driver via dkms a while back and it worked, I tried to look up on using akmods and building rpms instead but I didn’t really have much spare time. I would also definitely be interested in running steam as steamos on my media center, but whether you want to put time into it is completely up to you. 🙂

          Reply

  46. I’m not having any luck running steam with Fedora 20. Has anyone seen this before?

    $ STEAM_RUNTIME=1 steam
Running Steam on fedora 20 64-bit
STEAM_RUNTIME is enabled by the user
Installing breakpad exception handler for appid(steam)/version(0_client)
/home/dlewis/.local/share/Steam/steam.sh: line 755:  7280 Segmentation fault      (core dumped) $STEAM_DEBUGGER "$STEAMROOT/$PLATFORM/$STEAMEXE" "$@"
mv: cannot stat ‘/home/dlewis/.steam/registry.vdf’: No such file or directory
Installing bootstrap /home/dlewis/.local/share/Steam/bootstrap.tar.xz
Reset complete!
Restarting Steam by request...
Running Steam on fedora 20 64-bit
STEAM_RUNTIME has been set by the user to: /home/dlewis/.local/share/Steam/ubuntu12_32/steam-runtime
Installing breakpad exception handler for appid(steam)/version(0_client)
/home/dlewis/.local/share/Steam/steam.sh: line 755:  7372 Segmentation fault      (core dumped) $STEAM_DEBUGGER "$STEAMROOT/$PLATFORM/$STEAMEXE" "$@"
    Reply

    1. I finally found the problem related to segmentation faults. Steam requires the 32-bit version of the nvidia librarires…

      sudo yum install xorg-x11-drv-nvidia-libs.i686

      Reply

      1. Exactly. It’s written under the “Installation” section of the page. Please note that the Steam package here it’s slightly different than the one in RPMFusion, if you want standard Steam defaults (i.e. using the Steam Runtime) do not use the one hosted here.

        Reply

      3. Just wanted to add on to this that if you’re using the negativo17 – NVIDIA repository then you will want to instead run this:

        “`
        sudo dnf install nvidia-driver-libs-2:355.11-3.fc22.i686
        “`

        Reply

  47. Thank you very much for this.
    Just installed the Steam client + Flash on a 64Bit Korora (Fedora 20) machine.
    Works as advertised 🙂

    Merry Xmas!

    Reply

  49. On F19 x86_64 I’m getting since a couple of days these errors:

    /usr/bin/pulseaudio: symbol lookup error: /lib64/libpulsecore-3.0.so: undefined symbol: orc_program_new_from_static_bytecode

    Preloading liborc-0.4.so.0 as suggested on several sites on the web does not work for me.

    ERROR: ld.so: object '/usr/lib/liborc-0.4.so.0' from LD_PRELOAD cannot be preloaded: ignored.

    Any idea how to fix/work around this?

    Reply

    1. I think you’re mixing two different things, the pulseaudio command you pasted is a 64 bit command in fact it’s looking for a 64 bit library.

      $ ldd /usr/bin/pulseaudio | grep orc
	liborc-0.4.so.0 => /lib64/liborc-0.4.so.0 (0x00007faa487b6000)
$ rpm -qf /lib64/liborc-0.4.so.0
orc-0.4.17-2.fc19.x86_64

      while the library you want to preload for Steam is a 32 bit one.

      $ ls -al /usr/lib/liborc-*
lrwxrwxrwx. 1 root root     20 May 27  2013 /usr/lib/liborc-0.4.so.0 -> liborc-0.4.so.0.17.0
-rwxr-xr-x. 1 root root 610884 Feb 20  2013 /usr/lib/liborc-0.4.so.0.17.0
lrwxrwxrwx. 1 root root     25 May 27  2013 /usr/lib/liborc-test-0.4.so.0 -> liborc-test-0.4.so.0.17.0
-rwxr-xr-x. 1 root root  31228 Feb 20  2013 /usr/lib/liborc-test-0.4.so.0.17.0
$ rpm -qf /usr/lib/liborc-0.4.so.0.17.0
orc-0.4.17-2.fc19.i686

      I think that for some reason you’re missing a 64 bit library and this prevents pulseaudio from running. Try installing both the i686 and x86_64 variants:

      yum -y install orc.i686 orc.x86_64

      If the x86_64 one is already installed try to reinstall it with yum -y reinstall. There should be nothing to preload as I’m running with the same setup and Steam works fine without any preload.

      Reply

  50. nstall mesa-dri-filesystem.i686 mesa-dri-drivers.i686 mesa-libGLU-devel.i686 mesa-libgbm.i686 mesa-libglapi.i686 mesa-libGL.i686 mesa-libGLU.i686 mesa-libEGL.i686′

    Theses libraries are missing after installing steam, maybe you can add them? 🙂

    Reply

    1. Hello, those packages are already requirements (or dependencies of its requirements) for the steam package. How did you install it? The only way to install it without its rpm requirements is to force the installation.

      $ rpm -q –requires steam | grep mesa
      mesa-libEGL(x86-32)
      mesa-libGL(x86-32)
      mesa-libgbm(x86-32)
      mesa-libglapi(x86-32)

      Reply

Leave a Reply