Difference between revisions of "Steam"

From ArchWiki
Jump to: navigation, search
(Killing standalone compositors when launching games)
(steam-session-git is not longer under active development and is, therefore, no longer worth mentioning.)
 
(317 intermediate revisions by more than 100 users not shown)
Line 1: Line 1:
 
[[Category:Gaming]]
 
[[Category:Gaming]]
[[Category:Wine]]
 
 
[[ja:Steam]]
 
[[ja:Steam]]
 +
[[ru:Steam]]
 
[[zh-CN:Steam]]
 
[[zh-CN:Steam]]
{{Article summary start}}
+
{{Related articles start}}
{{Article summary text|[http://store.steampowered.com/about/ Steam] is a content delivery system made by Valve Software. It is best known as the platform needed to play Source Engine games (e.g. Half-Life 2, Counter-Strike). Today it offers many games from many other developers.}}
+
{{Related|Steam/Wine}}
 +
{{Related|Steam/Troubleshooting}}
 +
{{Related|Steam/Game-specific troubleshooting}}
 +
{{Related articles end}}
 +
From [[Wikipedia:Steam (software)|Wikipedia]]:
 +
:Steam is a digital distribution, digital rights management, multiplayer and communications platform developed by Valve Corporation. It is used to distribute games and related media online, from small independent developers to larger software houses.
  
{{Article summary heading|Related}}
+
[http://store.steampowered.com/about/ Steam] is best known as the platform needed to play Source Engine games (e.g. Half-Life 2, Counter-Strike). Today it offers many games from many other developers.
{{Article summary wiki|Wine}}
+
{{Article summary wiki|Steam/Game-specific troubleshooting}}
+
{{Article summary end}}
+
 
+
From [[Wikipedia:Steam (software)|Wikipedia]]:
+
: ''Steam is a digital distribution, digital rights management, multiplayer and communications platform developed by Valve Corporation. It is used to distribute games and related media online, from small independent developers to larger software houses.''
+
  
== Native Steam on Linux ==
+
== Installation ==
  
 
{{Note|
 
{{Note|
 
* Arch Linux is '''not''' [https://support.steampowered.com/kb_article.php?ref=1504-QHXN-8366 officially supported].
 
* Arch Linux is '''not''' [https://support.steampowered.com/kb_article.php?ref=1504-QHXN-8366 officially supported].
* Because the Steam client is a 32-bit application, you will need to enable the [[multilib]] repository if you have a 64-bit system. It may also make sense to install {{Grp|multilib-devel}} to provide some important multilib libraries. You also most likely need to install the 32-bit version of your graphics driver to run Steam.
+
* If you have a 64-bit system, enable the [[multilib]] repository.
 
}}
 
}}
  
Steam can be installed with the package {{Pkg|steam}}, available in the [[official repositories]]. If you have a 64-bit system, enable the [[multilib]] repository first.
+
[[Install]] the {{Pkg|steam}} package.
  
 
Steam is not supported on this distribution. As such some fixes are needed on the users part to get things functioning properly:
 
Steam is not supported on this distribution. As such some fixes are needed on the users part to get things functioning properly:
  
*Steam makes heavy usage of the Arial font. A decent Arial font to use is {{Pkg|ttf-liberation}} or one of the official Microsoft fonts packages containing Arial: {{AUR|ttf-microsoft-arial}}, {{AUR|ttf-ms-win8}},{{AUR|ttf-office-2007-fonts}}, {{AUR|ttf-win7-fonts}} or {{AUR|ttf-ms-fonts}}. See [[MS Fonts]] for more details. Asian languages require {{Pkg|wqy-zenhei}} to display properly.
+
* Steam makes heavy usage of the Arial font. A decent Arial font to use is {{Pkg|ttf-liberation}} or [[Steam/Troubleshooting#Text is corrupt or missing|the fonts provided by Steam]]. Asian languages require {{Pkg|wqy-zenhei}} to display properly.
 +
* If you have a 64-bit system, you '''must''' install the 32-bit Multilib version of your [[Xorg#Driver installation|graphics driver]], {{pkg|lib32-alsa-plugins}} to enable sound, and {{pkg|lib32-curl}} to enable update at first run.
 +
* Several games have dependencies which may be missing from your system. If a game fails to launch (often without error messages) then make sure all of the libraries listed in [[Steam/Game-specific troubleshooting]] are installed.
  
*Most games require {{Pkg|libtxc_dxtn}} and {{Pkg|lib32-libtxc_dxtn}} when using mesa drivers, so it is recommended to install these packages.
+
== Usage ==
  
*Several games have dependencies which may be missing from your system. If a game fails to launch (often without error messages) then make sure all of the libraries listed in [[Steam/Game-specific troubleshooting]] are installed.
+
=== Big Picture Mode ===
  
=== Troubleshooting ===
+
To start Steam in Big Picture Mode from a [[Display manager]], create a {{ic|/usr/share/xsessions/steam-big-picture.desktop}} file with the following contents:
  
{{Note|
+
{{hc|/usr/share/xsessions/steam-big-picture.desktop|<nowiki>
* In addition to being documented here, any bug/fix/error should be, if not already, reported on Valve's bug tracker on their [https://github.com/ValveSoftware/steam-for-linux GitHub page].
+
[Desktop Entry]
* Connection problems may occur when using DD-WRT with peer-to-peer traffic filtering.
+
Name=Steam Big Picture Mode
}}
+
Comment=Start Steam in Big Picture Mode
 +
Exec=/usr/bin/steam -bigpicture
 +
TryExec=/usr/bin/steam
 +
Icon=
 +
Type=Application</nowiki>}}
  
==== GUI problems with KDE ====
+
=== Steam runtime ===
  
: Valve GitHub [https://github.com/ValveSoftware/steam-for-linux/issues/594 issue 594]
+
See [[Steam/Troubleshooting#Steam runtime issues]].
  
If you are using KDE and you have problems with the GUI (such as lag or random crashes), in KDE system settings, go to ''Workspace Appearance and Behaviour > Desktop Effects > Advanced''. Change "Compositing type" from "XRender" to "OpenGL".
+
== Tips and tricks ==
  
==== The close button only minimizes the window ====
+
=== Launching games with custom commands ===
  
: Valve GitHub [https://github.com/ValveSoftware/steam-for-linux/issues/1025 issue 1025]
+
{{Style}}
  
To close the Steam window (and remove it from the taskbar) when you press '''x''', but keep Steam running in the tray, set the environment variable {{ic|STEAM_FRAME_FORCE_CLOSE}} to {{ic|1}}. You can do this by launching Steam using the following command.
+
Steam has fortunately added support for launching games using your own custom command. To do so, navigate to the Library page, right click on the selected game, click Properties, and Set Launch Options. Steam replaces the tag {{ic|%command%}} with the command it actually wishes to run. For example, to launch Team Fortress 2 with primusrun and at resolution 1920x1080, you would enter:
$ STEAM_FRAME_FORCE_CLOSE=1 steam
+
  
==== Flash not working on 64-bit systems ====
+
primusrun %command% -w 1920 -h 1080
  
: Steam Support [https://support.steampowered.com/kb_article.php?ref=1493-GHZB-7612 article]
+
On some systems optirun gives better performances than primusrun, however some games may crash shortly after the launch. This may be fixed preloading the correct version of libGL. Use:
 +
 +
locate libGL
  
First ensure {{Pkg|lib32-flashplugin}} is installed. It should be working at this point, if not create a local Steam Flash plugin folder:
+
to find out the available implementations. For a 64 bits game you may want to preload the nvidia 64 bits libGL, then use the launch command:
$ mkdir ~/.steam/bin32/plugins/
+
and set a symbolic link to the global lib32 flash plugin file in your upper new folder
+
$ ln -s /usr/lib32/mozilla/plugins/libflashplayer.so ~/.steam/bin32/plugins/
+
  
==== Text is corrupt or missing ====
+
LD_PRELOAD=/usr/lib/nvidia/libGL.so optirun %command%
 
+
The Steam Support [https://support.steampowered.com/kb_article.php?ref=1974-YFKL-4947 instructions] for Windows seem to work on Linux also: Simply download [https://support.steampowered.com/downloads/1974-YFKL-4947/SteamFonts.zip SteamFonts.zip] and install them (copying to {{ic|~/.fonts/}} works at least).
+
 
+
==== Error on some games: black textures/S3TC support is missing ====
+
 
+
Install the following dependencies:
+
* {{Pkg|libtxc_dxtn}}
+
* {{Pkg|lib32-libtxc_dxtn}}
+
 
+
====Black screen on (Valve?) games (but audio works)====
+
 
+
Check the Steam stdout/stderr for Error lines, some quick dependencies for reference:
+
* {{Pkg|lib32-intel-dri}} (not confirmed as absolutely necessary)
+
 
+
Run Steam from console via primusrun steam
+
 
+
If using KDE, disable all desktop effects ({{ic|Alt+Shift+F12}}) before starting Steam.
+
 
+
==== SetLocale('en_US.UTF-8') fails at game startup ====
+
 
+
Edit {{ic|/etc/locale.gen}} in your favourite editor and uncomment the line {{ic|en_US.UTF-8 UTF-8}}. Then run {{ic|# locale-gen}}.
+
 
+
==== Steam complains about direct rendering not available on 64bit systems with NVIDIA driver ====
+
 
+
Make sure you have [multilib] enabled in {{ic|/etc/pacman.conf}}.
+
 
+
Install the following dependencies:
+
* {{Pkg|lib32-nvidia-utils}}
+
* {{Pkg|lib32-nvidia-libgl}}
+
 
+
Steam, being a 32-bit application, requires 32-bit nvidia GL libraries to run. This packages will install the proper 32-bit libGl libraries and symlinks in {{ic|/usr/lib32}} and will replace any existing mesa equivalent symlinks.
+
 
+
=== Launching games with custom commands, such as Bumblebee/Primus ===
+
 
+
Steam has fortunately added support for launching games using your own custom command. To do so, navigate to the Library page, right click on the selected game, click Properties, and Set Launch Options. Steam replaces the tag {{ic|%command%}} with the command it actually wishes to run. For example, to launch Team Fortress 2 with primusrun and at resolution 1920x1080, you would enter:
+
 
+
primusrun %command% -w 1920 -h 1080
+
  
 
If you are running the [[Linux-ck]] kernel, you may have some success in reducing overall latencies and improving performance by launching the game in SCHED_ISO (low latency, avoid choking CPU) via {{Pkg|schedtool}}
 
If you are running the [[Linux-ck]] kernel, you may have some success in reducing overall latencies and improving performance by launching the game in SCHED_ISO (low latency, avoid choking CPU) via {{Pkg|schedtool}}
Line 103: Line 69:
 
  # schedtool -I -e %command% ''other arguments''
 
  # schedtool -I -e %command% ''other arguments''
  
==== Killing standalone compositors when launching games ====
+
Also keep in mind that Steam [http://i.imgur.com/oJcLDBi.png doesn't really care] what you want it to run. By setting {{ic|%command%}} to an environment variable, you can have Steam run whatever you would like. For example, the Launch Option used in the image above:
  
Further to this, utilising the {{ic|%command%}} switch, you can kill standalone compositors (such as Xcompmgr or [[Compton]]) - which can cause lag and tearing in some games on some systems - and relaunch them after the game ends by adding the following to your game's launch options.
+
IGNORE_ME=%command% glxgears
  
  killall compton && %command% && nohup compton &
+
=== Skins for Steam ===
  
Replace {{ic|compton}} in the above command with whatever your compositor is. You can also add -options to {{ic|%command%}} or {{ic|compton}}, of course.
+
{{Note|Using skins that are not up-to-date with the version of the Steam client may cause visual errors.}}
 
+
Steam will latch on to any processes launched after {{ic|%command%}} and your Steam status will show as in game. So in this example, we run the compositor through {{ic|nohup}} so it is not attached to Steam (it will keep running if you close Steam) and follow it with an ampersand so that the line of commands ends, clearing your Steam status.
+
 
+
=== Skins for Steam ===
+
  
 
The Steam interface can be fully customized by copying its various interface files in its skins directory and modifying them.
 
The Steam interface can be fully customized by copying its various interface files in its skins directory and modifying them.
  
==== Steam skin manager ====
+
An extensive list of skins can be found on [http://forums.steampowered.com/forums/showthread.php?t=1161035 Steam's forums].
  
The process of applying a skin to Steam can be greatly simplified using {{AUR|steam-skin-manager}} from the AUR. The package also comes with a hacked version of the Steam launcher which allows the window manager to draw its borders on the Steam window.
+
=== Changing the Steam friends notification placement ===
  
As a result, skins for Steam will come in two flavors, one with and one without window buttons. The skin manager will prompt you whether you use the hacked version or not, and will automatically apply the theme corresponding to your GTK+ theme if it is found. You can of course still apply another skin if you want.
+
{{Style}}
  
The package ships with two themes for the default Ubuntu themes, Ambiance and Radiance. A Faience theme is under development and already has its own package on the AUR {{AUR|steam-skin-faience-git}}.
+
{{Note|A handful of games do not support this, for example this can not work with XCOM: Enemy Unknown.}}
  
== Steam on Wine ==
+
==== Use a skin ====
  
Install {{Pkg|wine}} from the [[multilib]] and follow the instructions provided in the [[Wine|article]].
+
You can create a skin that does nothing but change the notification corner. First you need to create the directories:
  
Install the required Microsoft fonts {{AUR|ttf-microsoft-tahoma}} and {{AUR|ttf-ms-fonts}} from the [[AUR]] or through {{AUR|winetricks-svn}}.
+
  $ mkdir -p $HOME/Top-Right/resource
{{Note|If you have access to Windows discs, you may want to install {{AUR|ttf-ms-win8}} or {{AUR|ttf-win7-fonts}} instead.}}
+
  $ cp -R $HOME/.steam/steam/resource/styles $HOME/Top-Right/resource/
 +
  $ mv $HOME/Top-Right $HOME/.local/share/Steam/skins/
 +
  $ cd .local/share/Steam/skins/
 +
  $ cp -R Top-Right Top-Left && cp -R Top-Right Bottom-Right
  
If you have an old Wine prefix ({{ic|~/.wine}}), you should remove it and let Wine create a new one to avoid problems (you can transfer over anything you want to keep to the new Wine prefix).
+
Then modify the correct files. {{ic|Top-Right/resource/styles/gameoverlay.style}} will change the corner for the in-game overlay whereas {{ic|steam.style}} will change it for your desktop.
  
=== Installation ===
+
Now find the entry: {{ic|Notifications.PanelPosition}} in whichever file you opened and change it to the appropriate value, for example for Top-Right:
  
Download and run the Steam installer from [http://store.steampowered.com/about/ steampowered.com]. It is no longer an {{ic|.exe}} file so you have to start it with {{ic|msiexec}}:
+
  Notifications.PanelPosition    "TopRight"
$ msiexec /i SteamInstall.msi
+
  
=== Starting Steam ===
+
This line will look the same in both files. Repeat the process for all the 3 variants ({{ic|Top-Right}}, {{ic|Top-Left}} and {{ic|Bottom-Left}}) and adjust the corners for the desktop and in-game overlay to your satisfaction for each skin, then save the files.
  
On x86:
+
To finish you will have to select the skin in Steam: ''Settings > Interface'' and ''<default skin>'' in the drop-down menu.
$ wine ~/.wine/drive_c/Program\ Files/Steam/Steam.exe
+
  
On x86_64 (with steam installed to a clean wine prefix):
+
You can use these files across distributions and even between Windows and Linux (OS X has its own entry for the desktop notification placement)
$ wine ~/.wine/drive_c/Program\ Files\ \(x86\)/Steam/Steam.exe
+
  
Alternatively, you may use this method:
+
==== On-the-fly patch ====
$ wine "C:\\Program Files\\Steam\\steam.exe"
+
  
You should consider making an alias to easily start steam (and put it in your shell's rc file), example:
+
This method is more compatible with future updates of Steams since the files in the skins above are updated as part of steam and as such if the original files change, the skin will not follow the graphics update to steam and will have to be re-created every time something like that happens. Doing things this way will also give you the ability to use per-game notification locations as you can run a patch changing the location of the notifications by specifying it in the launch options for games.
alias steam='wine ~/.wine/drive_c/Program\ Files\ \(x86\)/Steam/Steam.exe >/dev/null 2>&1 &'
+
  
{{Note|If you are using an nvidia card through Bumblebee, you should prefix those commands with {{ic|optirun}}.}}
+
Steam updates the files we need to edit everytime it updates (which is everytime it is launched) so the most effective way to do this is patching the file after Steam has already been launched.
  
=== Tips ===
+
First you will need a patch:
  
==== Performance ====
+
{{hc|$HOME/.steam/topright.patch|<nowiki>
 +
--- A/steam/resource/styles/gameoverlay.styles 2013-06-14 23:49:36.000000000 +0000
 +
+++ B/steam/resource/styles/gameoverlay.styles 2014-07-08 23:13:15.255806000 +0000
 +
@@ -7,7 +7,7 @@
 +
mostly_black "0 0 0 240"
 +
semi_black "0 0 0 128"
 +
semi_gray "32 32 32 220"
 +
- Notifications.PanelPosition    "BottomRight"
 +
+ Notifications.PanelPosition    "TopRight"
 +
}
 +
 +
styles
 +
 +
</nowiki>}}
  
Consider disabling wine debugging output by adding this to your shell rc file:
+
{{Note|The patch file should have all above lines, including the newline at the end.}}
export WINEDEBUG=-all
+
or, just add it to your steam alias to only disable it for steam:
+
alias steam='WINEDEBUG=-all wine ~/.wine/drive_c/Program\ Files\ \(x86\)/Steam/Steam.exe >/dev/null 2>&1 &'
+
Additionally, Source games rely on a paged pool memory size specification for audio, and WINE by default does not have this set. To set it:
+
$ wine reg add "HKLM\\System\\CurrentControlSet\\Control\\Session Manager\\Memory Management\\" /v PagedPoolSize /t REG_DWORD /d 402653184 /f
+
  
==== Application launch options ====
+
You can edit the entry and change it between "BottomRight"(default), "TopRight" "TopLeft" and "BottomLeft": the following will assume you used "TopRight" as in the original file.
  
Go to ''Properties > Set Launch Options'', e.g.:
+
Next create an alias in {{ic|$HOME/.bashrc}}:
-console -dxlevel 90 -width 1280 -height 1024
+
* {{ic|console}}
+
: Activate the console in the application to change detailed applications settings.
+
* {{ic|dxlevel}}
+
: Set the application's DirectX level, e.g. 90 for DirectX Version 9.0. It is recommended to use the video card's DirectX version to prevent crashes. See the official Valve Software wiki http://developer.valvesoftware.com/wiki/DirectX_Versions for details.
+
* {{ic|width}} and {{ic|height}}
+
: Set the screen resolution. In some cases the graphic settings are not saved in the application and the applications always starts in the default resolution.
+
Please refer to http://developer.valvesoftware.com/wiki/Launch_options for a complete list of launch options.
+
  
==== Using a pre-existing Steam install ====
+
  alias steam_topright='pushd $HOME/.steam/ && patch -p1 -f -r - --no-backup-if-mismatch < topright.patch && popd'
  
If you have a shared drive with Windows, or already have a Steam installation somewhere else, you can simply symlink the Steam directory to {{ic|~/.wine/drive_c/Program Files/Steam/}} . However, be sure to do '''all''' the previous steps in this wiki. Confirm Steam launches and logs into your account, ''then'' do this:
+
Log out and back in to refresh the aliases. Launch Steam and wait for it to fully load, then run the alias
  
$ cd ~/.wine/drive_c/Program\ Files/
+
   $ steam_topright
$ mv Steam/ Steam.backup/   (or you can just delete the directory)
+
$ ln -s /mnt/windows_partition/Program\ Files/Steam/
+
  
{{Note|
+
And most games you launch after this will have their notification in the upper right corner.
* If you have trouble starting Steam after symlinking the entire Steam folder, try linking only the {{ic|steamapps}} subdirectory in your existing wine steam folder instead.
+
* If you still have trouble starting games, use {{ic|# mount --bind /path/to/SteamApps ~/.local/share/Steam/SteamApps -ouser&#61;your-user-name }}, this is the only thing that worked for me with {{ic|TF2}}.
+
}}
+
  
==== Running Steam in a second X server ====
+
You can also duplicate the patch and make more aliases for the other corners if you do not want all games to use the same corner so you can switch back.
  
Assuming you are using the script above to start Steam, make a new script, called {{ic|x.steam.sh}}. You should run this when you want to start Steam in a new X server, and {{ic|steam.sh}} if you want Steam to start in the current X server.
+
To automate the process you will need a script file as steam launch options cannot read your aliases. The location and name of the file could for example be '''$HOME/.scripts/steam_topright.sh''', and assuming that is the path you used, it needs to be executable:
  
If due to misconfiguration a black screen is shown, you could always close down the second X server by pressing {{Keypress|Ctrl+Alt+Backspace}}.
+
  $ chmod +755 $HOME/.scripts/steam_topright.sh
  
{{bc|1=
+
The contents of the file should be the following:
#!/bin/bash
+
  
DISPLAY=:1.0
+
  #!/bin/sh
 +
  pushd $HOME/.steam/ && patch -p1 -f -r - --no-backup-if-mismatch < topright.patch && popd
  
xinit $HOME/steam.sh $* -- :1
+
And the launch options should be something like the following.
}}
+
  
Now you can use {{Keypress|Ctrl+Alt+F7}} to get to your first X server with your normal desktop, and {{Keypress|Ctrl+Alt+F8}} to go back to your game.  
+
  $HOME/.scripts/steam_topright.sh && %command%
  
Because the second X server is ''only'' running the game and the first X server with all your programs is backgrounded, performance should increase. In addition, it is much more convenient to switch X servers while in game to access other resources, rather than having to exit the game completely or {{Keypress|Alt+Tab}} out. Finally, it is useful for when Steam or WINE goes haywire and leaves a bunch of processes in memory after Steam crashes. Simply {{Keypress|Ctrl+Alt+Backspace}} on the second X server to kill that X and all processes on that desktop will terminate as well.  
+
There is another file in the same folder as '''gameoverlay.style''' folder called '''steam.style''' which has an entry with the exact same function as the file we patched and will change the notification corner for the desktop only (not in-game), but for editing this file to actually work it has to be set before steam is launched and the folder set to read-only so steam cannot re-write the file. Therefore the only two ways to modify that file is to make the directory read only so steam cannot change it when it is launched (can break updates) or making a skin like in method 1.
  
'''If you get errors that look like "Xlib: connection to ":1.0" refused by server" when starting the second X''': You will need to adjust your X permissions.
+
=== Silent Mode ===
  
'''If you lose the ability to use the keyboard while using Steam''': This is an odd bug that does not happen with other games. A solution is to use a WM in the second X as well. Thankfully, you do not need to run a large WM. Openbox and icewm have been confirmed to fix this bug (evilwm, pekwm, lwm ''do not'' work), but the icewm taskbar shows up on the bottom of the game, thus it's recommended to use [[Openbox]]. Install {{Pkg|openbox}} from the [[official repositories]], then add {{ic|openbox &}} to the top of your {{ic|steam.sh}} file. Note you can run other programs (ex. Teamspeak &) or set X settings (ex. xset, xmodmap) before the WINE call as well.
+
To stop the main window from showing at startup, use the {{ic|-silent}} option:
  
==== Steam links in Firefox, Chrome, etc ====
+
$ steam -silent
  
To make {{ic|steam://}} urls in your browser connect with Steam in Wine, there are several things you can do. One involves making steam url-handler keys in gconf, another involves making protocol files for KDE, others involve tinkering with desktop files or the Local State file for chromium. These seem to only work in firefox or under certain desktop configurations. One way to do it that works more globally is using mimeo, a tool made by Xyne (an Arch TU) which follows. For another working and less invasive (but firefox-only) way, see the first post [http://ubuntuforums.org/showthread.php?t=433548 here] .
+
{{Tip|This option can be added to a [[desktop entry]].}}
  
* Make {{ic| /usr/bin/steam}} with your favorite editor and paste:
+
=== Streaming server ===
  
{{bc|
+
See https://steamcommunity.com/sharedfiles/filedetails/?id=680514371
#!/bin/sh
+
#
+
# Steam wrapper script
+
#
+
exec wine "c:\\program files\\steam\\steam.exe" "$@"
+
}}
+
 
+
* Make it executable:
+
 
+
# chmod +x /usr/bin/steam
+
 
+
* Install {{AUR|mimeo}} and {{AUR|xdg-utils-mimeo}} from AUR. You will need to replace the existing {{Pkg|xdg-utils}} if installed. In XFCE, you will also need {{Pkg|xorg-utils}}.
+
 
+
* Create {{ic|~/.config/mimeo.conf}} with your favorite editor and paste:
+
 
+
{{bc|
+
/usr/bin/steam %u
+
  ^steam://
+
}}
+
 
+
* Lastly, open {{ic|/usr/bin/xdg-open}} in your favorite editor. Go to the {{ic|detectDE()}} section and change it to look as follows:
+
 
+
{{bc|<nowiki>
+
detectDE()
+
{
+
    #if [ x"$KDE_FULL_SESSION" = x"true" ]; then DE=kde;
+
    #elif [ x"$GNOME_DESKTOP_SESSION_ID" != x"" ]; then DE=gnome;
+
    #elif $(dbus-send --print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.GetNameOwner string:org.gnome.SessionManager > /dev/null 2>&1) ; then DE=gnome;
+
    #elif xprop -root _DT_SAVE_MODE 2> /dev/null | grep ' = \"xfce4\"$' >/dev/null 2>&1; then DE=xfce;
+
    #elif [ x"$DESKTOP_SESSION" == x"LXDE" ]; then DE=lxde;
+
    #else DE=""
+
    #fi
+
    DE=""
+
}
+
</nowiki>}}
+
 
+
* Restart the browser and you should be good to go. In Chromium, you cannot enter a {{ic|steam://}} link in the url box like you can with Firefox. The forum link above has a {{ic|steam://open/friends}} link to try if needed.
+
 
+
{{Note|
+
* If you have any problems with file associations after doing this, simply revert to regular xdg-utils and undo your changes to {{ic|/usr/bin/xdg-open}}.
+
* Those on other distributions that stumble upon this page, see the link above for firefox specific instructions. No easy way to get it working on Chromium on other distros exists.
+
}}
+
  
==== No text rendered problem ====
+
== Troubleshooting ==
  
If there is no text/font rendered when starting steam you should try to start steam with the parameter {{ic|-no-dwrite}}. Read more in [https://bbs.archlinux.org/viewtopic.php?id=146223 the forum thread about it.]
+
See [[Steam/Troubleshooting]].
{{bc|wine ~/.wine/drive_c/Program\ Files\ \(x86\)/Steam/Steam.exe -no-dwrite}}
+
  
 
== See also ==
 
== See also ==
  
* https://wiki.gentoo.org/wiki/Steam
+
* [https://wiki.gentoo.org/wiki/Steam Steam] at Gentoo wiki
* [http://appdb.winehq.org/objectManager.php?sClass=version&iId=19444 Wine Application Database]
+
* [http://pcgamingwiki.com/wiki/The_Big_List_of_DRM-Free_Games_on_Steam The Big List of DRM-Free Games on Steam] at PCGamingWiki
 +
* [http://steam.wikia.com/wiki/List_of_DRM-free_games List of DRM-free games] at wikia

Latest revision as of 23:03, 7 August 2016

From Wikipedia:

Steam is a digital distribution, digital rights management, multiplayer and communications platform developed by Valve Corporation. It is used to distribute games and related media online, from small independent developers to larger software houses.

Steam is best known as the platform needed to play Source Engine games (e.g. Half-Life 2, Counter-Strike). Today it offers many games from many other developers.

Installation

Note:

Install the steam package.

Steam is not supported on this distribution. As such some fixes are needed on the users part to get things functioning properly:

Usage

Big Picture Mode

To start Steam in Big Picture Mode from a Display manager, create a /usr/share/xsessions/steam-big-picture.desktop file with the following contents:

/usr/share/xsessions/steam-big-picture.desktop
[Desktop Entry]
Name=Steam Big Picture Mode
Comment=Start Steam in Big Picture Mode
Exec=/usr/bin/steam -bigpicture
TryExec=/usr/bin/steam
Icon=
Type=Application

Steam runtime

See Steam/Troubleshooting#Steam runtime issues.

Tips and tricks

Launching games with custom commands

Tango-edit-clear.pngThis article or section needs language, wiki syntax or style improvements.Tango-edit-clear.png

Reason: please use the first argument of the template to provide a brief explanation. (Discuss in Talk:Steam#)

Steam has fortunately added support for launching games using your own custom command. To do so, navigate to the Library page, right click on the selected game, click Properties, and Set Launch Options. Steam replaces the tag %command% with the command it actually wishes to run. For example, to launch Team Fortress 2 with primusrun and at resolution 1920x1080, you would enter:

primusrun %command% -w 1920 -h 1080

On some systems optirun gives better performances than primusrun, however some games may crash shortly after the launch. This may be fixed preloading the correct version of libGL. Use:

locate libGL

to find out the available implementations. For a 64 bits game you may want to preload the nvidia 64 bits libGL, then use the launch command:

LD_PRELOAD=/usr/lib/nvidia/libGL.so optirun %command%

If you are running the Linux-ck kernel, you may have some success in reducing overall latencies and improving performance by launching the game in SCHED_ISO (low latency, avoid choking CPU) via schedtool

# schedtool -I -e %command% other arguments

Also keep in mind that Steam doesn't really care what you want it to run. By setting %command% to an environment variable, you can have Steam run whatever you would like. For example, the Launch Option used in the image above:

IGNORE_ME=%command% glxgears

Skins for Steam

Note: Using skins that are not up-to-date with the version of the Steam client may cause visual errors.

The Steam interface can be fully customized by copying its various interface files in its skins directory and modifying them.

An extensive list of skins can be found on Steam's forums.

Changing the Steam friends notification placement

Tango-edit-clear.pngThis article or section needs language, wiki syntax or style improvements.Tango-edit-clear.png

Reason: please use the first argument of the template to provide a brief explanation. (Discuss in Talk:Steam#)
Note: A handful of games do not support this, for example this can not work with XCOM: Enemy Unknown.

Use a skin

You can create a skin that does nothing but change the notification corner. First you need to create the directories:

 $ mkdir -p $HOME/Top-Right/resource
 $ cp -R $HOME/.steam/steam/resource/styles $HOME/Top-Right/resource/
 $ mv $HOME/Top-Right $HOME/.local/share/Steam/skins/
 $ cd .local/share/Steam/skins/
 $ cp -R Top-Right Top-Left && cp -R Top-Right Bottom-Right

Then modify the correct files. Top-Right/resource/styles/gameoverlay.style will change the corner for the in-game overlay whereas steam.style will change it for your desktop.

Now find the entry: Notifications.PanelPosition in whichever file you opened and change it to the appropriate value, for example for Top-Right:

 Notifications.PanelPosition     "TopRight"

This line will look the same in both files. Repeat the process for all the 3 variants (Top-Right, Top-Left and Bottom-Left) and adjust the corners for the desktop and in-game overlay to your satisfaction for each skin, then save the files.

To finish you will have to select the skin in Steam: Settings > Interface and <default skin> in the drop-down menu.

You can use these files across distributions and even between Windows and Linux (OS X has its own entry for the desktop notification placement)

On-the-fly patch

This method is more compatible with future updates of Steams since the files in the skins above are updated as part of steam and as such if the original files change, the skin will not follow the graphics update to steam and will have to be re-created every time something like that happens. Doing things this way will also give you the ability to use per-game notification locations as you can run a patch changing the location of the notifications by specifying it in the launch options for games.

Steam updates the files we need to edit everytime it updates (which is everytime it is launched) so the most effective way to do this is patching the file after Steam has already been launched.

First you will need a patch:

$HOME/.steam/topright.patch
--- A/steam/resource/styles/gameoverlay.styles	2013-06-14 23:49:36.000000000 +0000
+++ B/steam/resource/styles/gameoverlay.styles	2014-07-08 23:13:15.255806000 +0000
@@ -7,7 +7,7 @@
 		mostly_black "0 0 0 240"
 		semi_black "0 0 0 128"
 		semi_gray "32 32 32 220"
-		Notifications.PanelPosition     "BottomRight"
+		Notifications.PanelPosition     "TopRight"
 	}
 	
 	styles
 
Note: The patch file should have all above lines, including the newline at the end.

You can edit the entry and change it between "BottomRight"(default), "TopRight" "TopLeft" and "BottomLeft": the following will assume you used "TopRight" as in the original file.

Next create an alias in $HOME/.bashrc:

 alias steam_topright='pushd $HOME/.steam/ && patch -p1 -f -r - --no-backup-if-mismatch < topright.patch && popd'

Log out and back in to refresh the aliases. Launch Steam and wait for it to fully load, then run the alias

 $ steam_topright

And most games you launch after this will have their notification in the upper right corner.

You can also duplicate the patch and make more aliases for the other corners if you do not want all games to use the same corner so you can switch back.

To automate the process you will need a script file as steam launch options cannot read your aliases. The location and name of the file could for example be $HOME/.scripts/steam_topright.sh, and assuming that is the path you used, it needs to be executable:

 $ chmod +755 $HOME/.scripts/steam_topright.sh

The contents of the file should be the following:

 #!/bin/sh
 pushd $HOME/.steam/ && patch -p1 -f -r - --no-backup-if-mismatch < topright.patch && popd

And the launch options should be something like the following.

 $HOME/.scripts/steam_topright.sh && %command%

There is another file in the same folder as gameoverlay.style folder called steam.style which has an entry with the exact same function as the file we patched and will change the notification corner for the desktop only (not in-game), but for editing this file to actually work it has to be set before steam is launched and the folder set to read-only so steam cannot re-write the file. Therefore the only two ways to modify that file is to make the directory read only so steam cannot change it when it is launched (can break updates) or making a skin like in method 1.

Silent Mode

To stop the main window from showing at startup, use the -silent option:

$ steam -silent
Tip: This option can be added to a desktop entry.

Streaming server

See https://steamcommunity.com/sharedfiles/filedetails/?id=680514371

Troubleshooting

See Steam/Troubleshooting.

See also