Closed issue by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/46649

Description:
### Is this a new report?

Yes

### System Info

Void 6.1.55_2 x86_64 GenuineIntel uptodate rFFFF

### Package(s) Affected

`steam-1.0.0.78_3`  | `com.valvesoftware.Steam 1.0.0.78 (Flatpak)`

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

Some similar bugs, although with varying differences in the matter of hardware configuration and packaged software:

https://github.com/ValveSoftware/steam-for-linux/issues/9630
https://github.com/ValveSoftware/steam-for-linux/issues/9383
https://github.com/ValveSoftware/steam-for-linux/issues/9984
https://github.com/ValveSoftware/steam-for-linux/issues/10001
https://github.com/ValveSoftware/steam-for-linux/issues/8667
https://github.com/ValveSoftware/steam-runtime/issues/403
https://github.com/ValveSoftware/steam-for-linux/issues/9077

Definitively, https://github.com/ValveSoftware/steam-for-linux/issues/10001 is the most similar, though. 

There may be, however, further Void-specific packaging concerns. 

### Expected behaviour

Recently Steam ( `steam-for-linux` ) has mainlined its newer beta GUI based upon the notorious https://www.electronjs.org/

It should allow for a newer HTML5-based & electron-based GUI, capable of supporting hardware acceleration, and a smoother user experience. 

### Actual behaviour

Attempting to launch Steam ( `steam-for-linux` ) results in the deployment of several electron-based and d-bus dependent processes (This seems intended), which however are unable to display any electron-based GUI of any kind. 

The application and its multiple resulting processes remain running, however there is no GUI-based window being drawn upon the display. 

The application is alive and well in the system tray, and can actually display its "settings" windows reliably. 
All other windows are however inaccessibile and/or otherwise invisible. 

No difference is reported whether with `steam-1.0.0.78_3` or `com.valvesoftware.Steam 1.0.0.78 (Flatpak)`. 

Relevant error log (Flatpak, but its `steam-1.0.0.78_3` equivalent is largely identical) is as follows:

`amdgpu_device_initialize: amdgpu_get_auth (1) failed (-1) amdgpu: amdgpu_device_initialize failed. libGL error: glx: failed to create dri3 screen libGL error: failed to load driver: radeonsi Steam Runtime Launch Service: starting steam-runtime-launcher-service Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 336 steam-runtime-launcher-service[336]: E: Unable to acquire bus name "com.steampowered.PressureVessel.LaunchAlongsideSteam" amdgpu_device_initialize: amdgpu_get_auth (1) failed (-1) amdgpu: amdgpu_device_initialize failed. libGL error: glx: failed to create dri3 screen libGL error: failed to load driver: radeonsi`

The dbus error seems relatively innocuos, thus I suspect the `failed to load driver: radeonsi` to be relevant insted. 

This happens on an AMD RX580 Video Card, upon a custom `sway-1.8.1_1`-based desktop. 

Workarounds suggested on exporting MESA variables do not appear to work.

### Steps to reproduce

1. You probably require a `radeonsi`-based GPU, and possibly a wayland-based desktop
2. Install `steam-for-linux` as `steam-1.0.0.78_3` or `com.valvesoftware.Steam 1.0.0.78 (Flatpak)`
3. Attempt to launch `steam-for-linux`, and be met with absent and/or invisible windows, despite the application being operative as processes and into the system tray. The window "settings" called from the system tray icon may be the only one to display somewhat reliably. Other windows may display on first attempt, and disappear thereafter. Sometimes, after clearing $HOME config, a black window may display for about two minutes before disappearing.