Steam/Client troubleshooting

This article provides troubleshooting details for the Steam client on Linux systems.

ATI video drivers

• If ATI Legacy drivers are used, and a Valve game (Counter-Strike: Source, Team Fortress 2, etc.) fails to start with the following error:

Required OpenGL extension "GL_EXT_texture_sRGB_decode" is not supported. Please update your OpenGL driver.

Update the ATI Legacy drivers to the most recent version.

Big Picture Mode and games not working with controller

This issue is most likely caused by incorrect uinput device node permissions.

Sony DualShock 3

Check /dev/uinput:

crw-rw---- 1 root input 10, 223 Apr  3 21:44 /dev/uinput

In order for Big Picture Mode to see the controller, it needs the user to have write access to it. The solution is a udev rule:

FILE /etc/udev/rules.d/60-dualshock3.rules

# Fix permissions to allow the DualShock 3 controller to be used by Steam
SUBSYSTEM=="usb", ATTRS{idVendor}=="054c", MODE="0666"
KERNEL=="uinput", SUBSYSTEM=="misc", MODE="0660", GROUP="input"

After saving the file, udev will need to be "re-triggered":

root #udevadm control --reload

root #udevadm trigger

If the user(s) that intend to use the controller with Steam are not already in the input group, they will need to be added:

root #gpasswd -a <user> input

After that, log out and back in as said user. Steam should detect the controller without issue. A good way to test this is to make sure Steam has focus and press the PlayStation button. If Big Picture mode starts, the controller is detected and configured correctly.

Microsoft Xbox 360 controller

The Microsoft Xbox 360 controller should work out of the box with steam-overlay and CONFIG_JOYSTICK_XPAD compiled into the kernel.

Wayland

Big Picture Mode not launching on Wayland

If Big Picture Mode fails to launch on Wayland, check if you do not have set the environment variable SDL_VIDEODRIVER=wayland, or override it on launching Steam:

user $SDL_VIDEODRIVER=x11 steam

When using the provided desktop file to launch Steam, the workaround can be made permanent by editing its Exec part:

FILE /usr/share/applications/steam.desktop

Exec=env SDL_VIDEODRIVER=x11 /usr/bin/steam %U

Steam client freezing shortly after startup

The Steam client may consistently freeze shortly after startup when run under KDE Wayland. This appears to be related to a failure of the steam client to properly handle its notification animations.

The easiest workaround is to click and dismiss any notification after steam has launched. It has been reported that using a custom skin for steam that disables notification animations resolves this issue for some (but not all) users.

Track the upstream issue here.

Direct rendering is not being used

The information in this section is probably outdated. You can help the Gentoo community by verifying and updating this section.

If Steam starts with the following error:

Error: OpenGL GLX context is not using direct rendering, which may cause performance problems.

Confirm if direct rendering is enabled with glxinfo, which is provided by the x11-apps/mesa-progs package:

root #glxinfo | grep "direct rendering"

direct rendering: Yes

If direct rendering is not enabled, ensure that the correct OpenGL implementation is selected:

root #eselect opengl list

Next, ensure that the user running Steam has sufficient permissions to access direct rendering. If the USE variable is set to acl and elogind or systemd is being used, permissions will be handled automatically. Otherwise, add the user running Steam to the video group:

root #gpasswd -a user video

If direct rendering is enabled and the correct OpenGL implementation is selected, then this issue may be caused by app-eselect/eselect-opengl 1.3*.. This issue has been fixed for users of the steam-launcher ebuild. Otherwise, run the following as a temporary workaround:

For ATI drivers:

user $LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/lib32/opengl/ati/lib" steam

For NVIDIA drivers:

user $LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/lib32/opengl/nvidia/lib" steam

If direct rendering is still not enabled, refer to the Steam Knowledge Base article on direct rendering for possible solutions.

Flatpak client

SSL errors

When installing the Flatpak version, certain items may show "Invalid SSL certificate" when trying to load (like News and Friends). This is caused by a bug in app-crypt/p11-kit. Make sure the version of app-crypt/p11-kit is equal to or greater than 0.23.20.

Steam systray icon is not visible

There is currently no solution. Instead the "empty space" in the systray can be clicked to open Steam.

Vulkan breaks after nvidia-drivers update

After updating x11-drivers/nvidia-drivers, Proton and Vulkan-based games may fail to work (fallback to OpenGL). On a laptop with multiple GPUs, Proton/Vulkan games use the integrated GPU instead of the NVIDIA discrete GPU after updating x11-drivers/nvidia-drivers.

Other symptoms when starting Vulkan-based games:

Could not create Vulkan instance :
ERROR_EXTENSION_NOT_PRESENT

FATAL ERROR: vkCreateInstance failed with error (VK_ERROR_EXTENSION_NOT_PRESENT)

This issue is likely due to a driver version mismatch. Flatpak applications run within a container (or "sandbox"), and the NVIDIA libraries within the container must match the drivers loaded and running on the Gentoo host.

To fix this, run

user $flatpak update --app com.valvesoftware.Steam

to update the required runtime for com.valvesoftware.Steam. Check if flatpak updates the org.freedesktop.Platform.GL[32].nvidia-VERSION-NUM package to match the version number of x11-drivers/nvidia-drivers on the Gentoo host.

glxChooseVisual failed

If you encounter this error:

glXChooseVisual failed
glXChooseVisual failedsrc/steamUI/Main.cpp (409) : Assertion Failed: Fatal Error: glXChooseVisual failed
src/steamUI/Main.cpp (409) : Assertion Failed: Fatal Error: glXChooseVisual failed

It usually indicates x11-drivers/nvidia-drivers needs to be compiled with the abi_x86_32 USE flag for 32-bit support. Add it to your package.use,

FILE /etc/portage/package.use

x11-drivers/nvidia-drivers abi_x86_32

Then do a world update:

root #emerge -avuDU @world

Friends list offline and store not rendering

When running Steam in the GNOME desktop environment the store (and special offers) no longer properly render; the friend's list is constantly in an offline state and status cannot be changed to online. When viewing Steam client debugging output, the following line is repeatably displayed:

./steamwebhelper: symbol lookup error: /usr/lib/gio/modules/libdconfsettings.so: undefined symbol: g_log_structured_standard

The issue is caused by Steam not properly setting the GSETTINGS_BACKEND environment variable, not setting the GIO_MODULE_DIR environment variable to its own GIO/modules path, and not shipping a newer version of glib library in its included runtime.

The workaround is to set the GSETTINGS_BACKEND environment variable to memory when launching Steam. This is best completed by editing the Exec line in the steam.desktop file used to launch Steam:

FILE /usr/share/applications/steam.desktop

Exec=env GSETTINGS_BACKEND=memory /usr/bin/steam %U

Hardened Gentoo

It seems that the Steam binary has rwx bits set, and needs to be PaX marked in order to work on a hardened system:

user $paxctl-ng -m ~/.local/share/Steam/ubuntu12_32/steam

The binaries of most games should also be PaX marked:

user $paxctl-ng -m ~/.local/share/Steam/steamapps/common/World\ of\ Goo/WorldOfGoo

user $paxctl-ng -m ~/.local/share/Steam/steamapps/common/Uplink/uplink.bin.x86_64

user $paxctl-ng -m ~/.local/share/Steam/steamapps/common/Team\ Fortress\ 2/hl2_linux

Failure to perform PaX marking will result in the game failing to run, with little information given. To check if a game needs to be PaX marked, run the game's startup script or binary file (found in ~/.local/share/Steam/steamapps or ~/.local/share/Steam/steamapps/common) under a debugger. This can be accomplished with some of Valve's provided startup scripts by setting the GAME_DEBUGGER environment variable to gdb:

user $env GAME_DEBUGGER=gdb ./hl2.sh

If a binary needs to be PaX marked, gdb should output something similar to:

warning: Cannot call inferior functions, Linux kernel PaX protection forbids return to non-executable pages!

and/or:

Cannot access memory at address 0x80486c6.

After an update in July 2013, Steam also needs a PaX marked /bin/bash when the OpenGL libraries require rwx markings, otherwise games will fail to run from the Steam client:

user $sudo paxctl-ng -m /bin/bash

However, this results in Bash failing to run. It is also a security issue, and it is strongly recommended to try without PaX marking. If it works when using the proprietary NVIDIA drivers, please make a note of it on this page.

libGL fails to load driver

The Steam runtime overrides various system libraries, including libgcc, libstdc++, and libgpg-error with its own bundled versions. This can result in Steam failing to start with the following error:

libGL error: unable to load driver: <driver_name>.so

To workaround this issue, locate the problematic library by starting Steam with libGL debugging enabled:

user $LIBGL_DEBUG=verbose /usr/bin/steam

libGL: dlopen /usr/lib32/dri/i965_dri.so failed (/usr/lib32/libgcrypt.so.20: symbol gpgrt_lock_lock, version GPG_ERROR_1.0 not defined in file libgpg-error.so.0 with link time reference)
libGL error: unable to load driver: i965_dri.so

Next, delete the problematic library from the Steam runtime to force the use of system library instead:

user $find ~/.steam/root/ -name "libgpg-error.so*" -print

Repeat the above to discover other problematic libraries in the Steam runtime. The bundled libraries may reappear after every Steam update. In this case simply delete the libraries again from the Steam runtime.

If the above solution does not work, run the following as a temporary workaround:

For NVIDIA drivers:

user $LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/lib32/opengl/nvidia/lib" steam

libGL fails to load driver with AMDGPU

When using AMDGPU, Steam may fail to start with the following error:

libGL error: unable to load driver: radeonsi_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: radeonsi
libGL error: unable to load driver: radeonsi_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: radeonsi
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast

To workaround this issue, disable the problematic libraries from the Steam runtime to force the use of system libraries instead:

user $mv ~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/lib/i386-linux-gnu/libgcc_s.so.1{,.disable}

user $mv ~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/libstdc++.so.6{,.disable}

Note
Tested with a Sapphire Radeon HD 7870 GPU on ~amd64 and VIDEO_CARDS="amdgpu radeonsi" in /etc/portage/make.conf.

Memory corruption

If Steam starts with the following error:

*** glibc detected *** zenity: malloc(): memory corruption: 0x00000000016cf020 ***

Installing the x11-libs/libXi package should fix the issue.

root #emerge --ask x11-libs/libXi

Missing fonts

If Steam is having issues with missing fonts, installing the media-fonts/font-bitstream-100dpi and media-fonts/corefonts packages may fix the issue.

root #emerge --ask media-fonts/font-bitstream-100dpi media-fonts/corefonts

If the X server does not recognize the newly installed fonts, run the following:

user $xset +fp /usr/share/fonts/100dpi

user $xset +fp /usr/share/fonts/corefonts

user $xset fp rehash

Reset the installation

To reset (i.e. wipe) the Steam installation, including installed games, and reinstall Steam without losing data:

user $steam --reset

Reversed X cursor

If an X cursor theme has not been set by the desktop environment or window manager, Steam will override the default X cursor theme. This can result in a reversed X cursor from left to right. The issue can be fixed by setting an X cursor theme, if one is available, or by installing an X cursor theme:

root #emerge --ask x11-themes/vanilla-dmz-xcursors

If the X cursor is still reversed, even after exiting Steam, run the following to fix the issue:

user $xsetroot -cursor_name left_ptr

Segfault when remember my password is selected

Selecting the Remember my password option at the Steam login dialog when Steam is running without D-Bus, will cause Steam to segfault the next time it is started. This issue can be fixed by running the following:

user $rm -fr ~/.local/share/Steam/config

Segfault when starting Steam

Steam segfaults when D-Bus is not accessible. Check that dbus service is runnning and that the DBUS_SESSION_BUS_ADDRESS variable is set:

user $echo $DBUS_SESSION_BUS_ADDRESS

dbus-J2zA6AVqHR,guid=e86f44f3b96c6c03f68d01a66029c172

This may happen when KDE is started from the command line and omit to use dbus-launch.

If Steam fails to start with the following error:

munmap_chunk(): invalid pointer: 0xf75aca24
free(): invalid pointer: 0xffca16d0

Setting the locale to C may fix the issue:

user $LANG=C steam

If Steam fails to start with the following error:

The futex facility returned an unexpected error code.

The kernel option CONFIG_COMPAT_32BIT_TIME needs to be activated.

Segfault when using apulse

Using Steam with media-sound/apulse while D-Bus is not running, will cause Steam to segfault with a Connection refused message. This issue can be fixed by ensuring that D-Bus is running:

root #rc-service dbus start

Segfault when using libcxx

When using sys-libs/libcxx system-wide, a Segmentation Fault when running Steam may occur. To fix this, make sure to set LD_PRELOAD to the following:

FILE /usr/share/applications/steam.desktop

Exec=env LD_PRELOAD="/usr/lib/gcc/x86_64-pc-linux-gnu/12/32/libstdc++.so" /usr/bin/steam %U

user $LD_PRELOAD="/usr/lib/gcc/x86_64-pc-linux-gnu/12/32/libstdc++.so" steam

Taskbar button persists even when closed or minimized

Depending on the desktop environment being used, the Steam taskbar button may persist even when the Steam window is closed or minimized to the system tray. To correct this behavior, force the Steam window to close instead of minimize:

user $STEAM_FRAME_FORCE_CLOSE=1 steam

To set the STEAM_FRAME_FORCE_CLOSE environment variable permanently, add the following to the shell login initialization file:

FILE ~/.bash_profileSetting a local environment variable with Bash

export STEAM_FRAME_FORCE_CLOSE=1

Log out and back in to have the changes take effect.

Steam hangs when installing a game

If clicking the Install button on a Steam game page causes the Steam client to hang with the following console output:

GameAction [AppID 255710, ActionID 1] : LaunchApp failed with AppError_18 with ""              
GameAction [AppID 255710, ActionID 1] : LaunchApp changed task to Failed with ""

It might be possible to fix this by running Steam with:

user $STEAM_RUNTIME=1 STEAM_RUNTIME_PREFER_HOST_LIBRARIES=1 steam

Use system libraries

Steam bundles many libraries which are used instead of the system libraries. To force Steam to use the system libraries, disable the Steam runtime:

Warning
It is not recommended to disable the Steam runtime, as it can lead to numerous problems, including runtime and missing 32-bit libraries.

user $STEAM_RUNTIME=0 steam

To set the STEAM_RUNTIME environment variable permanently, add the following to the shell login initialization file:

FILE ~/.bash_profileSetting a local environment variable with Bash

export STEAM_RUNTIME=0

Log out and back in to have the changes take effect.

Windows games crash immediately on launch

If Windows-only games crash without even displaying a window, and the Steam log includes a line that begins:

wine: Unhandled exception 0x20474343 in thread..

or a series of errors similar to:

Vulkan missing requested extension 'VK_KHR_surface'.
Vulkan missing requested extension 'VK_KHR_xlib_surface'.
BInit - Unable to initialize Vulkan!

the cause might be that the system Mesa library (on which Steam depends) is not compiled with Vulkan support. Follow the instructions on the Vulkan page to rectify this, and ensure that the media-libs/vulkan-loader package is compiled with X11 support:

FILE /etc/portage/package.use

media-libs/vulkan-loader X

xterm launches briefly and then closes

This issue is caused by the shell being set to something other than a POSIX compliant shell (i.e. fish). Change the shell to a POSIX compliant shell and accept the Steam license agreement. The shell can be set back afterwards.

System information can not be detected

Sometimes it may be useful to obtain system information, as explained here: https://steamcommunity.com/sharedfiles/filedetails/?id=390278662 . If the client is not able to detect the distribution in which it is running or any related information, install sys-apps/lsb-release.

root #emerge --ask sys-apps/lsb-release

Library and store display a black screen

This is related to the following error:

D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/etc/machine-id": No such file or directory

In this case it is remedied by generating a machine ID with the following command

root #systemd-machine-id-setup

Games immediately crash/don't start

This is related to the following error:

eventfd: Too many open files
eventfd: Too many open files
eventfd: Too many open files
eventfd: Too many open files
eventfd: Too many open files
eventfd: Too many open files
eventfd: Too many open files
eventfd: Too many open files
wine: Unhandled page fault on read access to 0000000000000000 at address 0000000141510EDA (thread 0114), starting debugger...
eventfd: Too many open files

Try cranking up the ulimit (user limit) for Steam.

FILE /etc/security/limits.d/steam.conf

* - nofile 1048576

Log out and log back in.

What this does is allow steam to open 1048576 file descriptors at once. If this value seems too high or low, adjust accordingly!

This config will allow all users and groups to use the new limit. To set the new limit to a particular user only, the * in the beginning must be replaced with a username.

systemd additional step

FILE /etc/systemd/system.conf

DefaultLimitNOFILE=1048576

FILE /etc/systemd/user.conf

DefaultLimitNOFILE=1048576

Then

root #systemctl daemon-reexec

Log out and log back in.

wine: RLIMIT_NICE is <= 20

RLIMIT_NICE has a range from 1 (corresponding to a nice value of 19, lowest priority) to 40 (corresponding to a nice value of -20, highest priority).

When a game is run using Proton, the wine message might show up in the logs. The way to fix this is to edit the limits config:

FILE /etc/security/limits.d/steam.conf

* - nice -20

Log out and log back in.

This allows steam to run processes with nice values as low as -20 (highest priority).

This config will allow all users and groups to use the new limit. To set the new limit to a particular user only, the * in the beginning must be replaced with a username.

SteamVR crashes amdgpu driver when started with valve index

Find out the name of HMD screen:

user $xrandr

Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 disconnected (normal left inverted right x axis y axis)
   2880x1600     90.00 + 144.00   120.02    80.00  
   1920x1200     90.00  
   1920x1080     90.00  
   1600x1200     90.00  
   1680x1050     90.00  
   1280x1024     90.00  
   1440x900      90.00  
   1280x800      90.00  
   1280x720      90.00  
   1024x768      90.00  
   800x600       90.00  
   640x480       90.00  
DisplayPort-2 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 480mm x 270mm
   1920x1080     74.97*+  60.00    50.00    59.94  
   1680x1050     59.95  
   1400x1050     59.98  
   1600x900      60.00  
   1280x1024     60.02  
   1440x900      59.89  
   1280x800      59.81  
   1280x720      60.00    50.00    59.94  
   1024x768      60.00  
   800x600       60.32  
   720x576       50.00  
   720x480       60.00    59.94  
   640x480       60.00    59.94  
HDMI-A-0 disconnected (normal left inverted right x axis y axis)

In this example it's DisplayPort-1. Execute this ugly script before starting SteamVR and crash will be prevented.

FILE fix-vr

#!/bin/bash

xrandr --output DisplayPort-1 --set non-desktop 0
xrandr --output DisplayPort-2 --primary --auto --output DisplayPort-1 --auto
sleep 5
xrandr --output DisplayPort-2 --primary --auto --output DisplayPort-1 --off
xrandr --output DisplayPort-1 --set non-desktop 1

No sound in SteamVR Home

Move libSDL2-2.0.so.0 files somewhere to force loading libSDL2-2.0.so.0 from the system:

user $mv ~/.local/share/Steam/steamapps/common/SteamVR/tools/steamvr_environments/game/bin/linuxsteamrt64/libSDL2-2.0.so.0 ~/linuxsteamrt64-libSDL2-2.0.so.0

user $mv ~/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/libSDL2-2.0.so.0 ~/linux64-libSDL2-2.0.so.0

If it doesn't help, follow the commented advice from ~/.local/share/Steam/steamapps/common/SteamVR/tools/steamvr_environments/game/steamtours.sh and execute:

user $export GAME_DEBUGGER="strace -f -o strace.log"

user $steam

The output will be available in ~/.local/share/Steam/steamapps/common/SteamVR/tools/steamvr_environments/game/strace.log. Additional instructions can apply to Half-Life: Alyx.

"Only one instance of the game can be running at one time." error in SteamVR

Stop steam and delete steam-related files from /tmp.

user $rm -r /tmp/qipc_systemsem_vrmonitor* /tmp/runtime-steam/ /tmp/source_engine_*.lock /tmp/steam_chrome_shmem_*

If you have other steam files there, probably it's a good idea to delete them too. Then start steam again.

Sharing a games library between Windows and Linux on a NTFS-backed directory

Official Valve instructions for using Proton to share games on an NTFS partition between Linux and Windows can be found here: https://github.com/ValveSoftware/Proton/wiki/Using-a-NTFS-disk-with-Linux-and-Windows

Client is not scaling properly

Environment variables

As of 2023-06-15 the Steam Beta Client honors the following environment variable which can to manually adjust the scaling factor of the client's display window:

user $STEAM_FORCE_DESKTOPUI_SCALING=<float> steam

Replace <float> as necessary for the scaling factor. It also should honor the scaling factor for GNOME systems via the org.gnome.desktop.interface/text-scaling-factor configuration value. This value can be inspected using gsettings.

CLI parameters

As of 2023-05-05, the Steam Beta Client provides the following command line argument to manually adjust the scaling factor of the client's display window:

user $steam -forcedesktopscaling <float>

Replace <float> as necessary for the scaling factor. For example, when running a 4K display, a factor of 2.0 is generally sufficient to present the client as it would appear without scaling on a 1080p display:

user $steam -forcedesktopscaling 2.0

Increase virtual memory mapping

Certain games like Dayz and Counter-Strike 2 may run out of memory if the default value of 65,530 is set in the /etc/sysctl.conf file. It is recommended to increase the default virtual memory map to a value of 1048576 in order to avoid memory related issues with certain games. This will affect all processes running on the system, so proceed with the risk in mind:

root #sysctl -w vm.max_map_count=1048576

SteamVR doesn't work after it was updated (as steam package) and no workaround exists

In this case it's possible do downgrade SteamVR steam package as described here https://github.com/ValveSoftware/SteamVR-for-Linux/issues/639#issuecomment-1817538299 . This workflow should also be able to downgrade other steam packages.

Slow download or limited

Disable HTTP2 for faster downloads. Some systems and configurations seem to have issues with HTTP2. Disabling HTTP2 will probably yield faster downloads on those configurations. Create the file as described below and add the following lines to the file

Try just one line first, if there is no improvement then use both

Steam Overlay Native Installs, create:

user $echo "@nClientDownloadEnableHTTP2PlatformLinux 0" >> ~/.steam/steam/steam_dev.cfg

Restart Steam and check download speed.

If the first option doesn't work, try adding another line

user $echo "@fDownloadRateImprovementToAddAnotherConnection 1.0" >> ~/.steam/steam/steam_dev.cfg

Restart Steam and check download speed.

Flatpak Steam Installs, create:

user $echo "@nClientDownloadEnableHTTP2PlatformLinux 0" >> ~/.var/app/com.valvesoftware.Steam/.steam/steam/steam_dev.cfg

Restart Steam and check download speed.

If the first option doesn't work, try adding another line

user $echo "@fDownloadRateImprovementToAddAnotherConnection 1.0" >> ~/.var/app/com.valvesoftware.Steam/.steam/steam/steam_dev.cfg

Restart Steam and check download speed.