protontricks icon indicating copy to clipboard operation
protontricks copied to clipboard

bwrap issue with installing dlls

Open Jhopmemes opened this issue 9 months ago • 2 comments

Describe the bug Protontricks wont run at all. Brings up gui, but when a game is selected, it crashed and throws this error XXXX is where my directory is, I replaced it. "" pressure-vessel-wrap[7196]: E: Child process exited with code 1: bwrap: setting up uid map: Permission denied

Traceback (most recent call last): File "/home/XXXX/.local/bin/protontricks", line 8, in sys.exit(cli()) ^^^^^ File "/home/XXXX/.local/pipx/venvs/protontricks/lib/python3.12/site-packages/protontricks/cli/main.py", line 32, in cli main(args) File "/home/XXXX/.local/pipx/venvs/protontricks/lib/python3.12/site-packages/protontricks/cli/util.py", line 159, in wrapper return cli_func(self, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/XXXX/.local/pipx/venvs/protontricks/lib/python3.12/site-packages/protontricks/cli/main.py", line 311, in main run_command( File "/home/XXXX/.local/pipx/venvs/protontricks/lib/python3.12/site-packages/protontricks/util.py", line 516, in run_command raise RuntimeError( RuntimeError: bwrap launcher crashed, returncode: 1

""

To Reproduce

In terminal: protontricks 9420

or just bring up the protontricks gui and select a game.

Expected behavior It brought up a wine config screen, through which I could find a bunch of dlls for proton, such as xact or d3dx9.

System (please complete the following information):

  • Distro: Ubuntu 20.04, I think.
  • Protontricks installation method: pipx
  • Protontricks version: protontricks (1.12.0)
  • Steam version: whichever one was released on jan 28 Additional context

NVM, it worked with --no-bwrap I'm still going to create this issue so the bwrap=true can be fixed.

Also, I don't know shit about any of the technical stuff here, I just want to play Supreme Commander: Forged Alliance, so I do apologize if the info provided isn't helpful.

Jhopmemes avatar Feb 07 '25 22:02 Jhopmemes

I'm almost certain this is due to AppArmor being enabled in Ubuntu without the needed profile for Protontricks. I made an upstream bug report here, which should hopefully go toward solving the problem in the upstream package, though it unfortunately won't help with installations made using pipx.

In your case, though, you'll probably need to create an AppArmor profile manually. You can create a file under /etc/apparmor.d/protontricks-local with the following contents (replace XXXX with your username):

abi <abi/4.0>,
include <tunables/global>

profile protontricks /home/XXXX/.local/bin/protontricks{,-launch} flags=(unconfined) {
  userns,

  # Site-specific additions and overrides. See local/README for details.
  include if exists <local/protontricks>
}

and then try restarting AppArmor by running sudo systemctl apparmor. This can be fairly involved, unfortunately. You might have the easiest time creating the file by running the command sudo nano /etc/apparmor.d/protontricks-local in terminal, copying the configuration and then saving with Ctrl+X and Y.

Matoking avatar Feb 12 '25 17:02 Matoking

AFAICT it's complaining about a missing profile for bwrap, not protontricks. Adding a profile for bwrap did the trick on my end, while a profile for protontricks didn't seem to make a difference one way or the other.

alexrp avatar Feb 20 '25 00:02 alexrp