-
Notifications
You must be signed in to change notification settings - Fork 37
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
crash upon selecting a game #314
Comments
it's also happens with the --no-bwrap |
Same issue on Linux Mint 22 |
Same issues for me as well I'm on Ubuntu 24.04 with latest protontricks version 1.11.1 via pipx installation. |
I seems to have got around the problem, by installing winetricks manually, see link for how to manually install it: https://github.com/Winetricks/winetricks?tab=readme-ov-file#manual-install and then using --no-bwrap flag. Still get some errors/warning but are able to do what I want to do. |
This could be related to this upstream Ubuntu issue. In short, an update to an Ubuntu security policy makes it too strict and prevents bwrap (which Protontricks uses unless Could someone who's affected try running |
Same error on Arch Linux |
Without --no-bwrap:
with --no-bwrap, I don't get journal entries. However, I do get:
This is using the latest pipx install for protontricks. It doesn't seem to matter at all what Proton version is selected. I can, in fact, launch games -- so the "file arch" problem is not related to whether or not Wine/Proton is actually working. However, this does work:
So I do not suspect a problem with winetricks. |
Yes, AppArmor security policy appears to be causing issues. The "Unknown file arch" Winetricks problem is tracked in Winetricks/winetricks#2183. In short, Protontricks creates wrapper scripts that launch Wine using the aforementioned Steam Runtime, as well as setting other settings for the environment. Winetricks didn't have a problem with this before, but it introduced a new check that attempts to determine the bitness of the Wine binaries; this fails since the executables added by Protontricks are not binaries at all. It's annoying, but you should be able to skip the errors. The bitness check has also been disabled in the Winetricks bundled with the Protontricks Flatpak for this reason. |
Having this issue on a steam deck where winetricks is not an option :/ |
What error message are you getting specifically? This error in particular is identified by the "bwrap launcher crashed, returncode: 1" message. The "Invalid file magic number" error which affects all Steam beta users is in #304, with a workaround described in the same issue. |
Apologies, I was on the wrong issue. I had the magic number error and needed to downgrade from Steam beta. |
Describe the bug
crash due to a nonexisting directory or I don't know.
To Reproduce
Steps to reproduce the behavior:
Selecting a game in the gui or running any command with a game for example: "protontricks 123 xna40"
Expected behavior
With the GUI version a new Window. with the cli version executing the expected commands
System (please complete the following information):
Additional context
If the error happens when trying to run a Protontricks command, run the command again using the
-vv
flag and copy the output!protontricks 855860 xna40 -vw
pressure-vessel-wrap[9]: E: linkat: No such file or directory
Traceback (most recent call last):
File "/app/bin/protontricks", line 8, in
sys.exit(cli())
^^^^^
File "/app/lib/python3.11/site-packages/protontricks/cli/main.py", line 32, in cli
main(args)
File "/app/lib/python3.11/site-packages/protontricks/cli/util.py", line 159, in wrapper
return cli_func(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/lib/python3.11/site-packages/protontricks/cli/main.py", line 370, in main
returncode = run_command(
^^^^^^^^^^^^
File "/app/lib/python3.11/site-packages/protontricks/util.py", line 516, in run_command
raise RuntimeError(
RuntimeError: bwrap launcher crashed, returncode: 1
the log from the gui:
Protontricks was closed due to the following error:
Traceback (most recent call last):
File "/app/lib/python3.11/site-packages/protontricks/cli/util.py", line 159, in wrapper
return cli_func(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/lib/python3.11/site-packages/protontricks/cli/main.py", line 290, in main
run_command(
File "/app/lib/python3.11/site-packages/protontricks/util.py", line 516, in run_command
raise RuntimeError(
RuntimeError: bwrap launcher crashed, returncode: 1
=============
Please include this entire error message when making a bug report.
Log messages:
Running inside Flatpak sandbox, version 1.14.6.
Found Steam directory at /home/thememe/.local/share/Steam
Using default Steam Runtime at /home/thememe/.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: josephss242
Couldn't find custom shortcuts. Maybe none have been created yet?
Using 'yad' as GUI provider
User has configured app Proton version (CompatToolMapping): proton_9
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/thememe/.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/thememe/.var/app/com.github.Matoking.protontricks/cache/protontricks/proton/Proton 9.0/bin/bwrap-launcher
Terminating launcher process 14
Launcher process terminated
The text was updated successfully, but these errors were encountered: