<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.alpinelinux.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Moon</id>
	<title>Alpine Linux - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.alpinelinux.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Moon"/>
	<link rel="alternate" type="text/html" href="https://wiki.alpinelinux.org/wiki/Special:Contributions/Moon"/>
	<updated>2026-05-09T19:41:24Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.40.0</generator>
	<entry>
		<id>https://wiki.alpinelinux.org/w/index.php?title=Steam&amp;diff=31274</id>
		<title>Steam</title>
		<link rel="alternate" type="text/html" href="https://wiki.alpinelinux.org/w/index.php?title=Steam&amp;diff=31274"/>
		<updated>2025-10-25T07:21:33Z</updated>

		<summary type="html">&lt;p&gt;Moon: Fixed grammar error&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page explains how to run [https://store.steampowered.com/about/ Steam], a popular game distribution platform by Valve on Alpine Linux. Steam requires glibc to run, and thus won&#039;t run natively on Alpine Linux. The simplest approach is to run it as [[Flatpak]]. Other workarounds involve using a virtual machine, a chroot or a container. It is theoretically possible to run the windows version of Steam using {{Pkg|wine}}.&lt;br /&gt;
&lt;br /&gt;
== Installation via Flatpak ==&lt;br /&gt;
&lt;br /&gt;
# Follow the [[Flatpak#Installing_Flatpak|Flatpak]] wiki page and ensure that [[Flatpak#Installing_Flatpak|Flathub repository]] is enabled. &lt;br /&gt;
# Install the Steam flatpak package from Flathub.{{Cmd|$ flatpak --user install com.valvesoftware.Steam}}&lt;br /&gt;
# After installation Steam can be started either using its .desktop file or from the command line: {{Cmd|$ flatpak run com.valvesoftware.Steam}}&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
=== My controllers aren&#039;t detected ===&lt;br /&gt;
&lt;br /&gt;
By default Steam doesn&#039;t have permission to read your controllers.&lt;br /&gt;
This can be fixed by installing an [[udev]] rule from the official Steam package, but the udev rules are also available as an Alpine package.&lt;br /&gt;
&lt;br /&gt;
  # apk add {{pkg|steam-devices|arch=x86_64}}&lt;br /&gt;
&lt;br /&gt;
These udev rules rely on the &amp;lt;code&amp;gt;TAG+=&amp;quot;uaccess&amp;quot;&amp;lt;/code&amp;gt;, and are therefore only expected to work reliably when using [[Elogind]].&lt;br /&gt;
&lt;br /&gt;
=== SteamVR won&#039;t launch ===&lt;br /&gt;
&lt;br /&gt;
Out of the box SteamVR might not be able to launch and give you various errors. Steam tries to fix this itself by setting the right capabilities on the SteamVR binary, but this doesn&#039;t work in the Flatpak. Instead we&#039;ll have do it manually.&lt;br /&gt;
&lt;br /&gt;
  # setcap CAP_SYS_NICE+ep ~/.var/app/com.valvesoftware.Steam/data/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher&lt;br /&gt;
&lt;br /&gt;
Then restart Steam.&lt;br /&gt;
&lt;br /&gt;
There is an issue for this [https://github.com/flathub/com.valvesoftware.Steam/issues/636#issuecomment-779763326 on the Flathub repository].&lt;br /&gt;
&lt;br /&gt;
=== Steam - Error: OpenGL GLX extension not supported by display ===&lt;br /&gt;
&lt;br /&gt;
Add the Mesa gallium driver and reboot your system.&lt;br /&gt;
&lt;br /&gt;
 # apk add {{pkg|mesa-dri-gallium|arch=x86_64}}&lt;br /&gt;
&lt;br /&gt;
=== eventfd: Too many open files ===&lt;br /&gt;
&lt;br /&gt;
Due to a low amount of allowed open file descriptors, Proton games may crash shortly after launching. This can be worked around by disabling esync but many games will perform measurably worse without it. Instead, user limits should be increased. In order to do this, you will need [[PAM]] and a PAM enabled login.&lt;br /&gt;
&lt;br /&gt;
Add the following to &amp;lt;code&amp;gt;/etc/security/limits.conf&amp;lt;/code&amp;gt;:&lt;br /&gt;
 @users hard nofile 524288&lt;br /&gt;
&lt;br /&gt;
{{Note|Although you should already belong to the users group, you can run &amp;lt;code&amp;gt;groups&amp;lt;/code&amp;gt; to check.}}&lt;br /&gt;
&lt;br /&gt;
Reboot and run &amp;lt;code&amp;gt;ulimit -Hn&amp;lt;/code&amp;gt; to verify the new limits are applied.&lt;br /&gt;
&lt;br /&gt;
=== dbus-launch: no such file or directory ===&lt;br /&gt;
&lt;br /&gt;
Set up [[D-Bus|dbus]] for your session.&lt;br /&gt;
&lt;br /&gt;
=== Steam games launched via Proton crash before creating a window ===&lt;br /&gt;
&lt;br /&gt;
Instead of just using the in-Steam menu to install and select a Proton version, try installing the flatpak community build for Proton onto your system. There are several versions, depending on your desired stability, and the experimental version available in Flathub is called &amp;quot;com.valvesoftware.Steam.CompatibilityTool.Proton-Exp&amp;quot;. After you install your chosen version, go into Steam to specify compatibility tool for a game as usual. The installed community build will now be an option. Select that and try launching the game again.&lt;br /&gt;
&lt;br /&gt;
As your last resort, you can try installing [https://github.com/GloriousEggroll/proton-ge-custom proton-ge-custom], but please note that in order for this to be even detected by Steam, you will need to install Steam via Nix due to high level of isolation that Flatpaks utilize. This can however come at the expense of your [https://tosdr.org/en/service/180 privacy].&lt;br /&gt;
&lt;br /&gt;
=== Steam spams dmesg with x86/split lock detection entries ===&lt;br /&gt;
&lt;br /&gt;
Add the below line to {{path|/etc/sysctl.conf}}:&lt;br /&gt;
  kernel.split_lock_mitigate = 0&lt;br /&gt;
&lt;br /&gt;
=== Steam hangs on start with a steamwebhelper popup ===&lt;br /&gt;
&lt;br /&gt;
If this happens and {{path|~/.var/app/com.valvesoftware.Steam/.local/share/Steam/logs/steamwebhelper.log}} says that you are missing X server or &amp;lt;var&amp;gt;DISPLAY&amp;lt;/var&amp;gt;, it means your &amp;lt;var&amp;gt;DISPLAY&amp;lt;/var&amp;gt; is not present in the activation environment. For more information please see https://github.com/ValveSoftware/steam-for-linux/issues/10554 &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[Sway]]&#039;&#039;&#039;: Go into your sway config file and ensure that &amp;lt;var&amp;gt;DISPLAY&amp;lt;/var&amp;gt; appears in the {{ic|dbus-update-activation environment}} line, as well as the [https://github.com/swaywm/sway/wiki#systemd-and-dbus-activation-environments others stated here], then restart:&lt;br /&gt;
&amp;lt;pre&amp;gt;exec dbus-update-activation-environment WAYLAND_DISPLAY DISPLAY XDG_CURRENT_DESKTOP=sway SWAYSOCK I3SOCK XCURSOR_SIZE XCURSOR_THEME&amp;lt;/pre&amp;gt;&lt;br /&gt;
For more information about this line, please see the [[Sway|Alpine Linux wiki entry]] on Sway&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hyprland&#039;&#039;&#039;: Add an exec-once to the configuration file at {{path|~/.config/hypr/hyprland}} to set &amp;lt;var&amp;gt;DISPLAY&amp;lt;/var&amp;gt;. Similarly to Sway you may already have a line that sets other variables. If so, add &amp;lt;var&amp;gt;DISPLAY&amp;lt;/var&amp;gt; to the line. The line should look similar to this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;exec-once = dbus-update-activation-environment DISPLAY&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== See Also ==&lt;br /&gt;
* [[Gaming on Alpine|Gaming on Alpine Linux]]&lt;br /&gt;
* [[Flatpak]]&lt;br /&gt;
* [https://wiki.postmarketos.org/wiki/Steam Steam on postmarketOS]&lt;br /&gt;
&lt;br /&gt;
[[category:Gaming]]&lt;/div&gt;</summary>
		<author><name>Moon</name></author>
	</entry>
</feed>