New comment by atvexy on void-packages repository

https://github.com/void-linux/void-packages/issues/41388#issuecomment-1947357310

Comment:
i not sure if anyone has found a way (apart from Flatpaks) to launch eac successfully so i'm just posting this here in case it could lead to the root cause.

I found a way to launch vrchat successfully by forcing steam to run the game outside of it's "Steam Linux Runtime 3.0 (Sniper)" wrapper using vrchats launch options in steam. 

When you launch the game normally and watch steam clients output for the launch command it will be some form of `<steam path>/reaper -- <steam path>/steam-launch-wrapper -- <linux runtime path>/_v2-entry-point -- <proton path>/proton <vrchat path>/launch.exe`

This way vrchat fails to connect with eac and quits. When you copy the command and **remove** the Steam Runtime wrapper however (removing the `_v2-entry-point` while leaving the `reaper` and `steam-launch-wrapper`) and put the full command steam launch options (eg. `<steam path>/reaper -- <steam path>/steam-launch-wrapper -- <proton path>/proton <vrc path>/launch.exe # %command%`) the game and eac launches successfully.

This is a scuffed setup but it must likely rules out glibc from being the problem. It seams there's an issue when running an eac game inside the steam runtime as vrc couldn't even detect eac while its service was running in the background (logging `[AntiCheatClient] Anti-cheat client not available. Verify that the game was started using the anti-cheat bootstrapper if you intend to use it.`)