Steamtinkerlaunch Installing When Trying To Use CLI

[weir99]

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

$ Steamtinkerlaunch help

Preparing to install SteamTinkerLaunch on SteamDeck
Downloading latest SteamTinkerLaunch
…

To Reproduce
Steps to reproduce the behavior:

1. Install Steamtinkerlaunch 12.12 via ProtonUp-Qt
2. Reboot
3. Run Steamtinkerlaunch command from command line

Expected behavior
It just runs without installing every time.

Desktop (please complete the following information):

• Platform: Steam Deck
• System: SteamOS 3.5.17
• Version: ProtonUp-Qt 2.9.1
• How did you install ProtonUp-Qt?: Flatpak on Discover App Sotre

Additional context
Add any other context about the problem here.

Terminal output

(deck@steamdeck ~)$ flatpak run net.davidotek.pupgui2
ProtonUp-Qt 2.9.1 by DavidoTek. Build Info: DavidoTek Flathub build.
Python 3.10.13 (main, Nov 10 2011, 15:00:00) [GCC 12.2.0], PySide 6.5.2
Platform: KDE Flatpak runtime 6.5 Linux-6.1.52-valve16-1-neptune-61-x86_64-with-glibc2.35
Qt: Session management error: Could not open network socket
Loading locale en / en_US
Loaded ctmod GE-Proton
Loaded ctmod Wine-GE
Loaded ctmod Boxtron
Loaded ctmod D8VK (nightly)
Loaded ctmod Kron4ek Wine-Builds Vanilla
Loaded ctmod Lutris-Wine
Loaded ctmod Luxtorpeda
Loaded ctmod Northstar Proton (Titanfall 2)
Loaded ctmod Proton Tkg
Loaded ctmod Proton Tkg (Wine Master)
Loaded ctmod Roberta
Loaded ctmod Steam-Play-None
Loaded ctmod SteamTinkerLaunch
Loaded ctmod SteamTinkerLaunch-git
Loaded ctmod vkd3d-lutris
Loaded ctmod vkd3d-proton
Loaded ctmod Wine Tkg (Valve Wine)
Loaded ctmod Wine Tkg (Vanilla Wine)
Loaded ctmod DXVK
Loaded ctmod DXVK Async
Loaded ctmod DXVK (nightly)
qt.pysideplugin: Environment variable PYSIDE_DESIGNER_PLUGINS is not set, bailing out.
qt.pysideplugin: No instance of QPyDesignerCustomWidgetCollection was found.
Gamepad error: No gamepad found

[sonic2kk]

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 👋).

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.

[weir99]

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