search

Matoking / protontricks

A wrapper that does winetricks things for Proton enabled games, requires Winetricks.
GNU General Public License v3.0
1.69k stars 37 forks source link

Cannot start protontricks #361

Open Violet-RM opened 1 week ago

Violet-RM commented 1 week ago

Describe the bug A clear and concise description of what the bug is. Protontricks is a dependency of an install script for Mod Organizer 2. I've been tearing my hair out trying to get this to work but its refusing to. I run it and it comes up with a protontricks error, and when i just try running protontricks outside of the script, I receive a similar error. Any help would be appreciated.

This seems to be similar to #304 but that seems to have been fixed in the current version, so I'm not sure if this is related.

To Reproduce Steps to reproduce the behavior:

  1. Run install.sh from https://github.com/rockerbacon/modorganizer2-linux-installer
  2. Select a game
  3. Command fails and error is displayed OR
  4. Run command protontricks
  5. Select a game
  6. Command fails and error is displayed

Expected behavior A clear and concise description of what you expected to happen.

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!

For example, if the command that causes the error is protontricks 42 faudio, run protontricks -vv 42 faudio instead and copy the output here.

If the output is very long, consider creating a gist using gist.github.com. https://gist.github.com/Violet-RM/4f2c6e1b3d37ada4dff3b16f1fb4749f https://gist.github.com/Violet-RM/8f264c54ebf0fae2381a96d7fe47aa1f

Matoking commented 1 week ago

It seems like Protontricks is passing the execution to pressure-vessel command correctly, but it's failing in turn due to the "error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory" error.

There are already several bug reports for this, but they all appear that they should be fixed:

Can you try running Protontricks again with the -vv flag so that more detailed debug logs are produced? There might be some additional context that is lost. protontricks -vv --gui should work, just ensure that you copy the output from the terminal, not the error dialog from Protontricks; the former can contain bwrap-launcher related logs that Protontricks itself can't capture and might prove useful here.

Violet-RM commented 1 week ago

To be frank, i do not know how to pass -vv to protontricks when its being run as a flatpak, flatpak run com.github.Matoking.protontricks --gui -vv just tells me it doesnt know what -vv is. This is for all flags so I assume its just user error and a flatpak thing. I'd use Debians native package but the powers that be don't have the latest version (which I need) in testing or sid.

Matoking commented 1 week ago

To be frank, i do not know how to pass -vv to protontricks when its being run as a flatpak, flatpak run com.github.Matoking.protontricks --gui -vv just tells me it doesnt know what -vv is. This is for all flags so I assume its just user error and a flatpak thing. I'd use Debians native package but the powers that be don't have the latest version (which I need) in testing or sid.

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

should work. Are you sure you have only one dash before vv? You also need Protontricks 1.11.0, though 1.12.0 should be installed given that it's required for Protontricks to work with the latest stable Steam client.

Violet-RM commented 1 week ago

well, that worked. it ran normally when i copy pasted that, but afterwards i opened a new shell to run it without -vv and it gave the same error as the gist i sent the other day. strange

sorry about the delay, heres the output of -vv https://gist.github.com/Violet-RM/b2b8e350df678cfc9d389c6c844917e1

Violet-RM commented 1 week ago

and when i say that worked, i mean the program ran normally and didnt abort on its own