I'm running KSP 0.23 on Linux, with dev build 138 of MechJeb. When I start KSP, everything is "fine" until I go to VAB/SPH and load a design saved with the MechJeb AR202 part on it, at which point KSP does a hard crash and returns me to Steam. I can create a new ship, attach the AR202 part to it, and launch it without a problem, but if I then try to go back to VAB/SPH and reload that design, it will again cause a hard crash.

I tried going to the command line and launching KSP there to see if I could get any debug output, but KSP doesn't have sound, and it doesn't crash that way either. I can then load designs with the AR202 without crashing, but again, I don't have sound. If I then quit KSP and relaunch it directly from Steam, it begins crashing again.

Also, if I revert back to the public 2.1 release of MechJeb, I can again load designs containing the AR202 without KSP crashing, but of course that version of MJ isn't compatible with 0.23, so I can't actually use any of the MJ features. Again, as soon as I reinstall any of the 136 or newer dev builds, the crashes start happening again.

I can replicate all of the above on both existing save games as well as fresh saves.

Can anyone give me any hints on how to either launch KSP with sound from the command line, or to troubleshoot/fix the crashes I'm experiencing? Thanks

OS specific bug :(
Does 131 works ? Of the recent change the only thing that "may" break other OS is 137.
Or it's related to the "save" bug. But the fix was sent by Taniwha and I think he plays on linux too...

Can you put your KSP_DATA/output.log somewhere ?

There was no output.log in KSP_Data, but I do have a KSP.log file in the KSP root directory - http://pub.noswap.com/ksp/KSP.log - though it doesn't seem to say anything useful. Do I need to pass a special parameter to KSP to make it create output.log?

I'll try 131 when/if I get a chance tonight.

You could ruin it in a virtual machine... our off a uesc drive

This message was sent via phone. Please excuse any typos, as my phone loves
to 'autocorrect' to the wrong words.
On Dec 19, 2013 1:01 PM, "sarbian" [email protected] wrote:

I get that log all the time when I run on Windows.
Which distrib do you use and is it with the 32 or 64 build of KSP ? If we
don't resolve this tomorrow I'll re install linux on my gaming PC.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/256#issuecomment-30950968
.

I get that log all the time when I run on Windows.
Which distrib do you use and is it with the 32 or 64 build of KSP ? If we don't resolve this tomorrow I'll re install linux on my gaming PC.

I run 64 bit Arch Linux, but the normal x86 build of KSP, because the
x86_64 build core dumps any time I try to start or load a save game.
On Dec 19, 2013 10:01 AM, "sarbian" [email protected] wrote:

I get that log all the time when I run on Windows.
Which distrib do you use and is it with the 32 or 64 build of KSP ? If we
don't resolve this tomorrow I'll re install linux on my gaming PC.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/256#issuecomment-30950968
.

VM and OpenGL game is not something I want to try
I know Linux, have spares HD and my other PC runs arch (but can't run KSP). Testing it won't be that hard.

using 64 bit Linux (Lubuntu) I cannot replicate any of these errors, the
only plugin (MJ) I'm running is the latest from the build server very
recently

I have tried both with the 32bit and 64bit versions of KSP, in all
likelihood especially given the issues with the working 64bit version of
KSP is that there are some subtle (or not so) differences between Ubuntu
and Arch

On 19 December 2013 20:29, sarbian [email protected] wrote:

VM and OpenGL game is not something I want to try
I know Linux, have spares HD and my other PC runs arch (but can't run
KSP). Testing it won't be that hard.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/256#issuecomment-30963546
.

Disclaimer:
By sending an email to ANY of my addresses you are agreeing that:

1. I am by definition, "the intended recipient"
2. All information in the email is mine to do with as I see fit and
   make such financial profit, political mileage, or good joke as it
   lends itself to. In particular, I may quote it where I please.
3. I may take the contents as representing the views of your company.
4. This overrides any disclaimer or statement of confidentiality
   that may be included on your message.

Can you have a look at this thread and test the various proposed fix : http://forum.kerbalspaceprogram.com/threads/24529-The-Linux-compatibility-thread! ?

Thank you so much for linking to that thread, the binary patch fixed my ability to run the x86_64 build, and also means that I can at least have sound when running straight from the command line. :)

I'm currently trying to investigate and pin down what exact conditions the crash happens under. With the 64 bit build, it no longer happens with loading spaceplane designs, and only happens when loading a VAB design if I haven't already loaded a spaceplane design. Eg, if I load a rocket first thing, it crashes, but if I load a spaceplane first, and then go to load the exact same rocket, it doesn't crash.

I attached strace a few times to see if I could find anything obvious that would cause the crash, but I don't know enough about KSP's internals and nothing seems obviously out of place. It just gets a segfault. The strace output is here, and has about 8MB of output: http://pub.noswap.com/ksp/ksp.strace

Again, none of this happens if I run from the command line, and I tried deleting the module and reinstalling a fresh copy (and tried build 141 as well) to make sure there wasn't a problem with the PluginData that builds up. Perhaps there's a conflict between all the libs that Steam adds to the LD_PRELOAD and LD_LIBRARY_PATH that somehow causes this? I'm completely stumped.

Anyways, at least now I can play with sound from the command line, so I can use MJ without losing out on the full gameplay experience, so feel free to close this if you don't think there's anything left to try. I understand you're just writing Unity plugins, so maybe this issue will be fixed with 0.24, or maybe it's just a permanent conflict between Steam and Arch Linux. /shrug

if its any consolation I tried with stable and then testing Debian to get a
system I was happy with, that kept steam happy too, while testing did make
steam happy and some of the more advanced shader tricks work in other games
(intel HD4000) - it still aint quite ready for use - still missing some
packages...

In the end I went back to a stripped down variant of Ubuntu - at the moment
steam seems very tightly focused on Ubuntu - you can only hope that
eventually other distro's have less issues - but this is basically down to
steam and in the case of KSP especially the makers of Unity.

On 21 December 2013 21:10, John Reese [email protected] wrote:

Thank you so much for linking to that thread, the binary patch fixed my
ability to run the x86_64 build, and also means that I can at least have
sound when running straight from the command line. :)

I'm currently trying to investigate and pin down what exact conditions the
crash happens under. With the 64 bit build, it no longer happens with
loading spaceplane designs, and only happens when loading a VAB design if I
haven't already loaded a spaceplane design. Eg, if I load a rocket first
thing, it crashes, but if I load a spaceplane first, and then go to load
the exact same rocket, it doesn't crash.

I attached strace a few times to see if I could find anything obvious that
would cause the crash, but I don't know enough about KSP's internals and
nothing seems obviously out of place. It just gets a segfault. The strace
output is here, and has about 8MB of output:
http://pub.noswap.com/ksp/ksp.strace

Again, none of this happens if I run from the command line, and I tried
deleting the module and reinstalling a fresh copy (and tried build 141 as
well) to make sure there wasn't a problem with the PluginData that builds
up. Perhaps there's a conflict between all the libs that Steam adds to the
LD_PRELOAD and LD_LIBRARY_PATH that somehow causes this? I'm completely
stumped.

Anyways, at least now I can play with sound from the command line, so I
can use MJ without losing out on the full gameplay experience, so feel free
to close this if you don't think there's anything left to try. I understand
you're just writing Unity plugins, so maybe this issue will be fixed with
0.24, or maybe it's just a permanent conflict between Steam and Arch Linux.
/shrug

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/256#issuecomment-31072234
.

Disclaimer:
By sending an email to ANY of my addresses you are agreeing that:

1. I am by definition, "the intended recipient"
2. All information in the email is mine to do with as I see fit and
   make such financial profit, political mileage, or good joke as it
   lends itself to. In particular, I may quote it where I please.
3. I may take the contents as representing the views of your company.
4. This overrides any disclaimer or statement of confidentiality
   that may be included on your message.

Not sure what fixed things when, but I've since been able to get steam to run the 64bit build of KSP, and I haven't experienced any crashes since then. Gonna close this out.