1.2.1 Linux, No-Go for Launch

[alecdacyczyn]

KSP Version: 1.2.1,  OS: LinuxMint 18 Cinnamon x86-64, Current proprietary Nvidia driver (nvidia-367), Installed from the ZIP archive, downloaded on Dec 1st

Game will not launch. I get this in console:

Quote

Set current directory to /opt/alec/KSP_Linux
Found path: /opt/alec/KSP_Linux/Launcher.x86_64
Mono path[0] = '/opt/alec/KSP_Linux/Launcher_Data/Managed'
Mono path[1] = '/opt/alec/KSP_Linux/Launcher_Data/Mono'
Mono config path = '/opt/alec/KSP_Linux/Launcher_Data/Mono/etc'
displaymanager : xrandr version warning. 1.5
client has 4 screens
displaymanager screen (0)(DVI-I-1): 1920 x 1080
displaymanager screen (1)(DVI-D-0): 1920 x 1080
Using libudev for joystick management

Importing game controller configs
Aborted

 

Player.log (This is it. There is no more. It crashes pretty early)

Quote

Stacktrace:

Native stacktrace:

    /opt/alec/KSP_Linux/Launcher_Data/Mono/x86_64/libmono.so(+0x91772) [0x7f49fa19a772]
    /opt/alec/KSP_Linux/Launcher_Data/Mono/x86_64/libmono.so(+0x348e4) [0x7f49fa13d8e4]
    /lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0) [0x7f49fd2e23d0]
    ./Launcher.x86_64() [0xdd7fea]
    ./Launcher.x86_64() [0xdd0404]
    ./Launcher.x86_64() [0xdd15d4]
    ./Launcher.x86_64() [0x46195c]
    /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f49fbaa1830]
    ./Launcher.x86_64() [0x46b4ed]

Debug info from gdb:

Could not attach to process.  If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Operation not permitted.
No threads.

=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

I've searched through these forums and tried all of the workarounds I could find with no discernible change in behavior, including:

-Deleting the "~/.config/unity3d" folder and all its contents.

-Running with "LC_ALL=C ./KSP.x86_64"

-Running with "-force-glcore" or "-force-gfx-direct"

-Pulseaudio is installed and running. The "pulsenomore" thingamajig has no effect.

-The libs listed by "ldd KSP.x86_64" all seem to be present.

- Installed 'libgl1-mesa-glx:i386'

-Identical behavior running all of these attempts with both 32-bit and 64-bit executables and direct to the KSP.x86(_64) binary and through the Launcher (except for the log file producing shorter memory addresses in the stack trace, obviously).

- That installer script at the top of the "Linux compatibility thread" didn't work... much. It downloaded and inflated the files fine, but then spit out a bunch of error messages. The binaries it installed produced the same results.

 

It looks like a problem with the Mono runtime, which I've read in included by Unity; so updating my system's packages won't help. Are there any known workarounds for this issue? I suspect I'll just have to wait patiently for someone at Unity to fix the bug. Until then, I'll try to get the Windows version working through Wine.

[sal_vager]

Hi @alecdacyczyn, I see you have KSP in opt, does KSP have write permissions for opt? If not then it will fail to run.

Do you have a /home/username/ folder that you can use instead?

[alecdacyczyn]

Yes, that directory is owned by the user. There are no permissions issues.

But I found the problem: While I was poking around in the Driver Manager, get the version number for the above post, I noticed that the "amd-microcode" part of the driver was turned off. Apparently that was installed as part of an update but is not turned on automatically. After I finished writing my post I enabled that device and restarted to see it it would make a difference.

It works! At least the 32-bit version. The 64-bit binary crashed the Cinnamon environment spectacularly. Really bad. I had to Ctrl+Alt+F1 to get out of that trainwreck of corrupted GUI elements to kill the Xorg server to recover. But that's not KSP's fault. I'll have to put in a bug report to Mint. It seemed to have something to do with a screen-mode change.

Never mind. It's now working and playable.

Edited December 1, 2016 by alecdacyczyn

[sal_vager]

Actually there's a known Unity bug that crashes the X server, it has been reported but no action yet.