Protontricks crash after selecting game

[PoisoN-Dieg0]

Describe the bug
Everytime I select a game the application crashes, I mainly execute the Protontricks via the menu and I never experienced this problem before.

To Reproduce

1. Open the application normally via the menu
2. Select a game

Expected behavior
Selecting the game and Protontricks giving me the WINE Prefix options.

System (please complete the following information):

• Distro: Linux Mint 22.3
• Protontricks installation method: Flatpak version via Mint's Software Manager
• Protontricks version: 1.14.0
• Steam version: Stable Client 1769025840

Additional context
The error message it displays when it crashes.

Protontricks was closed due to the following error:

Traceback (most recent call last):
  File "/app/lib/python3.13/site-packages/protontricks/cli/util.py", line 180, in wrapper
    return cli_func(self, *args, **kwargs)
  File "/app/lib/python3.13/site-packages/protontricks/cli/main.py", line 153, in main
    RunWinetricksGUICommand(args).execute()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/app/lib/python3.13/site-packages/protontricks/cli/command.py", line 98, in execute
    self.run()
    ~~~~~~~~^^
  File "/app/lib/python3.13/site-packages/protontricks/cli/main.py", line 200, in run
    run_command(
    ~~~~~~~~~~~^
        winetricks_path=self.winetricks_path,
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
        cwd=cwd
        ^^^^^^^
    )
    ^
  File "/app/lib/python3.13/site-packages/protontricks/util.py", line 667, in run_command
    raise RuntimeError(
    ...<2 lines>...
    )
RuntimeError: bwrap launcher crashed, returncode: 1


=============

Please include this entire error message when making a bug report.
Environment:

Protontricks version: 1.14.0
Is Flatpak sandbox: True
Is Steam Deck: False
Is SteamOS 3+: False

Log messages:

Found Steam directory at /home/docdieg0/.local/share/Steam
Running inside Flatpak sandbox, version 1.14.6.
Using default Steam Runtime at /home/docdieg0/.local/share/Steam/ubuntu12_32/steam-runtime
WINETRICKS environment variable is not available. Searching from $PATH.
Found 1 Steam library folders
Currently logged-in Steam user: poison_diego118
Found 0 Steam shortcuts running using Steam compatibility tools
Using 'yad' as GUI provider
User has configured app Proton version (CompatToolMapping): proton_9
User has configured default Proton version (CompatToolMapping): GE-Proton10-32
Found active compatibility tool: Proton 9.0
Active compatibility tool is a Proton installation
Using 'bwrap = True' as default value
Using separately installed Steam Runtime: Steam Linux Runtime 3.0 (sniper)
Running Steam Runtime using bwrap containerization.
If any problems arise, please try running the command again using the `--no-bwrap` flag and make an issue report if the problem only occurs when bwrap is in use.
Created Steam Runtime Wine binary directory at /home/docdieg0/.var/app/com.github.Matoking.protontricks/cache/protontricks/proton/Proton 9.0/bin
WINE environment variable is not available. Setting WINE environment variable to Proton bundled version.
WINESERVER environment variable is not available. Setting WINESERVER environment variable to Proton bundled version
Starting bwrap launcher process: /home/docdieg0/.var/app/com.github.Matoking.protontricks/cache/protontricks/proton/Proton 9.0/bin/bwrap-launcher
Terminating launcher process 5
Launcher process terminated

[Matoking]

Could you try running Protontricks from the command-line using the following command? The graphical dialog is not able to capture all log messages that occur, especially when they are related to Steam Runtime startup as seems to be the case here.

$ flatpak run com.github.Matoking.protontricks -vv --gui

This will print plenty of logs, so you'll want to use gist.github.com to upload them instead of pasting them into the reply directly.

Since you're on Linux Mint (Debian/Ubuntu derivative), I guess AppArmor related issues might be to blame? This would be indicated by pressure-vessel-wrap[5]: E: linkat: No such file or directory or a similar line in the logs.

[PoisoN-Dieg0]

Sure, here's the gist: https://gist.github.com/PoisoN-Dieg0/a9088a98a4da89003d0a42f9a7d59b7e

[Matoking]

Yes, the linkat: No such file or directory error most likely makes this a duplicate of #458, given that you're also running on an Ubuntu-derivative (Linux Mint).

I have not been able to reproduce the problem on Pop!_OS, which is what the other user was running.

Could you confirm the following?

• /etc/apparmor.d/flatpak file exists?
• Running sudo aa-status in a terminal while Protontricks is running (i.e. when the app selection dialog is still open) lists yad or python3.13 among the processes that "are unconfined but have a profile defined"? They should also list flatpak as the active profile, like so:

6 processes are unconfined but have a profile defined.
   ...
   /usr/bin/python3.13 (2683) flatpak
   /usr/bin/yad (2690) flatpak