proton-caller icon indicating copy to clipboard operation
proton-caller copied to clipboard

SteamLinuxRuntime_soldier pressure-vessel error

Open FlafyDev opened this issue 2 years ago • 3 comments

Describe the bug Getting a 127 error when starting any exe file.

[flafydev@nixos:~]$ proton-call -c "/mnt/general/SteamLibrary/steamapps/common/Proton 7.0" -r "/mnt/general/SteamLibrary/steamapps/common/BeFunnyNow/BeFunnyNow.exe"
/mnt/general/SteamLibrary/steamapps/common/SteamLinuxRuntime_soldier/pressure-vessel/bin/pressure-vessel-unruntime: line 162: /mnt/general/SteamLibrary/steamapps/common/SteamLinuxRuntime_soldier/pressure-vessel/bin/pressure-vessel-wrap: No such file or directory
proton-call: proton exited with: code: 127

To Reproduce Steps to reproduce the behavior:

  1. Get Proton Caller 3.1.0.
  2. Download Proton and Steam Linux Runtime - Soldier.
  3. Do proton-call -r "<any real directory or file>".

Expected behavior The exe file to start.

Desktop (please complete the following information):

  • OS: Linux - NixOS
  • Browser Firefox
  • Version Proton Caller (proton-call) 3.1.0 Copyright (C) 2021 Avery Murray <[email protected]>

Additional context Same thing happens with Steam Linux Runtime - sniper

Config:

data = "/home/flafydev/Documents/Proton/env/"
steam = "/home/flafydev/.steam/steam/"

# optional
common = "/mnt/general/SteamLibrary/steamapps/common/"

FlafyDev avatar Jun 30 '22 04:06 FlafyDev

Proton Caller is not made to run games available on Steam. It is made specifically to run applications and games not available on Steam. Enable Proton for all games in Steam's settings to run all non-linux native games through Steam.

caverym avatar Jul 05 '22 03:07 caverym

I am also getting this error. On NixOS as well...

zyansheep avatar Aug 18 '22 23:08 zyansheep

I also have this issue on NixOS. I have Proton enabled for all games, and I am trying to run a non-Steam EXE.

Pauan avatar Oct 12 '22 15:10 Pauan

Perhaps superfluous, but same issue here on NixOS. It works inside of steam-run, so this is probably a NixOS packaging issue.

Edit: Filed here

joepie91 avatar Oct 21 '22 20:10 joepie91