So weird - I've been having a hard time figuring out why
#StardewValley would not run on my partner's
#Linux PC when modded. Her mod setup's the exact same on her
#SteamDeck and mine/all my other devices and they all worked fine except her PC.
I would hit play, and nothing would happen other than the button (on #Steam) turns to stop and back to play again. I assumed it just crashed before being able to spawn anything i.e. game window, or
#SMAPI terminal, but still weird cos there are no logs whatsoever.
I initially thought maybe gamemode or #MangoHud was causing the issue but the issue persists even after removing those from the game's launch option - also they worked fine on any of her other games, including SV when not modded.
In the end the issue was what I had not expected - SMAPI, requires a terminal it uses to spawn/launch itself, and the command that does so I specifically remember lists down pretty much all terminals it could use under the sun in case one isn't installed. The first if I'm not mistaken is #Xterm, which I'm sure is the one SMAPI normally uses on all of our other devices. Xterm isn't installed on my partner's PC, but there are plenty on the list SMAPI could've used such as
#Alacritty and ofc, the default,
#Konsole. I was sure this shouldn't be the issue, but as I ran out of other things to try, I installed Xterm and modded SV via SMAPI magically works again.
I'll have to look into this further when it's not 4am lol.
Update:
I suspect SMAPI's list/order for the terminal to use should work, I see no reason why it wouldn't, but perhaps the issue lies in whatever terminal it did reach for next (which should be Konsole, in said list on my partner's machine) wasn't compatible with SMAPI somehow - which caused it to just not launch. This is a known possibility, hence why SMAPI prefers and prioritises Xterm, which often comes preinstalled on most Linux machines.
🔗
https://github.com/Pathoschild/SMAPI/issues/695#issuecomment-610147802