Sudden problems with several Steam-games on Ubuntu 20.04 (using Radeon graphics card)

[[kjøttkake] ElToro]

I suddenly have problems with several games on the Steam platform. I am running Steam on Ubuntu 20.04, and I have a Radeon RX 5600 graphics card. When I start the Steam-client in a terminal and then start a game - say, Insurgency or War Thunder - - from the client, steam starts processing shaders but the game does not start. I typically get the following:

Game update: AppID 222880 "", ProcID 12474, IP 0.0.0.0:0
ERROR: ld.so: object '/home/eric/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Starting app 222880
>>> Adding process 12474 for game ID 222880
GameAction [AppID 222880, ActionID 1] : LaunchApp changed task to WaitingGameWindow with ""
ERROR: ld.so: object '/home/eric/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
pid 12477 != 12476, skipping destruction (fork without exec?)
ERROR: ld.so: object '/home/eric/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/eric/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/eric/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
GameAction [AppID 222880, ActionID 1] : LaunchApp changed task to Completed with ""
>>> Adding process 12475 for game ID 222880
>>> Adding process 12476 for game ID 222880
>>> Adding process 12478 for game ID 222880
>>> Adding process 12479 for game ID 222880
>>> Adding process 12480 for game ID 222880
libGL error: MESA-LOADER: failed to open radeonsi: /usr/lib/dri/radeonsi_dri.so: wrong ELF class: ELFCLASS64 (search paths /usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libGL error: failed to load driver: radeonsi
libGL error: MESA-LOADER: failed to open radeonsi: /usr/lib/dri/radeonsi_dri.so: wrong ELF class: ELFCLASS64 (search paths /usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libGL error: failed to load driver: radeonsi
libGL error: MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libGL error: failed to load driver: swrast
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 152 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Value in failed request: 0x0
Serial number of failed request: 89
Current serial number in output stream: 90

I believe all of it started after the latest Ubuntu update, but I am not sure about that. Note that some games do start, like Civilization IV.

Any help greatly appreciated.

[class101 [OLED deck]]

libGL error: MESA-LOADER: failed to open radeonsi: /usr/lib/dri/radeonsi_dri.so: wrong ELF class: ELFCLASS64

means the game attempted to load a 32-bit driver but only found 64-bit version on your system

your system upgrade probably reverted changes you have made to your system to retrieve 32-bit libraries

not ubuntu user here but I'm sure peoples around can help you to restore this

[Marlock]

sudo dpkg --add-architecture i386 
sudo add-apt-repository ppa:kisak/kisak-mesa
sudo apt update
sudo apt upgrade
sudo apt install libgl1-mesa-dri:i386 mesa-vulkan-drivers mesa-vulkan-drivers:i386

adding the ppa is optional but probably worth it (step marked in bold) because it provides the latest stable version of Mesa (including the AMDGPU opensource driver) and t
your gpu is quite recent so there is likely a lot of relevant improvements

the rest is all meant to ensure support for 32-bit is enabled and that you have the necessary opengl and vulkan libs in both 64-bit and 32-bit


other than that, you should try to boot the system over linux kernel 5.4.x (default out-of-the-box branch for Ubuntu 20.04) and over 5.8.x (afaik the latest stable branch offered by Ubuntu through normal means)... some people have been reporting issues on 5.8, but on the other hand it might offer more modern support for the gpu too

[[kjøttkake] ElToro]

Thanks, @Marlock and @class101. Added the ppa and downloaded libgl1-mesa-dri:i386 mesa-vulkan-drivers, and mesa-vulkan-drivers:i386. I am one step further, I think. But games still won't launch. Now, when I press play I get

GameAction [AppID 222880, ActionID 1] : LaunchApp changed task to ProcessingInstallScript with ""
GameAction [AppID 222880, ActionID 1] : LaunchApp changed task to SynchronizingCloud with ""
GameAction [AppID 222880, ActionID 1] : LaunchApp changed task to ProcessingShaderCache with ""

And there it gets stuck on Vulkan shader processing. I tried to alter the Steam settings to unable shader pre-caching (and background processing of Vulkan shaders). However, that gets me:
GameAction [AppID 222880, ActionID 2] : LaunchApp changed task to Completed with ""
>>> Adding process 16309 for game ID 222880
>>> Adding process 16311 for game ID 222880
>>> Adding process 16312 for game ID 222880
>>> Adding process 16313 for game ID 222880
libGL error: MESA-LOADER: failed to open radeonsi: /usr/lib/dri/radeonsi_dri.so: wrong ELF class: ELFCLASS64 (search paths /usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libGL error: failed to load driver: radeonsi
libGL error: MESA-LOADER: failed to open radeonsi: /usr/lib/dri/radeonsi_dri.so: wrong ELF class: ELFCLASS64 (search paths /usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libGL error: failed to load driver: radeonsi
libGL error: MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libGL error: failed to load driver: swrast
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 152 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Value in failed request: 0x0
Serial number of failed request: 89
Current serial number in output stream: 90
Game removed: AppID 222880 "", ProcID 16307
Uploaded AppInterfaceStats to Steam
Exiting app 222880

Looks like I am damned if I do, and damned if I don't enable shader pre-caching.

[[kjøttkake] ElToro]

As for falling back to earlier kernels; I am already on 62, and I can only fall back to 60. Tried that, but gave me exactly the same result as for 62.

[class101 [OLED deck]]

really have no idea, from the log file it is obvious to me insurgency is 32-bit and is attempting to load a 64-bit driver but since I'm on Arch Linux can't help you much and don't want to break your system with wrong directions. On Arch it is as simple as uncommenting two lines in pacman.conf file to enable 32-bit support maybe you want to switch to it :P

[Marlock]

what i meant by using a different version of the linux kernel was switching between 5.4.latest and 5.8.latest, not between 5.4.60 and 5.4.62 (or 5.8.60 and 5.8.62 if that's the case)... did you try that as well?

on linux mint the Updates Manager has a dedicated gui for managing linux kernel versions, and everything listed there comes from Ubuntu Kernels repo directly (for Ubuntu 20.04 in the case of LM 20, which is what I use), so I know you have 5.4 and 5.8 available... I'm just not sure how this is managed on ubuntu itself, but IIRC the 5.8.x kernel was considered what ubuntu calls HWE (hardware enablement)? googling how to install linux kernel on ubuntu should yield easy some methods (but probably you should ignore links about UKUU, as it's no longer FOSS)

[Marlock]

as for the error message, i believe the correct interpretation there is that vulkan 64 bit is available so steam tries to use it but fails due to wrong bitness (should be 32bit but tried 64bit) and that it didn't even try the 32bit version... it would be normal behavior to see it trying one and failing, then trying the other and succeeding, but it skips right to SWRAST (CPU-based software rendering) instead...

[Marlock]

are you using steam from flatpak, by any chance?

Civ VI is a native linux game with 64-bit support, so it makes sense that it works in all circumstances... means the 64-bit vulkan stuff is A-OK

can you try to install / update / uninstall+reinstall "Steam Runtimes for Linux - Soldier" from Library > Tools?

then try any failing native linux games and/or proton 5.13 again...

conversely, try older proton (5.0 and older) with windows games... these didn't use soldier like 5.13 does

[[kjøttkake] ElToro]

"vulkan 64 bit is available so steam tries to use it but fails due to wrong bitness (should be 32bit but tried 64bit) and that it didn't even try the 32bit version... it would be normal behavior to see it trying one and failing, then trying the other and succeeding, but it skips right to SWRAST (CPU-based software rendering) instead... " Hmm... Sounds like I should bug report this to Steam(?)

[[kjøttkake] ElToro]

"are you using steam from flatpak, by any chance?" Don't remember. Think so...

Eh... "can you try to install / update / uninstall+reinstall "Steam Runtimes for Linux - Soldier" from Library > Tools?" In Steam? There isn't any Tools-choice under the Library-menu... Or do you mean something else?

[[kjøttkake] ElToro]

"what i meant by using a different version of the linux kernel was switching between 5.4.latest and 5.8.latest, not between 5.4.60 and 5.4.62 (or 5.8.60 and 5.8.62 if that's the case)... did you try that as well?" Nope. Since I don't have those accessible at startup, I haven't tried that yet. Not sure how to fall back all the way to 5.4... Will look into it.

[Marlock]

in the library, on the top left there is a tiny filter set to Games by default, but you can mark Tools, Software, etc on a droplist if you click it

[Marlock]

skipping right to swrast is expected if the 32-bit libs aren't available... you said you installed them, but the install might be broken somehow, or innacessible to steam for some reason... in those cases, it is not a bug on steam itself, just a bad setup on your machine...

that is why I asked about flatpak, because it runs steam in a sandbox with a set of libs separate from the base OS libs...

...and also why I mentioned Soldier, because the game is sandboxed with a steam-provided set of libs instead of the base OS libs... though afaik the gpu driver, opengl and vulkan are all still the base OS ones, maybe there is some broken intermediary (i'm not familiar with how they implemented Soldier, so I'm guessing either way... it's worth checking out since there where several people with issues as soon as soldier came out)

[WarnerCK]

Originally posted by ElTorobeltalowda:

Since I don't have those accessible at startup, I haven't tried that yet. Not sure how to fall back all the way to 5.4.

You'd install the linux-generic package.

[[kjøttkake] ElToro]

@Marlock, reinstalled Soldier, but to no avail. However, the flatpak-solution worked! Thanks!