From ArchWiki
(Redirected from Steam runtime)
  1. Make sure that you have followed Steam#Installation.
  2. If the Steam client / a game is not starting and/or you have error message about a library, read #Steam runtime and see #Debugging shared libraries.
  3. If the issue is related to networking, make sure that you have forwarded the required ports for Steam.
  4. If the issue is about a game, consult Steam/Game-specific troubleshooting.

Steam runtime

Steam for Linux ships with its own set of libraries called the Steam runtime. By default Steam launches all Steam Applications within the runtime environment. The Steam runtime is located at ~/.steam/root/ubuntu12_32/steam-runtime/.

If you mix the Steam runtime libraries with system libraries you will run into binary incompatibility issues, see steam-for-linux issue #4768. Binary incompatibility can lead to the Steam client and games not starting (manifesting as a crash, as hanging or silently returning), audio issues and various other problems.

The steam package offers two ways to launch Steam:

  • steam-runtime (alias steam), which overrides runtime libraries known to cause problems via the LD_PRELOAD environment variable (see
  • /usr/lib/steam/steam, the default Steam launch script

As the Steam runtime libraries are older they can lack newer features, e.g. the OpenAL version of the Steam runtime lacks HRTF and surround71 support.

Steam native runtime

Warning: Using the Steam native runtime is not recommended as it might break some games due to binary incompatibility and it might miss some libraries present in the Steam runtime.

The steam-native-runtime package depends on over 130 packages to pose a native replacement of the Steam runtime, some games may however still require additional packages.

This package provides the steam-native script, which launches Steam with the STEAM_RUNTIME=0 environment variable making it ignore its runtime and only use system libraries.

You can also use the Steam native runtime without steam-native-runtime by manually installing just the packages you need. See #Finding missing runtime libraries.

Debugging shared libraries

To see the shared libraries required by a program or a shared library run the ldd command on it, see ldd(1). The LD_LIBRARY_PATH and LD_PRELOAD environment variables can alter which shared libraries are loaded, see To correctly debug a program or shared library it is therefore important that these environment variables in your debug environment match the environment you wish to debug.

If you figure out a missing library you can use pacman or pkgfile to search for packages that contain the missing library.

Finding missing game libraries

If a game fails to start, a possible reason is that it is missing required libraries. You can find out what libraries it requests by running ldd game_executable. game_executable is likely located somewhere in ~/.steam/root/steamapps/common/. Please note that most of these "missing" libraries are actually already included with Steam, and do not need to be installed globally.

Finding missing runtime libraries

If individual games or Steam itself is failing to launch when using steam-native you are probably missing libraries. To find the required libraries run:

$ cd ~/.steam/root/ubuntu12_32
$ file * | grep ELF | cut -d: -f1 | LD_LIBRARY_PATH=. xargs ldd | grep 'not found' | sort | uniq

Alternatively, run Steam with steam-runtime and use the following command to see which non-system libraries Steam is using (not all of these are part of the Steam runtime):

$ for i in $(pgrep steam); do sed '/\.local/!d;s/.*  //g' /proc/$i/maps; done | sort | uniq

Debugging Steam

This article or section is out of date.

Reason: Steam no longer redirects stdout and stderr to /tmp/dumps/USER_stdout.txt by default. See: steam-for-linux issue 7114 A similar effect can be achieved by starting steam with steam 2>&1 (Discuss in Talk:Steam/Troubleshooting)

The Steam launcher redirects its stdout and stderr to /tmp/dumps/USER_stdout.txt. This means you do not have to run Steam from the command-line to see that output.

It is possible to debug Steam to gain more information which could be useful to find out why something does not work.

You can set DEBUGGER environment variable with one of gdb, cgdb, valgrind, callgrind, strace and then start steam.

For example with gdb

$ DEBUGGER=gdb steam

gdb will open, then type run which will start steam and once crash happens you can type backtrace to see call stack.

Runtime issues

'GLBCXX_3.X.XX' not found when using Bumblebee

This error is likely caused because Steam packages its own out of date See #Finding missing runtime libraries about working around the bad library. See also steam-for-linux issue 3773.

Steam>Warning: failed to init SDL thread priority manager: SDL not found

Solution: install the lib32-sdl2 package.

Game crashes immediately

This is likely due to #Steam runtime issues, see #Debugging shared libraries.

Disabling the in-game Steam Overlay in the game properties might help.

And finally, if those do not work, you should check Steam's output for any error from the game. You may encounter the following:

  • munmap_chunk(): invalid pointer
  • free(): invalid pointer

In these cases, try replacing the file from the problematic game with one of a game that works. This error usually happens for games that were not updated recently when Steam runtime is disabled. This error has been encountered with AYIM, Bastion and Monaco.

If the game crashes with terminate called after throwing an instance of 'dxvk::DxvkError' it's likely that conflicting versions of vulkan are installed. lib32-amdvlk, lib32-vulkan-intel and Nvidia vulkan drivers are mutually exclusive. This is solved by uninstalling the unneeded driver. To obtain information about the chipset vendor one can run:

# lshw -C display | grep vendor

To get a list of installed packages

# pacman -Qs vulkan

Game and Steam crashes after game start

If the following error is output:

failed to dlopen error=/home/GAMEPATH/bin/ version `GCC_7.0.0' not found (required by /usr/lib32/

moving the incompatible lib can be a workaround.

mv .local/share/Steam/steamapps/common/GAME/bin/ .local/share/Steam/steamapps/common/GAME/bin/

Some games freeze at start when in focus

A combination of using ForceFullCompositionPipeline, specific Proton versions and Nvidia driver version 535 is known to freeze some games using DXVK/Vulkan at launch under Xorg. Using Alt+Tab allows bringing Steam in focus, and the game seems to run properly in the background. Solution: disable ForceFullCompositionPipeline or downgrade Nvidia drivers.

Version `CURL_OPENSSL_3` not found

This is because curl alone is not compatible with previous versions. You need to install the compatibility libraries:

One of the following messages may show up:

# Nuclear Throne
./nuclearthrone: /usr/lib32/ version `CURL_OPENSSL_3' not found (required by ./nuclearthrone)

# Devil Daggers
./devildaggers: /usr/lib/ version `CURL_OPENSSL_3' not found (required by ./devildaggers)

You need to install either libcurl-compat or lib32-libcurl-compat and link the compatibility library manually:

# Nuclear Throne
$ ln -s /usr/lib32/ "LIBRARY/steamapps/common/Nuclear Throne/lib/"

# Devil Daggers
$ ln -s /usr/lib/ LIBRARY/steamapps/common/devildaggers/lib64/

Steam webview/game browser not working in native runtime (Black screen)

Since the new Steam Friends UI update, the client webview is not working correctly with the native-runtime.

./steamwebhelper: error while loading shared libraries: cannot open shared object file: No such file or directory

It can be solved preloading glib libraries; Those do not require libpcre and selinux to work.

$ LD_PRELOAD="/usr/lib/ /usr/lib/" steam-native

Alternatively, you may create a symbolic link to the native Arch libpcre library.

# ln -s /usr/lib/ /usr/lib64/

Since update from around 3/3/2022, there are some reports of black screen still persisting after applying above workaround.

The workaround for now is to run Steam with the -no-cef-sandbox option. More information can be found in Github Steam-For-Linux repository Issue #8451 and #8420.

Steam: An X Error occurred

When using an NVidia GPU and proprietary drivers, Steam may fail to start and (if run from the terminal) produce errors of the form:

Steam: An X Error occurred
X Error of failed request:  GLXBadContext
Major opcode of failed request:  151
Serial number of failed request:  51
xerror_handler: X failed, continuing

Install the package lib32-nvidia-utils (or lib32-nvidia-390xx-utilsAUR if using an old GPU).

If lib32-nvidia-utils is installed, ensure that the package version matches nvidia with

# pacman -Qs nvidia

You may need to change which mirrors you are using to install the drivers if they do not match.

If you are using AMD, have enabled 10-bit color depth, and are having this problem. You will likely need to disable 10-bit color depth.

Another issue that causes this error message can be solved by removing the config.vdf file:

$ rm ~/.local/share/Steam/config/config.vdf

Steam: Compatibility tool configuration failed

If you are trying to run a native game using Proton but get a Steam compatibility tool error immediately after starting the game, you might have to reinstall the runtime.

  1. Navigate to your Steam library.
  2. In the dropdown above your game list check the Tools option to make them visible.
  3. Search for Proton, right click on each installed tool, visit Properties, open the Local files tab and click Verify integrity of tool files for each entry.
  4. Search for Steam Linux Runtime and repeat the same procedure. If none are available, install the latest Steam Linux Runtime - Soldier.

Game starts but closes immediately with custom kernel

Make sure that you have enabled User namespace in General setup -> Namespaces support.

Steam Library won't start

Opening the steam library either displays nothing, or a brief splash, but no window appears. Running /usr/bin/steam-runtime in a terminal window gives this error:

Assertion 'device' failed at src/libsystemd/sd-device/device-private.c:103, function device_get_tags_generation(). Aborting.

Bugs reports are filed: #79006

See also discussion at: Steam failing to launch since systemd 253.5-2 update

A workaround is to install lib32-libnm.

Graphical issues

Blurry text and graphics with Xwayland and HiDPI

When Steam runs as an Xwayland client under a compositor that uses HiDPI scaling, you may find that Steam and games are rendered at half resolution and then upscaled to fit the HiDPI screen. This results in blurry graphics.

One option is to run Steam under a nested gamescope compositor. Install the gamescope package:

$ gamescope -f -m 1 -e -- steam -gamepadui

This runs Steam in "big picture" mode (actually Steam Deck mode), in fullscreen, without scaling (i.e. at full resolution). The same settings should also propagate to games run under Steam.

Audio issues

If the sections below do not address the issue, using the #Steam native runtime might help.

Configure PulseAudio

Games that explicitly depend on ALSA can break PulseAudio. Follow the directions for PulseAudio#ALSA to make these games use PulseAudio instead.

No audio or 756 Segmentation fault

First #Configure PulseAudio and see if that resolves the issue. If you do not have audio in the videos which play within the Steam client, it is possible that the ALSA libraries packaged with Steam are not working.

Attempting to playback a video within the steam client results in an error similar to:

ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave

A workaround is to rename or delete the alsa-lib folder and the* files. They can be found at:


An alternative workaround is to add the* library to the LD_PRELOAD environment variable:

$ LD_PRELOAD='/usr/$LIB/ '${LD_PRELOAD} steam

If audio still will not work, adding the Pulseaudio-libs to the LD_PRELOAD variable may help:

$ LD_PRELOAD='/usr/$LIB/ /usr/$LIB/ '${LD_PRELOAD} steam

Be advised that their names may change over time. If so, it is necessary to take a look in


and find the new libraries and their versions.

Bugs reports have been filed: #3376 and #3504

FMOD sound engine

The factual accuracy of this article or section is disputed.

Reason: No source / bug report. (Discuss in Talk:Steam/Troubleshooting)

The FMOD audio middleware package is a bit buggy, and as a result games using it may have sound problems.

It usually occurs when an unused sound device is used as default for ALSA. See Advanced Linux Sound Architecture#Set the default sound card.

Affected games: Hotline Miami, Hotline Miami 2, Transistor

PulseAudio & OpenAL: Audio streams cannot be moved between devices

If you use PulseAudio and cannot move an audio stream between sinks, it might be because recent OpenAL versions default to disallow audio streams from being moved. Try to add the following to your ~/.alsoftrc:


Cracking Microphone in Steam Voice and Games

If you experience cracking with your audio input while using Steam Voice or in games, you can try to launch steam with the environmental variable PULSE_LATENCY_MSEC=30

Steam client issues

Cannot browse filesystem to add a library folder or library folder appears as empty

If the file chooser is empty when trying add a library folder, or if a previously set up folder now appears with 0 games installed, this can be the result of an incorrect timestamp on the root directory or in the library folder. Timestamps can be checked with stat:

$ stat path

If the timestamp is in the future, run

$ touch path

to reinitialize it to the current date, then re-run Steam.

Cannot add library folder because of missing execute permissions

If you add another Steam library folder on another drive, you might get the error message:

New Steam library folder must be on a filesystem mounted with execute permissions

Make sure you are mounting the filesystem with the correct flags in your /etc/fstab, usually by adding exec to the list of mount parameter. The parameter must occur after any user or users parameter since these can imply noexec.

This error might also occur if your library folder does not contain a steamapps directory. Previous versions used SteamApps instead, so ensure the name is fully lowercase.

This error can also occur because of Steam runtime issues and may be fixed following the #Finding missing runtime libraries section or due to no space being left on the device. For debugging purposes it might be useful to run Steam from the console and observe the log.

Unusually slow download speed

If your Steam (games, software…) download speed through the client is unusually slow, but browsing the Steam store and streaming videos is unaffected, installing a DNS cache program, such as dnsmasq can help [1].

Something else that might help would be disabling IPv6. See [2] for more information.

Another potential fix is to disable HTTP2 [3] by creating ~/.steam/steam/steam_dev.cfg with the line

@nClientDownloadEnableHTTP2PlatformLinux 0

Adding the following line to the steam_dev.cfg file to increase the server connections may improve but may also negatively affect speeds

@fDownloadRateImprovementToAddAnotherConnection 1.0

"Needs to be online" error

This article or section is out of date.

Reason: nscd was removed in glibc 2.38-4. (Discuss in Talk:Steam/Troubleshooting)

This article or section needs expansion.

Reason: Unclear why enabling nscd can help (Discuss in Talk:Steam/Troubleshooting#Needs to be online error: Enabling nscd.service)

If the Steam launcher refuses to start and you get an error saying: "Fatal Error: Steam needs to be online to update" while you are online, then there might be issues with name resolving.

Try installing lib32-systemd, lib32-libcurl-compat, nss-mdns, lib32-nss, lib32-glu or lib32-dbus.

This may also be as simple as DNS resolution not correctly working and is not always obvious since modern browsers will use their own DNS servers. Follow Domain name resolution.

Steam may have issues if systemd-resolved is providing DNS resolution. Make sure lib32-systemd is present to resolve this.

If DNS resolution works but the Steam launcher still shows the same error message, enabling DNS caching e.g. via the "Name Service Caching Daemon", nscd.service, has shown to work around this issue.

It is unclear what exactly running nscd does to make it work again though. Please check the talk page for more info.

Steam forgets password

Related: steam-for-linux#5030

Steam for Linux has a bug which causes it to forget the password of some users.

As a workaround, after logging in to Steam, run

# chattr +i ~/.steam/registry.vdf

This will set the file's immutable bit so Steam cannot modify, delete, or rename it and thus not log you out.

Preventing crash memory dumps

Every time Steam crashes, it writes a memory dump to /tmp/dumps/. If Steam falls into a crash loop, the dump files can become quite large. When /tmp is mounted as tmpfs, memory and swap file can be consumed needlessly.

To prevent this, link /tmp/dumps/ to /dev/null:

# ln -s /dev/null /tmp/dumps

Or alternatively, create and modify permissions on /tmp/dumps. Then Steam will be unable to write dump files to the directory.

# mkdir /tmp/dumps
# chmod 600 /tmp/dumps

This also has the added benefit of Steam not uploading these dumps to Valve's servers.

Steam license problem with playing videos

Steam uses Google's Widevine DRM for some videos. If it is not installed you will get the following error:

This video requires a license to play which cannot be retrieved. This may be a temporary network condition. Please restart the video to try again.

To solve this issue follow the Streaming Videos on Steam support page.

No context menu for joining/inviting friends

Since the new Steam Friends UI update, it may be the case that in the right-click menu the entries for "Join Game", "Invite to Game" and "View Game Info" are missing.

In order to fix this, it maybe be necessary to install lsof.

Slow and unresponsive user interface

If you experience extremely slow and sluggish performance when using the Steam client it might help to disable the Enable GPU accelerated rendering in web views option under the Interface tab in the Steam client settings.

The friends list can also cause this problem. Two workarounds are mentioned in

  • Moving the friends list to another monitor [4].
  • Disabling animated avatars. Open your friends list settings (click the gear in the top-right of the list). Set FRIENDS LIST > Enable Animated Avatars & Animated Avatar Frames in your Friends List and Chat > OFF [5].

Steam fails to start correctly

One troubleshooting step is to run

$ steam-runtime --reset

This can fix various issues that come with a broken install.

Missing taskbar menu

If clicking your steam taskbar icon does not give you a menu, it may be necessary to install the libappindicator-gtk2 and lib32-libappindicator-gtk2 packages and restart steam.

"Your browser does not support the minimum set of features required to watch this broadcast" error

See steam-for-linux issue 6780

If you get an error stating "Your browser does not support the minimum set of features required to watch this broadcast" when attempting to watch a stream/broadcast try the following two troubleshooting steps:

  1. Navigate to Community > Broadcasts. If the page displays "Updating Steam" wait a few minutes to see if the process completes and cancel it after a while in case it does not. Now test if you are able to watch broadcasts, e.g. by clicking on one of the ones display under Community > Broadcasts.
  2. Start a broadcast while in Big Picture mode (View > Big Picture Mode). If a broadcast starts fine while in Big Picture mode check if it still works after switching back to the main interface.
  3. Trigger the Steam client to directly unlock H.264 decoding using the following command: steam-runtime steam://unlockh264/. The Steam client should start headless and run the unlock command. Wait a minute to be sure the process completes, then close and relaunch the Steam client.

Using system titlebar and frame

Currently steam client tries to manage its windows itself, but it does it improperly, see steam-for-linux#1040. As a workaround you can use steamwm project. Run steam like this: ./steamwm.cpp steam. Also the project provides a skin that removes unnative control buttons and frame, but leaves default skin decorations.

More selective DPMS inhibition

By default, the Steam client totally disables screensaving when it is running, whether a game is launched or not.

A workaround to this issue is provided by steam-screensaver-fixAUR: run steam-screensaver-fix-native or steam-screensaver-fix-runtime.

This will allow your screen to turn off if Steam is running, but will keep inhibiting the screensaver if a game is launched.

See Issue 5607 at Valve's GitHub for the details.

Steam window does not show on Nvidia GPUs after the June 14, 2023 update

Note: This issue is a recent issue and might be fixed sooner or later making this section obsolete or inaccurate

See steam-for-linux 9577

This issue seems to be caused by an Nvidia driver update that coincided with the release of the new Steam UI to stable channels. Currently there are four ways that appear to work around this issue. The first is to downgrade the Nvidia drivers to 530.41.03 using a tool like downgradeAUR, which should work around the issue until Nvidia or Valve fix this issue. The second workaround is to delete the GLCache directory at ~/.cache/nvidia/GLCache/. After starting Steam, delete that directory using rm -r ~/.config/nvidia/GLCache. After running this command, Steam should appear. A third, temporary workaround is to run the steam --reset command, which resets the steam installation and logs the user out. This should work for one session, or until the system is rebooted. A fourth workaround is to revert to the old UI using steam -vgui. This UI may get broken as time goes, for now only the friends menu seems to be broken, but more functionality may be broken as time goes on.

When downgrading, ensure the same version is used for all components (kernel module nvidia/nvidia-dkms, 64bit userspace nvidia-utils and 32bit userspace lib32-nvidia-utils) and you have booted into the updated your initrd.

Enabling fractional scaling

If the text and icons in the Steam client window are too small to read on your display, it may be beneficial to enable fractional scaling. The Steam client has a settings option to enable it, at Settings > Interface > Scale text and icons to match monitor settings. Enabling this should tell the client to use the system's fractional scaling settings.

However, if this does not automatically work, there is a command line parameter to force fractional scaling. Running Steam with the -forcedesktopscaling 1.5 flag will scale the client to 1.5x size. This value can be changed to the correct scaling factor for your monitor. If you wish to make this change permanent, you can edit the Exec field in the steam.desktop file.

Steam Beta crashes

If you are using Steam Beta (which can be confirmed with the presence of You are in the 'publicbeta' client beta in the logs) and encounter breaking bugs, manually switch back to non-Beta:

$ rm -f ~/.local/share/Steam/package/beta

Report the issue after looking for duplicates at

Steam Remote Play issues

See Steam#Steam Remote Play.

Remote Play does not work from Arch Linux host to Arch Linux guest

Chances are you are missing lib32-libcanberra. Once you install that, it should work as expected.

With that, Steam should no longer crash when trying to launch a game through Remote Play.

Hardware decoding not available

Remote Play hardware decoding uses vaapi, but steam requires libva2_32bit, where as Arch defaults to 64bit.

As a basic set, this is libva and lib32-libva. Intel graphics users will also require both libva-intel-driver and lib32-libva-intel-driver.

For more information about vaapi see hardware video acceleration.

It may also be necessary to remove the steam runtime version of libva, in order to force it to use system libraries. The current library in use can be found by using:

$ pgrep steam | xargs -I {} cat /proc/{}/maps | grep libva

If this shows locations in ~/.local/Share/steam steam is still using its packaged version of libva. This can be rectified by deleting the libva library files at ~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/libva*, so that steam falls back to the system libraries.

Big Picture Mode minimizes itself after losing focus

This can occur when you play a game via Remote Play or if you have a multi-monitor setup and move the mouse outside of BPM's window. To prevent this, set the SDL_VIDEO_MINIMIZE_ON_FOCUS_LOSS=0 environment variable and restart Steam.

See also the steam-for-linux issue 4769.

Other issues

Steam Library in NTFS partition

If your Steam library resides in NTFS partition it is probable that games residing there could not start.

The trouble is that Wine uses a colon in its $WINEPREFIX/dosdevices directory, and NTFS-3G, when mounted with the windows_names option, is instructed to not create such colon names which can confuse Windows. Not adding it is not that unsafe: Windows will act fine besides being unable to open the symlink (which it will not need to do anyways); chkdsk may delete the link, but it is easily recreated.

Better workaround: mount without windows_names. This option is often added by GUI file explorers via udisks2 for caution, but adding a real Fstab line will give it a proper way to do so.

  1. Run genfstab -U / and extract the line containing the ntfs partition, e.g. UUID=12345678ABCDEF00 /run/media/user/Gamez ntfs {options_omitted} 0 0. Note the options are inaccurate because of fuse; if you want to see what really is in use, use ps aux|grep ntfs as root.
  2. Write the line into /etc/fstab, editing it to use the proper options without windows_names. With the earlier example, we would write UUID=12345678ABCDEF00 /run/media/user/Gamez ntfs rw,allow_other,user_id=1000,big_writes 0 0 – assuming you are UID 1000.
  3. Unmount the partition, then remount.

Alternatively, disable udisks use of windows_names globally following instructions in udisks#NTFS file creation failing (filename-dependent).

Other workaround: move the steamapps/common/Proton x.y and steamapps/compatdata to a non-NTFS drive, then create symbolic link in their original locations. You may be wasting some space on your otherwise important Linux drive, however.

$ mv SteamLibrary/steamapps/common/Proton\ x.y /home/user/dir/
$ mv SteamLibrary/steamapps/compatdata /home/user/dir/
$ ln -s /home/user/dir/Proton\ x.y/ SteamLibrary/steamapps/common/Proton\ x.y
$ ln -s /home/user/dir/compatdata/ SteamLibrary/steamapps/compatdata

Wrong ELF class

If you see this message in Steam's console output

ERROR: object '~/.local/share/Steam/ubuntu12_32/' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.

you can safely ignore it. It is not really any error: Steam includes both 64- and 32-bit versions of some libraries and only one version will load successfully. This "error" is displayed even when Steam (and the in-game overlay) is working perfectly.

Multiple monitors setup

This article or section needs expansion.

Reason: Is this Nvidia-only? Can this be reproduced by anyone? Is there an upstream report? (Discuss in Talk:Steam/Troubleshooting)

A setup with multiple monitors may prevent games from starting. Try to disable all additional displays, and then run a game. You can enable them after the game successfully started.

Also you can try running Steam with this environment variable set:

$ export LD_LIBRARY_PATH=/usr/lib32/nvidia:/usr/lib/nvidia:$LD_LIBRARY_PATH

Text is corrupt or missing

Try installing lib32-fontconfig, ttf-liberation and wqy-zenhei (for Asian characters), then restart Steam to see whether the problem is solved.

Note: When Steam cannot find the Arial font, font-config likes to fall back onto the Helvetica bitmap font. Steam does not render this and possibly other bitmap fonts correctly, so either removing problematic fonts or disabling bitmap fonts will most likely fix the issue without installing the Arial or ArialBold fonts. The font being used in place of Arial can be found with the command
$ fc-match -v Arial

SetLocale('en_US.UTF-8') fails at game startup or typing non-ASCII characters does not work in the Steam client

You need to generate the en_US.UTF-8 UTF-8 locale. See Locale#Generating locales.

Missing libc

The factual accuracy of this article or section is disputed.

Reason: Issue #3730 is closed. Is $HOME ending in a slash still relevant? (Discuss in Talk:Steam/Troubleshooting)

This could be due to a corrupt Steam executable. Check the output of:

$ ldd ~/.local/share/Steam/ubuntu12_32/steam

Should ldd claim that it is not a dynamic executable, then Steam likely corrupted the binary during an update. The following should fix the issue:

$ cd ~/.local/share/Steam/
$ ./ --reset

If it does not, try to delete the ~/.local/share/Steam/ directory and launch Steam again, telling it to reinstall itself.

This error message can also occur due to a bug in Steam which occurs when your $HOME directory ends in a slash (Valve GitHub issue 3730). This can be fixed by editing /etc/passwd and changing /home/username/ to /home/username, then logging out and in again. Afterwards, Steam should repair itself automatically.

Games do not launch on older Intel hardware


On older Intel hardware which does not support OpenGL 3, such as Intel GMA chips or Westmere CPUs, games may immediately crash when run. It appears as a error in /tmp/dumps/mobile_stdout.txt, but looking in /tmp/gameoverlayrenderer.log it shows a GLXBadFBConfig error.

This can be fixed, by forcing the game to use a later version of OpenGL than it wants. Add MESA_GL_VERSION_OVERRIDE=3.1 MESA_GLSL_VERSION_OVERRIDE=140 to your launch options.

Mesa: Game does not launch, complaining about OpenGL version supported by the card

Some games are badly programmed, to use any OpenGL version above 3.0. With Mesa, an application has to request a specific core profile. If it does not make such a request, only OpenGL 3.0 and lower are available.

This can be fixed, by forcing the game to use a version of OpenGL it actually needs. Add MESA_GL_VERSION_OVERRIDE=4.1 MESA_GLSL_VERSION_OVERRIDE=410 to your launch options.

2K games do not run on XFS partitions

This article or section needs expansion.

Reason: Seems to be a general issue, e.g. [6] (Discuss in Talk:Steam/Troubleshooting)

If you are running 2K games such as Civilization 5 on XFS partitions, then the game may not start or run properly due to how the game loads files as it starts. [7]

Steam controller not being detected correctly

See Gamepad#Steam Controller.

Steam controller makes a game crash

See Gamepad#Steam Controller makes a game crash or not recognized.

Steam hangs on "Installing breakpad exception handler..."


You have an Nvidia GPU and Steam has the following output:

Running Steam on arch rolling 64-bit
STEAM_RUNTIME is enabled automatically
Installing breakpad exception handler for appid(steam)/version(0_client)

Then nothing else happens. Ensure you have the correct drivers installed as well as their 32-bit versions (the 64-bit and 32-bit variants have to have the same versions): see NVIDIA#Installation.

Killing standalone compositors when launching games

Utilizing the %command% switch, you can kill standalone compositors (such as Xcompmgr or picom) - 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.

killall compositor && %command%; nohup compositor &

You can also add -options to %command% or compositor, of course.

Steam will latch on to any processes launched after %command% and your Steam status will show as in game. So in this example, we run the compositor through 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.

If your compositor supports running in daemon mode, you can use it instead. For example, picom(1) has the --daemon / -b option to daemonize its process:

killall picom && %command%; picom -b

Symbol lookup error using DRI3

Steam outputs this error and exits.

symbol lookup error: /usr/lib/ undefined symbol: xcb_send_request_with_fds

To work around this, run Steam with LIBGL_DRI3_DISABLE=1, disabling DRI3 for Steam.

Launching games on Nvidia optimus laptops

This article or section is out of date.

Reason: Was for using bumblebee : what is the equivalent for recommended setup now, using prime-run instead does not work (Discuss in Talk:Steam/Troubleshooting)

To be able to play games which require using Nvidia GPU (for example, Hitman 2016) on optimus enabled laptop, you should start game with primusrun prefix in launch options. Otherwise, game will not work.

Right click the game in your steam library and select Properties > GENERAL > LAUNCH OPTIONS. Change options to

primusrun %command%

Running steam with primusrun used to work. While steam has changed some behavior that now running steam with primusrun would not have effect on launching games. As a result, you need to set launch options for each game (and you do NOT have to run steam with primusrun).

For primusrun, VSYNC is enabled by default it could result in a mouse input delay lag, slightly decrease performance and in-game FPS might be locked to a refresh rate of a monitor/display. In order to disable VSYNC for primusrun default value of option vblank_mode needs to be overridden by environment variable.

vblank_mode=0 primusrun %command%

Same with optirun that uses primus as a bridge.

vblank_mode=0 optirun -b primus %command%

If that did not work try:


For more details see Bumblebee#Primusrun mouse delay (disable VSYNC).


HiDPI support should work out of the box, although on some systems it is necessary to force it setting the -forcedesktopscaling factor cli option to set the desired scale factor.

Protocol support under KDE Plasma

If you are getting an error after running a game through web browser (or executing the link through xdg-open)

Error — KIOExec
File not found: steam://run/440

Go to System Settings -> Applications -> File Associations, add new, select inode group and name it vnd.kde.service.steam, then under Application Preference Order you have to add Steam. Apply changes, It should be working now.

The game crashes when using Steam Linux Runtime - Soldier

This article or section is out of date.

Reason: Was a fix 2021-03 : is this still relevant today? (Discuss in Talk:Steam/Troubleshooting)

Since Proton 5.13 Steam uses the Steam Linux Runtime - Soldier by default. Some games crash when using it.

To bypass it, you can:

  • Manually build a proton without the Steam Runtime
  • Replace the Soldier entry point script:

shift 2
exec "${@}"

Games running with Proton 5.13+ have no Internet connectivity

If you are using systemd-resolved as your DNS resolver, ensure you have created the resolv.conf symlink as described in systemd-resolved#DNS.

The file should contain something similar to:

# This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
# Do not edit.

"could not determine 32/64 bit of java"

A forgotten install of the linux-steam-integrationAUR package caused this with at least one game. Early on there were conflicts between the system and the steam runtime versions of some libraries, and that package helped resolve some of them. It is unclear whether it is still helpful, but uninstalling it resolved the above error message for Project Zomboid. The solution was discovered by noticing that running the command from the command line worked, but switching the launch options to sh -xc 'echo %command%; declare -p' showed Steam was trying to run the exact same command, but there were a lot of lsi--prefixed libraries inserted in the preload and path.

Stuttering with Vulkan

If you notice a constant intense stutter every 1-2 seconds, there may be conflicts in your vsync settings. Manually configuring vsync in the parameters will possibly fix it.

Go to the game properties and configure it in Launch Options:

DXVK_FRAME_RATE=60 %command%

Force OpenGL emulation

Some, especially older games might not work with the default Vulkan (DXVK) wrapper Proton uses. Try running the application with WineD3D OpenGL wrapper instead:

PROTON_USE_WINED3D=1 %command%

File picker does not see anything but steam library

See FS#78625. You need to install xdg-desktop-portal.

DirectX errors on hybrid graphics

For laptop with Intel/Nvidia Hybrid graphics encountering the following error:

A d3d11-compatible gpu (feature level 11.0, shader model 5.0) is required to run the engine.

It's probably because your game is running on the iGPU instead of the dedicated GPU and you need to configure PRIME. If it's still not doing it, try using Direct3D instead of DXVK.

No Internet Connection when downloading

If you see No Internet Connection while downloading games, a possible solution is clearing the download cache (Steam > Settings > Downloads > Clear Download Cache).

Poor performance or stuttering after launching Steam

If you experience reduced performance or stuttering, lasting anywhere from a few seconds to a couple of minutes after launching Steam, it may be cased by bugged or outdated Proton installations.

Remove bugged Proton installed under app ID 0: ~/.steam/root/steamapps/compatdata/0. You may also need to remove outdated and problematic Proton versions, including custom ones like GE-Proton, especially 5.21-GE-1.

For more details, see steam-for-linux#8114.

See also