-
Notifications
You must be signed in to change notification settings - Fork 10
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
Can't run wine binaries #72
Comments
I have not seen this issue before. Is there any other logs/terminal output that shows the issue? |
logs when I click start, it hides the launcher then reopens it after a couple seconds
when I try to run the command manually:
when I cd into the directory and ls:
This isn't an uncommon issue, if I download and run a binary that was compiled on another operating system this is what typically happens. I believe this is because when you compile a binary on nixos, many of the common libraries are linked to somewhere in /nix/store instead of wherever the binary expects them to be. Edit: nevermind, libraries are correctly found. I'm gonna keep debugging
|
What version of the launcher are you using? What version of Nixpkgs are you using? The entire launcher runs inside of a FHS bubblewrap sandbox (like steam does), so the library linking itself isn't the problem (though it is why wine64 isn't running from the command line). If you want to run wine64 from within FHS sandbox, run |
this does indeed work and yeah you're so right that it runs everything inside steam-run so I really have no idea why it's not launching. wine does correctly run when I run it with steam-run. Actually no clue what's happening |
I might have the same problem... I will try to debug as soon as I have some more time on my hands |
This is probably because they weren't compiled on nixos, but I can't run any of the wine/proton binaries. It says "required file not found" even though it successfully downloaded and the file is right there. Did you have the same issue? If so, how did you get around it
The text was updated successfully, but these errors were encountered: