Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Steam pressure vessel might be a futur problem for MangoHUD #523

Closed
class101 opened this issue May 11, 2021 · 5 comments
Closed

Steam pressure vessel might be a futur problem for MangoHUD #523

class101 opened this issue May 11, 2021 · 5 comments

Comments

@class101
Copy link

class101 commented May 11, 2021

Hello guys,

Firstly, thank you for your work on MangoHUD this is a great project for the linux community :)

I wanted to have your attention on a possible issue, that you possibly haven't caught yet because it requires to run a Windows game under Proton of Steam for Linux, with the Steam Client Beta update with MangoHUD enabled.

I have opened the following issue here because I believe this is something the Valve's devs have to consider

ValveSoftware/steam-runtime#408

To resume briefly the problem, Steam's pressure vessel redirects every request made to the directory /usr/bin/ to the following one /pressure-vessel/usr/bin

So any executable present in /usr/bin/ but NOT in /pressure-vessel/usr/bin, will fail the C/C++ call to popen(), for instance glxinfo but the issue does not limit only to this executable, taking into accounts that pressure vessel can do this can probably save you from futur problems

Let me know if you need much informations

@stephanlachnit
Copy link
Contributor

The executable isn't the problem afaik.The problem are the Vulkan Layers and libraries.

@class101
Copy link
Author

class101 commented May 20, 2021

@stephanlachnit

There should be some technical restrictions under this decision I understand.

Anyway, thank you for your feedback, I have renamed the ticket anyway now to make it more clear there is a bug in MangoHUD with Steam Pressure Vessel, and it should be more search friendly like that :)

Steps to reproduce :

  • Install Steam
  • In Steam settings, select Steam Client Beta
  • (Not sure if running a Window game is a requirement to produce the error, if pressure vessel is used to run native game, then it should also happen in them too)
  • In Steam settings, enable latest Proton 6.3-4 version for all games
  • Add PROTON_LOG=1 mangohud %command% as launch option on a Windows game
  • Run the Windows game
  • Open at the file in /home/$USER/steam-APPID.log for reading

Notice the following error is shown

MANGOHUD: recreating font image
sh: 1: glxinfo: not found

Attempting to create a symbolic link of /usr/bin/glxinfo into /home/${USER}/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier/var/deploy-0.20210415.0/files/bin produces the following error

MANGOHUD: recreating font image
sh: 1: glxinfo: Too many levels of symbolic links

The only way I have found to fix was to copy /usr/bin/glxinfo inside the SteamLinuxRuntime_soldier directory

@stephanlachnit
Copy link
Contributor

If you use recent proton versions, you should use MANGOHUD=1 %command% and it should work fine. The executable won't work (and so do OpenGL games for that matter).

@class101
Copy link
Author

Ho thank you I didn't know this trick :)

@stephanlachnit
Copy link
Contributor

From #369 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants