The game, in general, works very well.
But I keep having crash to desktop errors with the follow message waiting for me at the terminal.


> support/gog_com.shlib: line 199: 5874 Aborted ./"${bin_64}"


The crash to desktop has so far only happened when going from rocket design to the launch pad (crashes somewhere during the load screen).

I am able to launch a few rockets (2 to 5 seems about right) before that happens though.

Any suggestions would be appreciated. I can also provide additional/refined details later if needed.

Rough System Specs:
Debian Jessie (w/ Openbox and Tint2 for desktop)
AMD Phenom 2 x4 945
8 gig ram
Crossfire 6870's (running AMD drivers, I think 14.1)
Kerbal Version 1.0

The error seems to come from a 64bit library. Are you able to launch your game in 32bit? (not sure if there's a 32bit ksp version in linux)

did you check the log files? maybe they can give a clue

there are two of them:
Player.log, which can be found here:
~/.config/unity3d/Squad/Kerbal Space Program

KSP.log, which should be in the game\ sub-directory in the folder where you unpacked KSP.

I am having the same crashes (also using Debian - but already updated to the new testing).
However, when using the launch option it works fine.
For doing that, either use the launcher application for that, or if you are starting the application via terminal, add "-l" (small L) to the command, e.g:
"gog-kerbal-space-program -l"

Hope that helped!

Edit: Game specs say "Notice: this game comes with a 32-bit binary only " ;-)

i think the launcher starts the 32bit executable, right?
that would indicate that the problem is indeed the 64bit version.
Does it work as well if you run the KSP.x86 ?

//edit:
nvm
just checked the start.sh from GOG, and they always launch KSP.x86, even on a 64bit platform.
so this crashed wasn't happening in the 64bit executable.

hmm, weird that it works when launched via the launcher.
still would be interesting if you can launch the game directly, not via gog's launcher. Just go to the game directory and launch the KSP.x86 or KSP.x86_64

(Sorry for my late response. Was fighting something over the weekend)

I was starting the program with "bash start.sh" from within the Kerbal directory. Clearly, that was not correct.
A bit strange that the start.sh script calls on x64 when the game doesn't support it.


In any case, thank you for responding.
I haven't had a crash yet by launching either Launcher.x86 of KSP.x86 from the /game directory.

For some reason, unlike my Don't Starve game (from tarball), I don't appear to have a "gog-kerbal-space-program" entry to call. Not sure what I did wrong on that one.

I'll update if another crash like the one before happens, but so far so good.

There seems to be a problem with your environment variable.
How did you install KSP? Via tarball or using dpkg and the *.deb file?
If you used the tarball, try using dpkg.
Otherwise you can edit your .bashrc (in your home directory) and add
"export PATH=$PATH:/usr/games"
at the end of the file.
Of course without the "
And make sure that /usr/games/gog-kerbal-space-program does exist.

You will probably need to re-login to your system to see changes, or run "bash" from commandline before executing gog-kerbal-space-program

no, that is correct and it should work.
That it doesn't work means there is a bug somewhere in the way the game was packaged.
Given that it works if you launch the game directly, there is most likely some incompatibility between the bundled libraries and your (new) debian version.
However, since debian isn't officially supported, i am not sure that the support will do much here. it is actually the other way around. The script always calls the x86 binary, even on a x64 platform. (at least the one the comes within the .deb package)
you could definitly try and launch the KSP.x86_64 directly.
Once you start adding mods the 64bit version really shines.

I extracted the programs with the tarballs. Given what I've recently learned about what is in the gog-kerbal-space-program (simple script calling the location of the start.sh) I understand why it's missing. Since I'll probably be installing my games in a different location than most installers, I'll make them manually or update a location as you suggested. Thanks for that. Good point that I downplayed, I'm sure this game would have worked without a hitch in the supported OSes. I just updated (with tarball) to 1.0.2. So I will be giving that a shot using the start.sh script. Should it crash, I'll update the thread and move to trying the KSP.x86_64 as my launcher.

... oh geez, mods. Nearly forgot about them. Mods are the reason I STILL haven't finished Oblivion. So many mods to try.... and then my system needs moar powar.... viscous cycle :)

Lets update this thread.

Linux x64 GOG 1.0.5 KSP is pretty stable on Debian and like.