Closed weir99 closed 3 months ago
This isn't a ProtonUp-Qt bug, as #352 explains (there is also a wiki page). For future reference, issues when using specific compatibility tools should be reported on their corresponding upstream channels. In the case of SteamTinkerLaunch, that would be sonic2kk/steamtinkerlauch (hello :wave:).
This also is not a SteamTinkerLaunch bug. This is just what happens when you use SteamTinkerLaunch on SteamOS. Keep in mind ProtonUp-Qt also serves the wider Linux Desktop, and for SteamTinkerLaunch, SteamOS is probably not going to be officially supported for much longer due to lack of community support (I have been asking for contributions for nearly a year with zero uptake, sonic2kk/steamtinkerlaunch#859).
No bug here, not sure why it would even be considered a bug... If you would like to see a change in behaviour, someone will have to submit a PR for it. But this is currently by design right now.
I couldn’t find this behaviour well-documented anywhere, the closest I came to finding anything on it was in the SteamTinkerLaunch documentation, where it mentions checking for updates each time it runs, but I wasn’t sure if that was what I was seeing and it said installing via ProtonUp-Qt should avoid this, so I figured something with ProtonUp-Qt’s install broke, making it a bug
Thank you, have a good day
Describe the bug
Whenever I try to run any ‘steamtinkerlaunch’ commands from command line after installing STL via ProtonUp-Qt, I get messages about installing Steamtinkerlaunch before my command executes
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It just runs without installing every time.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
Terminal output