-
Notifications
You must be signed in to change notification settings - Fork 43
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
v0.4 Issue - Launch button does not seem to work (Linux, Steam) #1151
Comments
Are you on Windows or on Linux? Also, can you attach some logs? Windows: |
I do not see anything in the log that would suggest a problem... I could run a dev build or run in debug mode or something if you needed it though |
You can try running this command manually: xdg-open steam://rungameid/413150 On Linux, we currently only support running the game through Steam. The only thing the launch button does is run the command above. NexusMods.App/src/Abstractions/NexusMods.Abstractions.Games/RunGameTool.cs Lines 116 to 142 in 5be72d2
|
@Slayer5934 can you try one of the latest builds at https://github.com/Nexus-Mods/NexusMods.App/actions/runs/8551545718 and check the logs afterwards? |
i will see |
same result, i see the launcher did try running the command, nothing happened |
It looks like we tried to start the process and then waited for a minute for it to start. For some reason, either |
I've got a PR #1206 open that should improve this, or at least give us more information. |
Can you try running https://github.com/Nexus-Mods/NexusMods.App/actions/runs/8646672224 |
nexusmods.app.main.current.log SystemJournal.txt |
@Slayer5934 looks like debug logging wasn't enabled. I've fixed that here: https://github.com/Nexus-Mods/NexusMods.App/actions/runs/8687979869 Can you explain what actually happens on screen? What's supposed to happen is,
|
I will download and run the new one, |
I think that Just be sure, running |
@Slayer5934 can you run the following commands in your terminal:
|
|
#1151 (comment) @l0b0 can you run these commands as well? |
I think you meant ❯ echo $SHELL
/run/current-system/sw/bin/bash
❯ which disown
which: no disown in (/nix/store/[omitted giant PATH])
❯ type disown
disown is a shell builtin
❯ which xdg-open
/run/current-system/sw/bin/xdg-open
❯ xdg-open --version
xdg-open 1.2.1 |
@l0b0 and @Slayer5934 how did you install Steam? Did you use flatpak, your system package manager, or something else? Also, can you check if links in diagnostics or in the changelog are clickable? This might either be an issue with how we use I'm really perplexed by this issue because If there isn't anything obvious that we've somehow missed, I'll probably rework how we do this entirely. |
I basically just set
The test process:
CLI logs:
Doesn't I'll try to upgrade to v0.5 to see if that changes anything. |
I'm presuming it tried to start a Windows binary as a regular Linux one, but Wine is not present or set as the default handler, i.e. More importantly, I'd guess we're probably not handling running of tools (SKSE) via a WINEPREFIX, regardless of whether we need to run it via Proton or Wine. That's a problem yet to be resolved. Skyrim is also currently unsupported and hasn't been touched since an eternity ago. Try Stardew Valley for the time being, see how that goes. |
I don't have that game, so I don't think I'll be able to contribute much more to this issue. |
@l0b0 We inherit the environment variables from the environment the App is running in. If you're starting the App from the shell, then it would inherit all environment variables that are present in the current shell session. |
nexusmods.app.main.current.log I'm able to reproduce this on my Steam Deck, I think this is the correct log file. |
This issue might be fixed with #1533. |
Fixed with #1533, confirmed by two testers. |
Bug Report
Summary
When trying to launch Stardew the Launch button does not seem to work. It says Running... then eventually turns back to Launch.
Steps to reproduce
...
What is the expected behaviour?
It launches.
Other information
It is worth noting that I installed SMAPI (and other mods) outside of the Nexus Mods App before getting it.
I installed one mod, applied, then launched through steam directly and everything worked fine.
The text was updated successfully, but these errors were encountered: