1.1.3 on Linux crashing shortly after starting

[CaelumEtAstra]

I honestly have no clue what is going on with this one.

I double click KSP.x86_64. The game starts, the cursor even loads, but upon reaching the loading screen, the game just crashes. Sometimes I don't get the loading screen and it crashes while the screen is still black. It happens every time it is run.

I obtained it through Steam as a fresh, bone stock install and ran it from .../steamapps/common/Kerbal Space program. Copying it to another location did not seem to help.

No KSP.log is generated after running.

player.log

System Specs:

Spoiler

It is worth noting that my heavily modded 1.0.4 and lightly modded 1.0.5 still run fine. A clean copy of 1.0.5 ran fine as well. EDIT: 1.1.2 ran fine as well.

Thank you in advance. Now excuse me while I grumble in frustration wait patiently for your help.

Edited September 3, 2016 by Mrsupersonic8
Clarification

[Galileo]

3 minutes ago, Mrsupersonic8 said:

I honestly have no clue what is going on with this one.

I double click KSP.x86_64. The game starts, the cursor even loads, but upon reaching the loading screen, the game just crashes. Sometimes I don't get the loading screen and it crashes while the screen is still black. It happens every time it is run.

I obtained it through Steam as a fresh, bone stock install and ran it from .../steamapps/common/Kerbal Space program. Copying it to another location did not seem to help.

No KSP.log is generated after running.

player.log

System Specs:

  Hide contents

It is worth noting that my heavily modded 1.0.4 and lightly modded 1.0.5 still run fine. A clean copy of 1.0.5 ran fine as well.

Thank you in advance. Now excuse me while I grumble in frustration wait patiently for your help.

Looks like you don't have enough memory,  unfortunately.  4gb of ram will hardly run the stock game on 1.1.3.  You will have to add more ram to your system 

Edited September 3, 2016 by Galileo

[CaelumEtAstra]

5 minutes ago, Galileo said:

Looks like you don't have enough memory,  unfortunately.  4gb of ram will hardly run the stock game on 1.1.3

I ran 1.1.2 just fine. There is no issue with RAM here. Heck, I had system monitor open, and it barely even got up to 2GBs before crashing. Not only that, but the Steam page still says 4GB is good enough for KSP.

Edited September 3, 2016 by Mrsupersonic8

[Galileo]

OK,  well when you don't state that,  it's easy to jump to conclusions. 

Regardless,  more ram wouldn't  hurt. 

 

 

 

 

Edited September 3, 2016 by Galileo
Spelling

[Green Baron]

4GB is okay. I don't know anything about steam. Try starting from a terminal, you will get an error message then.

Open a terminal, cd into the ksp directory, enter ./KSP.x86_64

You are likely to get an error message ...

[CaelumEtAstra]

53 minutes ago, Green Baron said:

4GB is okay. I don't know anything about steam. Try starting from a terminal, you will get an error message then.

Open a terminal, cd into the ksp directory, enter ./KSP.x86_64

You are likely to get an error message ...

Ran from terminal, but no error message. Perhaps the output from the terminal will help?

Spoiler

Set current directory to /home/isaiah/.local/share/Steam/steamapps/common/Kerbal_Space_Program
Found path: /home/isaiah/.local/share/Steam/steamapps/common/Kerbal_Space_Program/KSP.x86_64
Mono path[0] = '/home/isaiah/.local/share/Steam/steamapps/common/Kerbal_Space_Program/KSP_Data/Managed'
Mono path[1] = '/home/isaiah/.local/share/Steam/steamapps/common/Kerbal_Space_Program/KSP_Data/Mono'
Mono config path = '/home/isaiah/.local/share/Steam/steamapps/common/Kerbal_Space_Program/KSP_Data/Mono/etc'
displaymanager : xrandr version warning. 1.4
client has 3 screens
displaymanager screen (0)(DFP2): 1280 x 1024
displaymanager screen (1)(CRT1): 1280 x 1024
Using libudev for joystick management

Importing game controller configs
Aborted
 

 

[Green Baron]

No error message ...

Really no ksp.log ?

Guessing (try to unplug a joystick, or find a missing library with ldd -v KSP.x86_64) won't solve it ... let's wait for the cracks ...

 

[steve_v]

@Mrsupersonic8: The Unity5 pulseaudio bug? (but you should get some log output in this case, IIRC).

Launch with pulsenomore linked from the bugreport above, or 'ln -s /dev/null libpulse-simple.so.0' in the KSP root dir.

Edited September 4, 2016 by steve_v
Tag right user

[CaelumEtAstra]

4 hours ago, steve_v said:

The Unity5 pulseaudio bug? (but you should get some log output in this case, IIRC).

Launch with pulsenomore linked from the bugreport above, or 'ln -s /dev/null libpulse-simple.so.0' in the KSP root dir.

How do I use the utilities? The bug report doesn't exactly explain it very clearly.

Edited September 4, 2016 by Mrsupersonic8

[steve_v]

Grab the binary, mark it executable, then './pulsenomore.x86_64 ./KSP.x86_64', IIRC. Or compile with ' gcc -std=gnu99 -O2 -o pulsenomore pulsenomore.c -ldl '. All in the bug report. As for the alternative (symlinking libpulse to /dev/null), I really don't know how to explain it any more simply.

 

Edited September 5, 2016 by steve_v

[CaelumEtAstra]

4 hours ago, steve_v said:

Grab the binary, mark it executable, then './pulsenomore.x86_64 ./KSP.x86_64', IIRC. Or compile with ' gcc -std=gnu99 -O2 -o pulsenomore pulsenomore.c -ldl '. All in the bug report. As for the alternative (symlinking libpulse to /dev/null), I really don't know how to explain it any more simply.

 

Tried it, but to no avail. Checking the player.log again doesn't seem to reveal any problems related to the pulseaudio bug. Maybe try hidepulse.x86_64?

EDIT: Nevermind hidepulse, it just says permission denied.

Edited September 5, 2016 by Mrsupersonic8

[steve_v]

25 minutes ago, Mrsupersonic8 said:

EDIT: Nevermind hidepulse, it just says permission denied.

Did you mark it executable? IIRC the first hack kspflo posted needs root too...

The simplest solution to this bug is to just make the symlink, as I described. All of those solutions achieve the same thing however, so if one doesn't work, that's not the problem.

Edited September 5, 2016 by steve_v

[Green Baron]

I'm guessing, maybe a library is missing, there should be an error message but just to be sure:

If you didn't try yet "ldd -v KSP.x86_64" in the ksp-directory. You get a list of dependencies of the program, these are the libraries it needs to run. Look for "not found" or a similar hint. If you cannot scroll up to the messages cause they disappeared out of sight then "ldd -v KSP.x86_64 > filename" to write the output to a file and then "less filename" to view the output.

 

Edited September 5, 2016 by Green Baron

[CaelumEtAstra]

7 hours ago, Green Baron said:

I'm guessing, maybe a library is missing, there should be an error message but just to be sure:

If you didn't try yet "ldd -v KSP.x86_64" in the ksp-directory. You get a list of dependencies of the program, these are the libraries it needs to run. Look for "not found" or a similar hint. If you cannot scroll up to the messages cause they disappeared out of sight then "ldd -v KSP.x86_64 > filename" to write the output to a file and then "less filename" to view the output.

 

Looked through, couldn't find anything related to it. I think It's just refusing to run. I did find that the log said "AudioManager: Using PulseAudio: Default Output Device" which leads me to believe this is not related to the pulseaudio bug, and that it just won't run. The only hope I have is that 1.2 will be a bit more stable.

[Green Baron]

Welcome to the church community of the "Advent of KSP 1.2" :-)

 

Edited September 5, 2016 by Green Baron

[Kerbal101]

This is your bug (its not about settings, read through).

And this is your solution.

I recommend to limit KSP to opengl 3.3 or 3.2 (-force-glcore33 or -force-glcore32)

It may still crash or display weird first screen randomly, but if it gets through loading screen, it runs fine afterwards.