Linux, as soon as I launch KSP (steam or binary), it does not respond, it does not get to the loading screen, and it does not create any logs.

[737]

Basically the title. Elementary OS 8.1 (Ubuntu 24.04 LTS based). Nvidia GTX 1650, i5-11400H, 16gb ram, Acer Nitro 5. It was running fine with parts mods before, then I pressed ctrl alt f12 because I wanted to access the cheats menu, it led to some non graphical command line, I had to restart, and when I opened KSP it just didn't open or create any logs. I backed up my save, my mods, and I re installed stock KSP, and that doesn't start either. It just opens a window with an image of the desktop/windows of the desktop before opening, and it doesn't respond, and it doesn't get to the loading screen. I ran it with ./KSP.x86_64, and the only output in terminal is:

Set current directory to /home/(mynameiscensored)/.local/share/Steam/steamapps/common/Kerbal Space Program
Found path: /home/(mynameiscensored)/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP.x86_64

and then even after waiting 10-15 minutes, nothing happens in the window or terminal except for a few prompts asking if I want to force quit it because it is not responding.

[737]

Restarted my laptop, and now it works. W

[Linkageless]

I'm glad to hear reboot cleared things up.

I'll guess that there may have been a temporary issue with your environment or window manager, or an issue getting file locks.  If this happens again, after confirming there's no other copy of KSP running, you can try running it from bash with strace, eg:

strace ./KSP.x86_64

Ordinarily, this will generate *a lot* of terminal output of system calls (startup with strace -o generates a ~51M file on my lightly modded install), but often we are only really interested in the last few lines assuming it hangs and does nothing more.  Logging strace output to file using -o is an option but slows things down and you'd probably be doing a tail -f on that anyway and ignore the rest.

It would also be interesting if you're seeing it constantly looping round generating the same calls over and over.  Either way make a note of where you end up in the system calls before killing the process off as elegantly as it will allow (ie - try kill -15 <pid> and give it a chance to clean up, before you resort to kill -9).

I note that the --single-instance option no longer seems to work (at least on my linux/steam install), but two instances wouldn't necessarily be the cause of such a problem so early on in startup..