KSP 1.0.5 (1028) Random crash on Arch Linux

[P-Maker]

Hello community!

I'm using KSP 1.0.5 (Build 1028, Steam version but launched seperately) on a pretty fresh Arch Linux install on my Acer Laptop (i7, GTX860M). I installed the proprietary graphics drivers and bumblebee. KSP (x64, x86 doesn't even start) is started using this command:

LD_PRELOAD="libpthread.so.0 libGL.so.1" __GL_THREADED_OPTIMIZATIONS=1 LC_ALL=C primusrun ./KSP.x86_64 --force-opengl

The game itself works without major problems, sometimes though, it just randomly freezes. When that happens not only KSP crashes but my entire PC, to the point where I have to hard-reset it. The freezes either happen on the initial loading screen, when switching scenes or sometimes just mid-game. I can't get the game to run for longer then, say, 5 minutes.

The logs don't show anything, although the Player.log has some weird (binary?) gibberish appended to it; all other entries are just normal messages like "EVA from craft X" or whatever.

I tried using optirun (also with -b primus), switching around the command line arguments, lanching through steam, applying the segfault fix (from the Linux Support Thread), I tried using noveau but that... really didn't work, plus I actually want to use the proprietary driver...

I know this is a very difficult problem to ask in a forum but I'm getting to the point where it's just so frustrating... Does anyone have an idea what's going on? Or even better, how to fix?

If you need any more information just ask, I'll provide it ASAP.

Thanks, Pi

[sal_vager]

Hi P-Maker, can you put the Player.log on pastebin for us, even if it looks useless it may still tell us something.

Also, please tty KSP without any arguments, they simply are not required and are optional, though LC_ALL=C should no longer be required at all as KSP 1.0+ ignores the system locale on both x86 and x86_64

--force-opengl is also completely redundant and useless on Linux.

But as KSP is causing the whole PC to freeze I'd be testing my RAM (memtest via a live cd) and checking my distro's own logs to find out what was going on.

While KSP might crash or freeze itself, for your system to freeze suggests a deeper issue than anything KSP can cause.

[P-Maker]

Player.log: http://pastebin.com/1AJD8wKU

This time the crash happened when loading a vessel, KSP.x86_64 was run without arguments (but with primusrun, as I want to use my nvidia card of course).

The distro's logs don't show anything, I think the system crashes before any log entries can be made...

Running a memtest right now

[sal_vager]

Yeah nothing in the logs just as you say, I'm not sure what else to suggest.

KSP does just crash sometimes, but next time your PC freezes you could try control+alt+F1 to switch to tty1, and log in to the text terminal.

You could see if it's only KSP that's not responding in htop, or use startx to get a desktop so you can use your regular task manager.

Control+alt+F7 gets you back to your normal desktop.

[P-Maker]

I tried Control-Alt-1/2/n already, nothing happening, that's what got me thinking it's something serious... Anyway, memtest doesn't show anything (as expected, I use a lot of memory heavy applications without problems).

My guess is that it has something to do with the graphics drivers, nvidia doesn't seem to like Linux that much.

Well, thanks for helping anyway.

[Boko]

On 1/2/2016 at 3:02 PM, P-Maker said:

I tried Control-Alt-1/2/n already, nothing happening,

It's actually Ctrl+Alt+F1/F2/Fn.

[radonek]

On 30. prosince 2015 at 8:04 PM, P-Maker said:

…but with primusrun, as I want to use my nvidia card of course…

You should still try it without, just to see how it ends. If it works, it would point to problem with nvidia blob  vs. bumblebee. If it fails even on builtin gpu, it could be problem somewhere in X stack (compositor, possibly). Or, if its possible to entirely disable builtin GPU in bios and use nvidia as one-and-only gpu (thus, without bumblebee), that may also give some pointers.