Melvyn
Melvyn
It might also be the combo of steam runtime and a downgraded talloc, in that case; I didn't test runtime with up-to-date talloc, but it didn't fix cs:go in native...
It would probably be easiest to start with passing through the tags from files that have them, and then figure out afterwards how to deal with files that jellyfin has...
Worked with a single typo in step 6: `phazor` not `phasor` Also the pyinstaller step does work, I get a standalone .app Thanks!
I can confirm that I have the same symptoms on Xwayland as that bug report, where unplugging it is required between every launch.
All of the z-ordering for steamvr overlays is inverted for me too, latest stable mesa + rx 580.
I had this issue since I re-enabled my iGPU, removing the intel-vulkan package solved it.
Last time I tried SteamVR on Wayland the same issue occured (Plasma/KWin however), so I think that steamvr simply does not support wayland for now.
When running linux directly, did steamvr work during a wayland session?
> Is there any way to resolve this by now? I'm using an AMD GPU without any integrated graphics and I have the same issue. are you on wayland?
For a late update, KDE Plasma beta 5.24 (aka 5.23.90) along with xwayland from git master works great for VR on wayland.