Hello @CMBadiuk, does any 32 bit opengl application work like glxinfo from mesa-utils:i386?
Yes, I just confirmed that glxinfo works, and that I have mesa-utils:i386. After making sure I had the mesa utils, I tried running Steam again, then had the same error.
I'm having the same problem - Ubuntu 18.04, no such file or directory. glxinfo and glxgears exist.
And there does, in fact, not exist any $HOME/.local/share/Steam/ubuntu12_32/steam-runtime/run.sh.
One of the solutions seems to be to install Steam via Ubuntu store (using snap). But I like deb and don't like snap.
Sorry, I tried snap on Ubuntu 18.04, it did not work.
The template file of run.sh can be found here; https://github.com/ValveSoftware/steam-runtime/blob/master/templates/run.sh
I tried adding it manually to the directory ~/.local/share/Steam/ubuntu12_32/steam-runtime/ and running the command sudo chmod +x (which gives the script execution privileges).
The template file of
run.shcan be found here; https://github.com/ValveSoftware/steam-runtime/blob/master/templates/run.shI tried adding it manually to the directory
~/.local/share/Steam/ubuntu12_32/steam-runtime/and running the commandsudo chmod +x(which gives the script execution privileges).
Does it work?
The error is gone, but steam does not launch.
Is it a Problem with the Official NVIDIA Driver?
Because some people on the internet say it is.
I'm observing the same error. :/
same.
@MagB93 @kiikoh - is your problem run.sh error, or that steam does not launch?
Assuming original issue is fixed, closing.
same issue
Assuming original issue is fixed, closing.
How was it fixed?
@TTimo Sorry for the late answer. I've been busy at work.
I get the following error in the terminal
$ steam
Running Steam on ubuntu 18.04 64-bit
STEAM_RUNTIME is enabled automatically
Pins up-to-date!
/home/mbad/.local/share/Steam/steam.sh: line 828: /home/mbad/.local/share/Steam/ubuntu12_32/steam-runtime/run.sh: No such file or directory
Installing breakpad exception handler for appid(steam)/version(0)
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
the output of nvidia-smi is
Thu Mar 28 19:45:13 2019
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 418.56 Driver Version: 418.56 CUDA Version: 10.1 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce RTX 2080 Off | 00000000:29:00.0 On | N/A |
| 22% 32C P8 15W / 215W | 457MiB / 7949MiB | 15% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 1265 G /usr/lib/xorg/Xorg 28MiB |
| 0 1309 G /usr/bin/gnome-shell 58MiB |
| 0 1548 G /usr/lib/xorg/Xorg 250MiB |
| 0 7254 G ...uest-channel-token=16894064775485970758 97MiB |
+-----------------------------------------------------------------------------+
Do you need something else?
Hello @MagB93, can you verify any 32 bit opengl application like glxinfo from mesa-utils:i386 works? Swrast is mesa's slower cpu opengl renderer and hints that the system is trying to use mesa's libGL.so.1 with nvidia's proprietary driver, which is incompatible.
~You are most likely encountering #5778 and run.sh missing could be a red herring.~ Looks like this is a current version in https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa/+packages. Please verify you have libnvidia-gl-418:i386 with something like apt policy libnvidia-gl-418:i386 and install it if you don't have it.
@kisak-valve no nothing of that matter was installed. I removed the driver from nvidia's site
and I've tried to install the one from the ppa you've mentioned. But without success.
The new installed driver just won't load. In Ubuntu-GUI where I can install the driver I can't
fix on the 418 driver. If I install it on the command line won' work either.
I guess I'll return the nvidia card and get an Vega VII instead, my workload besides gaming was FP64 anyway. ^^
Sorry for the trouble.
Please see kisak's comment about and check that your 32 bit opengl drivers are setup correctly. If not consider opening a separate support issue.
If your drivers are working correctly, but steam does not start, and you are seeing an error about run.sh during startup. Please do the following the report back:
STEAM_DEBUG=1 steam - save the output mv ~/.local/share/Steam/ubuntu12_32/steam-runtime ~/.local/share/Steam/ubuntu12_32/steam-runtime.offSTEAM_DEBUG=1 steam again - save the output if that still doesn't work and report back ..Thanks!
Installed Steam using the instructions here: https://github.com/ValveSoftware/steam-for-linux
First got the error about a missing run.sh so I did what @leimao did and manually downloaded it from this repo and put it in the correct folder: https://github.com/ValveSoftware/steam-for-linux/issues/6077#issuecomment-471270471
The missing run.sh error goes away but I am left with two libGL errors.
crawforc3@computer:~ $ steam
Setting up Steam content in /home/crawforc3/.local/share/Steam
Running Steam on ubuntu 18.04 64-bit
STEAM_RUNTIME is enabled automatically
Pins potentially out-of-date, rebuilding...
/home/crawforc3/.local/share/Steam/steam.sh: line 828:
/home/crawforc3/.local/share/Steam/ubuntu12_32/steam-runtime/run.sh: No such file or directory
Installing breakpad exception handler for appid(steam)/version(0)
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
Following @kisak-valve's suggestions:
Installed mesa-utils and ran glxinfo. I guess it works, here's the output:
crawforc3@computer:~/.local/share/Steam $ glxinfo | head -n 20
name of display: :1
display: :1 screen: 0
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
server glx extensions:
GLX_ARB_context_flush_control, GLX_ARB_create_context,
GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile,
GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float,
GLX_ARB_multisample, GLX_EXT_buffer_age,
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile,
GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_libglvnd,
GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear,
GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer,
GLX_NV_robustness_video_memory_purge, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGI_swap_control, GLX_SGI_video_sync
client glx vendor string: NVIDIA Corporation
client glx version string: 1.4
client glx extensions:
Here's the output from nvidia-smi:
Note that I'm using version 410 drivers
crawforc3@computer:~ $ nvidia-smi
Sat Mar 30 08:57:28 2019
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 410.48 Driver Version: 410.48 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 108... Off | 00000000:01:00.0 On | N/A |
| 0% 41C P8 15W / 280W | 515MiB / 11177MiB | 1% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 1206 G /usr/lib/xorg/Xorg 26MiB |
| 0 1241 G /usr/bin/gnome-shell 90MiB |
| 0 3116 G /usr/lib/xorg/Xorg 197MiB |
| 0 3250 G /usr/bin/gnome-shell 139MiB |
| 0 4351 G ...quest-channel-token=7772452847088013529 58MiB |
+-----------------------------------------------------------------------------+
This is the output from apt policy libnvidia-gl-410
crawforc3@computer:~ $ apt policy libnvidia-gl-410
libnvidia-gl-410:
Installed: 410.48-0ubuntu1
Candidate: 410.48-0ubuntu1
Version table:
*** 410.48-0ubuntu1 500
500 file:/var/cuda-repo-10-0-local-10.0.130-410.48 Packages
100 /var/lib/dpkg/status
Hello @crawforc3, both glxinfo from mesa-utils (without :i386) and nvidia-smi told you that you have 64 bit nvidia drivers installed properly, but tells you nothing about 32 bit support. In your case you've encountered #5778, which is a driver packaging issue.
@kisak-valve Thanks, I went back and removed mesa-utils and installed mesa-utils:i386. And you're right. glxinfo now has this output:
crawforc3@computer:~ $ glxinfo
name of display: :1
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
X Error of failed request: GLXBadContext
Major opcode of failed request: 154 (GLX)
Minor opcode of failed request: 6 (X_GLXIsDirect)
Serial number of failed request: 54
Current serial number in output stream: 53
Thanks for the quick response!
First got the error about a missing run.sh so I did what @leimao did and manually downloaded it from this repo and put it in the correct folder: #6077 (comment)
I would like to understand how this happens - there should be no need to get run.sh anywhere. It is packaged in the steam runtime that the steam client downloads during first run. If you are able, please run through the steps in https://github.com/ValveSoftware/steam-for-linux/issues/6077#issuecomment-478062644 and report.
Same issues here
I had this issue when I first installed Steam. It makes it really difficult to replicate if you install it on your desktop. Every Linux installation is somewhat different from another.
I managed to get Steam to install in a LXD system container and I just completed the instructions,
https://blog.simos.info/running-steam-in-a-lxd-system-container/
That is, you launch a brand new and pristine Ubuntu 18.04 in a LXD system container and then set it up to run Steam in there. Any user-space configuration is restricted in the container.
While writing the tutorial, I would get the issues reported here. For example, I would try and successfully get Steam to launch in a i386 (ubuntu:18.04/i386) container, but then the Store would not work because there is no support for 32-bit operating systems since a couple of years ago. By killing and recreating those system containers, I managed to get a working set of steps.
@TTimo that's the issue. When you run steam for the 1st time it does nothing/downloads nothing. Thats why this error appears.
From myself I want to add that this issue does NOT happen with linux mint 19.1 whatever livedvd or clean install but DOES happen after performing system update (prior to making any additional modifications). If steam installed 1st and THEN update is performed, everything continues to work fine.
Therefore some update breaks steam installation process and not the actual steam.
If you can install it in a container both with and without this failure, can you do that and compare the diffs from the base image? I suspect there's a smoking gun somewhere in there - it may be an upstream bug, or it may be something that steam expects as a dependency that's not properly getting installed after the upgrade or something.
@waynew Once I installed Steam in a LXD system container, it would work. I could not get a case where it stopped working after updates, etc. By default, the Ubuntu container images perform automatically any security updates but you need to explicitly do any non-security updates.
As I mentioned before, once steam is installed and was able to launch, it would work fine, with or without updates. The problem is with installation process that is supposed to grab additional resources (with run.sh being of them). On a fully updated system after initial steam install no additional install steps are performed and so when steam launches it can't find run.sh and other stuff. Because it is indeed not there.
I have no idea what steam uses to grab additional resources or how it does it. But for those who know, it should not be hard to find out what update could possibly affect that. Applying updates one by one manually is a way as well, but a time-consuming one.
@Meru just to confirm - did you use the latest, official steam_latest.deb for your first install on ubuntu 18.04? e.g.
8f8e1e573b5bdf0ffe516f4cba91ed4b steam_latest.deb (md5sum, version 1.0.0.59 out of http://repo.steampowered.com/steam/archive/precise/steam_latest.deb)
edit: yes, you probably did ... I see what the problem is now.
This new steam debian package candidate should solve the run.sh problem (and potentially a number of other issues):
http://repo.steampowered.com/download/testing/steam-launcher_1.0.0.60_all.deb
fc32d588a5b5fe04cd8d0781c6f934cf steam-launcher_1.0.0.60_all.deb
It will install the current steam beta client directly, but that shouldn't be a huge problem. You should still be able to come back down to the production steam client after the bootstrap.
Please test if you are able. We will probably push this new package to replace 1.0.0.59 some time after the current beta client goes to general availability.
FWIW for me this partially fixes the problem - i.e. I no longer get run.sh: No such file or directory. It hangs at
Repairing installation, linking /home/wayne/.steam/steam to /home/wayne/.local/share/Steam
Running Steam on ubuntu 18.04 64-bit
STEAM_RUNTIME is enabled automatically
Pins up-to-date!
Installing breakpad exception handler for appid(steam)/version(0)
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
Tried rm -rf ~/.steam && rm -rf ~/Steam && rm -rf ~/.local/share/Steam after a sudo apt purge steam and then relaunching, to no success :man_shrugging:
Hello @waynew, swrast is mesa's slower cpu opengl implementation and this error is commonly seen when the system tries to use mesa's libGL.so.1 with the nvidia proprietary driver, which is incompatible.
What video card / driver version are you using?
~ sudo ldconfig -p | grep -i gl.so (2s 911ms)
libwayland-egl.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libwayland-egl.so.1
libcogl.so.20 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libcogl.so.20
libOpenGL.so.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libOpenGL.so.0
libOpenGL.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libOpenGL.so
libGL.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libGL.so.1
libGL.so.1 (libc6) => /usr/lib/i386-linux-gnu/libGL.so.1
libGL.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libGL.so
libEGL.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libEGL.so.1
libEGL.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libEGL.so
~ glxinfo | grep OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 960/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 415.27
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6.0 NVIDIA 415.27
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 415.27
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:
@kisak-valve I think this should contain all the relevant info?
(also, FWIW glxgears works just fine)
There's a good chance you tested 64 bit glxgears, while Steam is 32 bit, and glxinfo/glxgears from mesa-utils:i386 would be a better way to check if the 32 bit opengl stack is sane.
In your case, please check if you have libnvidia-gl-415:i386 with something like apt policy libnvidia-gl-415:i386 and install it with sudo apt install libnvidia-gl-415:i386.
@kisak-valve that sorted it for me - I was just missing the 32-bit version of libnvidia-gl-415. The sudo apt install libnvidia-gl-415:i386 was what I needed, and the steam UI is up and doing the "updating steam" thing :tada:
I have the same issue as @waynew. What do I need to do if I have the following
sudo ldconfig -p | grep -i gl.so
libwayland-egl.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libwayland-egl.so.1
libcogl.so.20 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libcogl.so.20
libOpenGL.so.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libOpenGL.so.0
libOpenGL.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libOpenGL.so
libGL.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libGL.so.1
libGL.so.1 (libc6) => /usr/lib/i386-linux-gnu/libGL.so.1
libGL.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libGL.so
libEGL.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libEGL.so.1
libEGL.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libEGL.so
glxinfo | grep OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 1070/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 418.39
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6.0 NVIDIA 418.39
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 418.39
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:
I don't want to run sudo apt install libnvidia-gl-415:i386 if that not the right setting for me? (Sorry unix newb)
@mr-bjerre, in your case it would be libnvidia-gl-418:i386 to match the 418 driver series you're using.
Ah I see. Although I get
Package libnvidia-gl-418:i386 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or is only available from another source
However the following packages replace it:
libnvidia-common-418
E: Package 'libnvidia-gl-418:i386' has no installation candidate
There is an extra troubleshooting step, trying to run glxgears.
If glxgears does not run, then the problem is with your Linux installation.
If glxgears runs, then the problem is with Steam.
@mr-bjerre, checking again, 418.39 is a cuda release and it sounds like you've hit #5778.
Runs just fine. I have cuda 10 installed. That might be related?
➜ ~ nvidia-smi
Tue Apr 9 16:28:36 2019
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 418.39 Driver Version: 418.39 CUDA Version: 10.1 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 1070 On | 00000000:01:00.0 On | N/A |
| 0% 46C P0 34W / 200W | 536MiB / 8111MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 1897 G /usr/lib/xorg/Xorg 26MiB |
| 0 2192 G /usr/bin/gnome-shell 51MiB |
| 0 2896 G /usr/lib/xorg/Xorg 274MiB |
| 0 3024 G /usr/bin/gnome-shell 130MiB |
| 0 3440 G ...pycharm-professional/127/jre64/bin/java 3MiB |
| 0 3976 G ...quest-channel-token=6210645115698830410 46MiB |
+-----------------------------------------------------------------------------+
@TTimo sorry I couldn't answer sooner. Yes I used latest one on a clean system with and without updating it.
steam-launcher 1.0.0.61 is officially out, assuming this issue is fixed.
If steam doesn't work because you lack working OpenGL drivers, please open a different issue!
Still have the same problem with the latest steam client.
$ steam
tar: This does not look like a tar archive
xz: (stdin): File format not recognized
tar: Child returned status 1
tar: Error is not recoverable: exiting now
find: ‘/home/leimao/.steam/ubuntu12_32/steam-runtime’: No such file or directory
I was able to turn on the software for the first time, and I could see that steam was updating. After update, there is nothing happened.
Somehow mkdir /home/leimao/.steam/ubuntu12_32/steam-runtime fix the problem. But I got another problem later.
SteamUpdateUI: An X Error occurred
I followed the steps in comment-478062644 and the problem was not fixed. Instead, the app is stuck trying to update itself:
$ steam STEAM_DEBUG=1
Setting up Steam content in /home/patrick/.local/share/Steam
Running Steam on elementary 5.0 64-bit
STEAM_RUNTIME is enabled automatically
Pins potentially out-of-date, rebuilding...
Installing breakpad exception handler for appid(steam)/version(0)
I'll leave it for a few more hours just in case, but I'm quite sure at this point that nothing will happen.
Your system information
Please describe your issue in as much detail as possible:
Since installing Ubuntu a couple weeks ago, I've been trying multiple methods to get Steam to start. Whenever I click the icon in my app tray or try to start it via the terminal, it won't. Nothing shows up on my screen at all. After trying to start the app via the terminal, I got this error message:
Running Steam on ubuntu 18.04 64-bit STEAM_RUNTIME is enabled automatically Pins up-to-date! /home/hc259/.local/share/Steam/steam.sh: line 828: /home/hc259/.local/share/Steam/ubuntu12_32/steam-runtime/run.sh: No such file or directoryI completely purged Steam and its working folders, then tried to install again from the official .deb package.
Steps for reproducing this issue:
steam