#183 changed the launcher to open a separate SMAPI terminal on Linux/Mac, matching the behaviour on Windows. This caused an issue where some Linux users couldn't launch SMAPI through Steam, which was mostly fixed by #198 (by launching without a terminal if the terminal returned 127 command-not-found).

The SMAPI terminal launch still fails for one user on the forums, but the reason for that is unclear.

I created a custom launcher which logs more information about the launch process.

• ✓ Log for a GOG user (no issue):

  invoked as ./StardewValley 
  detected Linux (uname=Linux, arch=x86_64)
  selected launcher: ./StardewModdingAPI.bin.x86_64 
  selected command: command -v
  launching terminal: x-terminal-emulator
  terminal launch exit code: 0
  

• ✓ Log for a Steam user affected by the command-not-found issue (see #198):

  invoked as /home/ledah/.local/share/Steam/steamapps/common/Stardew Valley/StardewValley STEAM_RUNTIME=0
  detected Linux (uname=Linux, arch=x86_64)
  selected launcher: ./StardewModdingAPI.bin.x86_64 STEAM_RUNTIME=0
  selected command: command -v
  launching terminal: x-terminal-emulator
  terminal launch exit code: 127
  

• ✘ Log from @nirasa1957 on the forums, who can't launch the game through Steam (but it works fine if launched directly):

   invoked as /home/irenas/.local/share/Steam/steamapps/common/Stardew Valley/StardewValley STEAM_RUNTIME=0
   detected Linux (uname=Linux, arch=x86_64)
   selected launcher: ./StardewModdingAPI.bin.x86_64 STEAM_RUNTIME=0
   selected command: command -v
   launching terminal: x-terminal-emulator
   terminal launch exit code: 1
  

Apparently fixed with Stardew Valley 1.2 beta and SMAPI 1.9 beta.