KSP does not load on Linux, always segfaults

[reinderien]

Running a brand new Steam install of KSP.

Starting the game from the console shows:

Set current directory to /home/greg
Found path: /home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP.x86_64
Mono path[0] = '/home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed'
Mono path[1] = '/home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono'
Mono config path = '/home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/etc'
displaymanager : xrandr version warning. 1.5
client has 6 screens
displaymanager screen (0)(DisplayPort-0): 1680 x 1050
displaymanager screen (1)(DVI-0): 1600 x 1200
Using libudev for joystick management


Importing game controller configs
Aborted (core dumped)

Player.log shows:

Stacktrace:


Native stacktrace:

	/home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/x86_64/libmono.so(+0x91772) [0x7fae983fb772]
	/home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/x86_64/libmono.so(+0x348e4) [0x7fae9839e8e4]
	/lib/x86_64-linux-gnu/libpthread.so.0(+0x11630) [0x7fae9dcb7630]
	/usr/lib/x86_64-linux-gnu/libLLVM-3.8.so.1(_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE8_M_eraseEPSt13_Rb_tree_nodeIS2_E+0x10) [0x7fae8df39f50]
	/lib/x86_64-linux-gnu/libc.so.6(+0x3a2e0) [0x7fae9c4a72e0]
	/lib/x86_64-linux-gnu/libc.so.6(+0x3a33a) [0x7fae9c4a733a]
	/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf8) [0x7fae9c48d3f8]
	./KSP.x86_64() [0x46f695]

Debug info from gdb:


=================================================================
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.
=================================================================

In dmesg I get these:

[12780.399329] show_signal_msg: 24 callbacks suppressed
[12780.399334] steamwebhelper[3171]: segfault at 4c ip 000055688ae25a54 sp 00007f3a3765f940 error 6 in steamwebhelper[55688adeb000+285000]
[12780.489185] Chrome_ChildThr[1707]: segfault at 0 ip 000055d584dc0b11 sp 00007f1893afe370 error 6 in plugin-container[55d584dbc000+1a000]
[13149.862363] KSP.x86_64[4882]: segfault at 7f711044bf78 ip 00007f7105f39f50 sp 00007fffd77d7610 error 4 in libLLVM-3.8.so.1[7f7105825000+24f9000]
[13309.725708] steamwebhelper[3746]: segfault at 4c ip 0000561b31a0fa54 sp 00007f62e1fc7940 error 6 in steamwebhelper[561b319d5000+285000]

Any ideas?

Edited March 24, 2017 by reinderien
dmesg additions

[sal_vager]

Hi @reinderien, I'm sorry to see you're having further issues, but I don't think I can help with the information you have provided.

Can you please tell me which Linux distribution and version you are using, and your hardware.

You can get a hardware report using the hardinfo Linux package, available in most package managers.

Does the KSP.x86 work for you? And can you describe what you see when you run KSP,x86_64 please.

[reinderien]

Quote

Linux distribution and version you are using

It is Lubuntu 16.10 x86-64:

$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.10
DISTRIB_CODENAME=yakkety
DISTRIB_DESCRIPTION="Ubuntu 16.10"

Quote

your hardware

I think the hardware should not be an issue because I have run KSP on this machine before. It is a Dell Precision T7400 with this graphics card:

$ sudo lspci | grep VGA
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X]

This memory:

$ free -h
              total        used        free      shared  buff/cache   available
Mem:            30G        2.2G         23G         71M        5.0G         27G

And this CPU:

CPU0: Intel(R) Xeon(R) CPU           X5450  @ 3.00GHz (family: 0x6, model: 0x17, stepping: 0x6)

I will attach hardinfo report.

Quote

Does the KSP.x86 work for you?

I first had to install some 32-bit libs, but then it failed in the same way.

$ sudo apt install libxcursor1:i386
$ sudo apt install libxrandr2:i386

$ ./KSP.x86
Set current directory to /home/greg/.steam/steam/steamapps/common/Kerbal Space Program
Found path: /home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP.x86
Mono path[0] = '/home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed'
Mono path[1] = '/home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono'
Mono config path = '/home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/etc'
displaymanager : xrandr version warning. 1.5
client has 6 screens
displaymanager screen (0)(DisplayPort-0): 1680 x 1050
displaymanager screen (1)(DVI-0): 1600 x 1200
Using libudev for joystick management


Importing game controller configs
Aborted (core dumped)

$ cat ~/.config/unity3d/Squad/Kerbal\ Space\ Program/Player.log 
Stacktrace:


Native stacktrace:

	/home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/x86/libmono.so(+0x89917) [0xf55ac917]
	/home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/x86/libmono.so(+0x21a63) [0xf5544a63]
	[0xf771bcc0]
	/usr/lib/i386-linux-gnu/libLLVM-3.8.so.1(_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE8_M_eraseEPSt13_Rb_tree_nodeIS2_E+0x23) [0xf0d44ae3]
	/usr/lib/i386-linux-gnu/libLLVM-3.8.so.1(+0x15b588c) [0xf1d7c88c]
	/lib/i386-linux-gnu/libc.so.6(+0x2eaab) [0xf717eaab]
	/lib/i386-linux-gnu/libc.so.6(+0x2eb11) [0xf717eb11]
	/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0x102) [0xf7168282]
	./KSP.x86() [0x80955c9]

Debug info from gdb:


=================================================================
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.
=================================================================

Quote

can you describe what you see when you run KSP.x86_64 please.

No screen appears, no window appears, just this:

$ ./KSP.x86_64 
Set current directory to /home/greg/.steam/steam/steamapps/common/Kerbal Space Program
Found path: /home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP.x86_64
Mono path[0] = '/home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed'
Mono path[1] = '/home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono'
Mono config path = '/home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/etc'
displaymanager : xrandr version warning. 1.5
client has 6 screens
displaymanager screen (0)(DisplayPort-0): 1680 x 1050
displaymanager screen (1)(DVI-0): 1600 x 1200
Using libudev for joystick management


Importing game controller configs
Aborted (core dumped)

 

[reinderien]

I couldn't find where to add an attachment, so I just uploaded the hardware report here.

[sal_vager]

Ahh, Lubuntu, if I remember right Lxde does not include Pulseaudio and the Unity engine requires it.

Please take a look here.

Specifically at Kspflo's post here.

Quote

New day, new hack.

pulsenomore checks if Pulseaudio is running, if it is, executes the supplied program directly, otherwise loades the executable into memory, replaces "libpulse-simple.so.0" with "/dev/null", and then executes that.

It requires the memfd_create() syscall introduced in 3.17. I actually tried to provide a fallback (open() with O_TMPFILE), but the file descriptor must not be opened with write permission, or ETXTBSY is returned, when trying to execute it. If needed, one could of course write the patched file to disk, but I'll wait for someone without memfd_create() to come along first.
I disabled Pulseaudio autospawn and KSP crashed as expected. Using pulsenomore, it launches successfully.

No more setuid needed, just make it executable, and run it.

And Lysius's post below about using this with Steam.

Hopefully this will fix KSP for you @reinderien.

[reinderien]

That's interesting - but unfortunately (1) I get 403s when attempting to access the Squad bugtracker it's not clear to me that that bug report applies to my situation, since (2) I seem to already have PA installed:

$ dpkg -l | grep pulse
ii  libpulse-mainloop-glib0:amd64               1:9.0-2ubuntu2.1                         amd64        PulseAudio client libraries (glib support)
ii  libpulse0:amd64                             1:9.0-2ubuntu2.1                         amd64        PulseAudio client libraries
ii  libpulsedsp:amd64                           1:9.0-2ubuntu2.1                         amd64        PulseAudio OSS pre-load library
ii  pulseaudio                                  1:9.0-2ubuntu2.1                         amd64        PulseAudio sound server
ii  pulseaudio-utils                            1:9.0-2ubuntu2.1                         amd64        Command line tools for the PulseAudio sound server

 

Edited March 24, 2017 by reinderien
bugtracker loads now

[sal_vager]

I just realized it was in an archived section, I have moved it to the public tracker so it is now accessible.

 

I have not heard of issues on Lubuntu for a while, and I know KSP will run on Linux, your logs are odd in that htey end very soon after launching, there is not even time for KSP to be loaded, your Player log should have lines like this.

Spoiler

Using libudev for joystick management

Importing game controller configs
UnloadTime: 2.641000 ms
Release Build
 
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42)

[KSP Version]: 1.2.2.1622 (LinuxPlayer) ====================================
 
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42)

[Input Devices]:

etc...

 

So it suggests the Unity engine is having a problem on your PC, I know you have the LibXcursor library so it can't be that, but I am at a loss to know what is wrong here.

One clues is this from your hardinfo report.

Spoiler

OpenGL
Vendor	Unknown
Renderer	Unknown
Version	Unknown
Direct Rendering	No

This is not right, and the Unity engine requires direct rendering to be able to display an image, here is mine for example.

Spoiler

OpenGL
Vendor	X.Org
Renderer	Gallium 0.4 on AMD KAVERI (DRM 2.46.0 / 4.8.0-42-generic, LLVM 3.8.0)
Version	3.0 Mesa 12.0.6
Direct Rendering	Yes

I'm using an R7 GPU built into my AMD-A8 CPU.

So it looks like your graphics driver is bad @reinderien, and you will need to fix it.

[reinderien]

Running the 64-bit binary via gdb, I get:

$ gdb KSP.x86_64 
[...]
Reading symbols from KSP.x86_64...(no debugging symbols found)...done.
(gdb) r
Starting program: /home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP.x86_64 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Found path: /home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP.x86_64
Mono path[0] = '/home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed'
Mono path[1] = '/home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono'
Mono config path = '/home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/etc'
[New Thread 0x7ffff7ff1700 (LWP 9574)]
[New Thread 0x7ffff1959700 (LWP 9575)]
[New Thread 0x7ffff1758700 (LWP 9576)]
displaymanager : xrandr version warning. 1.5
client has 6 screens
displaymanager screen (0)(DisplayPort-0): 1680 x 1050
displaymanager screen (1)(DVI-0): 1600 x 1200
Using libudev for joystick management


Importing game controller configs
[New Thread 0x7fffe3dea700 (LWP 9577)]
[Thread 0x7fffe3dea700 (LWP 9577) exited]

Thread 1 "KSP.x86_64" received signal SIGSEGV, Segmentation fault.
0x00007fffe9201f50 in std::_Rb_tree<unsigned int, std::pair<unsigned int const, unsigned int>, std::_Select1st<std::pair<unsigned int const, unsigned int> >, std::less<unsigned int>, std::allocator<std::pair<unsigned int const, unsigned int> > >::_M_erase(std::_Rb_tree_node<std::pair<unsigned int const, unsigned int> >*) () from /usr/lib/x86_64-linux-gnu/libLLVM-3.8.so.1

The stacktrace looks like:

(gdb) bt
#0  0x00007fffe9201f50 in std::_Rb_tree<unsigned int, std::pair<unsigned int const, unsigned int>, std::_Select1st<std::pair<unsigned int const, unsigned int> >, std::less<unsigned int>, std::allocator<std::pair<unsigned int const, unsigned int> > >::_M_erase(std::_Rb_tree_node<std::pair<unsigned int const, unsigned int> >*) () from /usr/lib/x86_64-linux-gnu/libLLVM-3.8.so.1
#1  0x00007ffff61b72e0 in __run_exit_handlers (status=-1, listp=0x7ffff653e5d8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:83
#2  0x00007ffff61b733a in __GI_exit (status=<optimized out>) at exit.c:105
#3  0x00007ffff619d3f8 in __libc_start_main (main=0x4651a0, argc=1, argv=0x7fffffffe1a8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffe198)
    at ../csu/libc-start.c:325
#4  0x000000000046f695 in ?? ()
#5  0x00007fffffffe198 in ?? ()
#6  0x000000000000001c in ?? ()
#7  0x0000000000000001 in ?? ()
#8  0x00007fffffffe47a in ?? ()
#9  0x0000000000000000 in ?? ()

 

1 hour ago, sal_vager said:

So it suggests the Unity engine is having a problem on your PC,

OK. If that is the case, I am going to try a different Unity/Steam game to see if it has the same issues, to try and narrow down the problem. Thanks @sal_vager.

Edited March 24, 2017 by reinderien
Remove gdb banner

[sal_vager]

By the way @reinderien I am using the open source xserver-xorg-video-radeon driver.

[reinderien]

1 minute ago, sal_vager said:

By the way @reinderien I am using the open source xserver-xorg-video-radeon driver.

I have that installed:

$ dpkg -l | grep xserver-xorg-video-radeon
ii  xserver-xorg-video-radeon                   1:7.7.1-1                                amd64        X.Org X server -- AMD/ATI Radeon display driver

And as far as I can tell xorg is using it:

[ 13309.901] (II) LoadModule: "ati"
[ 13309.902] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
[ 13309.902] (II) Module ati: vendor="X.Org Foundation"
[ 13309.902]    compiled for 1.18.4, module version = 7.7.1
[ 13309.902]    Module class: X.Org Video Driver
[ 13309.902]    ABI class: X.Org Video Driver, version 20.0
[ 13309.902] (II) LoadModule: "radeon"
[ 13309.902] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
[ 13309.902] (II) Module radeon: vendor="X.Org Foundation"
[ 13309.902]    compiled for 1.18.4, module version = 7.7.1
[ 13309.902]    Module class: X.Org Video Driver
[ 13309.902]    ABI class: X.Org Video Driver, version 20.0
...
[ 13309.910] (--) RADEON(0): Chipset: "VERDE" (ChipID = 0x683d)

I've not installed any proprietary drivers, so I don't think they're in use here.

31 minutes ago, sal_vager said:

So it looks like your graphics driver is bad @reinderien, and you will need to fix it.

Well, I just installed and ran Infinifactory (A Unity game), and it has no problems, graphical or otherwise. Hmmmmm, what else could be the culprit?

[sal_vager]

2 minutes ago, reinderien said:

I've not installed any proprietary drivers, so I don't think they're in use here.

I think AMD dropped the proprietary driver for the HD 7 series, but the open driver should be detected by hardinfo.

As for other games, KSP runs on Unity 5 so the best games to try are Pulsar lost colony, Besieged and Satellite reign, unfortunately I don't know of any demos that use Unity 5.

[sal_vager]

@reinderien here's some things to try.

https://unix.stackexchange.com/questions/27918/getting-opengl-to-work-under-ubuntu

[reinderien]

10 minutes ago, sal_vager said:

the best games to try are Pulsar lost colony, Besieged and Satellite reign

As luck would have it, I own Besiege, so I installed it and it, too, runs OK. I'm investigating why hardinfo does not report my graphics card, in the meantime.

3 minutes ago, sal_vager said:

@reinderien here's some things to try.

https://unix.stackexchange.com/questions/27918/getting-opengl-to-work-under-ubuntu

Ah, great.

glxinfo looks OK:

name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
[...]
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: X.Org (0x1002)
    Device: AMD CAPE VERDE (DRM 2.46.0 / 4.8.0-41-generic, LLVM 3.8.1) (0x683d)
    Version: 12.0.6
    Accelerated: yes
    Video memory: 1024MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.1
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.0
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD CAPE VERDE (DRM 2.46.0 / 4.8.0-41-generic, LLVM 3.8.1)
OpenGL core profile version string: 4.1 (Core Profile) Mesa 12.0.6

And xvinfo does not return any errors.

[sal_vager]

13 minutes ago, reinderien said:

And xvinfo does not return any errors.

Okay so graphics have got to be fine, have you tried checking KSP's permissions? It can fail to run if files are read only.

[reinderien]

Just now, sal_vager said:

Okay so graphics have got to be fine

I think you are right - a fairly definitive Unity test I found (you may find useful to keep in your back pocket):

$ /usr/lib/nux/unity_support_test -f -p
OpenGL vendor string:   X.Org
OpenGL renderer string: Gallium 0.4 on AMD CAPE VERDE (DRM 2.46.0 / 4.8.0-41-generic, LLVM 3.8.1)
OpenGL version string:  3.0 Mesa 12.0.6

Not software rendered:    yes
Not blacklisted:          yes
GLX fbconfig:             yes
GLX texture from pixmap:  yes
GL npot or rect textures: yes
GL vertex program:        yes
GL fragment program:      yes
GL vertex buffer object:  yes
GL framebuffer object:    yes
GL version is 1.4+:       yes

Unity 3D supported:       yes

Quote

have you tried checking KSP's permissions? It can fail to run if files are read only.

I think they are alright, but you be the judge:

~/.steam/steam/steamapps/common/Kerbal Space Program$ ls -l
total 98004
-rwxrwxr-x 1 greg greg       52 Mar 23 20:08 buildID.txt
drwxrwxr-x 2 greg greg     4096 Mar 23 20:14 EmptySteamDepot
drwxrwxr-x 3 greg greg     4096 Mar 23 20:14 GameData
drwxrwxr-x 2 greg greg     4096 Mar 23 20:14 Internals
drwxrwxr-x 6 greg greg     4096 Mar 23 20:14 KSP_Data
-rw-rw-r-- 1 greg greg   211273 Mar 24 11:14 KSP.log
-rwxrwxr-x 1 greg greg 25644176 Mar 23 20:11 KSP.x86
-rwxrwxr-x 1 greg greg 25923152 Mar 23 20:11 KSP.x86_64
drwxrwxr-x 6 greg greg     4096 Mar 24 11:17 Launcher_Data
-rwxrwxr-x 1 greg greg 23853216 Mar 23 20:14 Launcher.x86
-rwxrwxr-x 1 greg greg 24196128 Mar 23 20:14 Launcher.x86_64
-rwxrwxr-x 1 greg greg   103513 Mar 24 11:14 PartDatabase.cfg
drwxrwxr-x 2 greg greg     4096 Mar 23 20:14 Parts
-rwxrwxr-x 1 greg greg    21792 Mar 23 20:14 Physics.cfg
drwxrwxr-x 2 greg greg     4096 Mar 24 11:08 Plugins
-rwxrwxr-x 1 greg greg   287922 Mar 23 20:13 readme.txt
drwxrwxr-x 2 greg greg     4096 Mar 23 20:14 Resources
drwxrwxr-x 4 greg greg     4096 Mar 23 20:14 saves
drwxrwxr-x 2 greg greg     4096 Mar 24 11:11 Screenshots
-rw-rw-r-- 1 greg greg    26796 Mar 24 11:10 settings.cfg
drwxrwxr-x 5 greg greg     4096 Mar 23 20:14 Ships
drwxrwxr-x 2 greg greg     4096 Mar 23 20:14 sounds

 

[sal_vager]

Sorry to go back to sound @reinderien but can you try this?

Quote

Checking Pulseaudio

You may find packages with 'pulse' in their name on your system. to check if pulseaudio is currently running do:

pgrep -l pulseaudio

which will list a process named 'pulseaudio' if it is running, or not list it, if it is not.

If you would like install the pulseaudio layer onto Lubuntu, please see Pulse Audio Pulseaudio can help if you're having difficulty configuring USB headphones, Skype, or need to increase volume past 100%

 

[reinderien]

1 minute ago, sal_vager said:

Sorry to go back to sound @reinderien but can you try this?

 

No need to apologise - yes, it's running:

$ pgrep -l pulseaudio 
5831 pulseaudio

$ pacmd info
[...]
3 sink(s) available.
[...]
  * index: 2
        name: <alsa_output.usb-045e_Microsoft_LifeChat_LX-3000-00.analog-stereo>
        driver: <module-alsa-card.c>
        flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
        state: IDLE
        suspend cause: 
        priority: 9049
        volume: front-left: 22978 /  35% / -27.31 dB,   front-right: 22978 /  35% / -27.31 dB
                balance 0.00
        base volume: 65687 / 100% / 0.06 dB
        volume steps: 65537
        muted: no
        current latency: 42.74 ms
        max request: 6 KiB
        max rewind: 344 KiB
        monitor source: 3
        sample spec: s16le 2ch 44100Hz
        channel map: front-left,front-right
                     Stereo
        used by: 0
        linked by: 1
        configured latency: 40.00 ms; range is 16.00 .. 2000.00 ms
        card: 2 <alsa_card.usb-045e_Microsoft_LifeChat_LX-3000-00>
        module: 8
        properties:
                alsa.resolution_bits = "16"
                device.api = "alsa"
                device.class = "sound"
                alsa.class = "generic"
                alsa.subclass = "generic-mix"
                alsa.name = "USB Audio"
                alsa.id = "USB Audio"
                alsa.subdevice = "0"
                alsa.subdevice_name = "subdevice #0"
                alsa.device = "0"
                alsa.card = "2"
                alsa.card_name = "Microsoft LifeChat LX-3000"
                alsa.long_card_name = "Microsoft LifeChat LX-3000 at usb-0000:00:1d.0-2, full speed"
                alsa.driver_name = "snd_usb_audio"
                device.bus_path = "pci-0000:00:1d.0-usb-0:2:1.0"
                sysfs.path = "/devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.0/sound/card2"
                udev.id = "usb-045e_Microsoft_LifeChat_LX-3000-00"
                device.bus = "usb"
                device.vendor.id = "045e"
                device.vendor.name = "Microsoft Corp."
                device.product.id = "070f"
                device.product.name = "LifeChat LX-3000 Headset"
                device.serial = "045e_Microsoft_LifeChat_LX-3000"
                device.form_factor = "headset"
                device.string = "front:2"
                device.buffering.buffer_size = "352800"
                device.buffering.fragment_size = "176400"
                device.access_mode = "mmap+timer"
                device.profile.name = "analog-stereo"
                device.profile.description = "Analog Stereo"
                device.description = "LifeChat LX-3000 Headset Analog Stereo"
                alsa.mixer_name = "USB Mixer"
                alsa.components = "USB045e:070f"
                module-udev-detect.discovered = "1"
                device.icon_name = "audio-headset-usb"
                device.intended_roles = "phone"
        ports:
                analog-output-speaker: Speakers (priority 10000, latency offset 0 usec, available: unknown)
                        properties:
                                device.icon_name = "audio-speakers"
        active port: <analog-output-speaker>

 

[sal_vager]

5 minutes ago, reinderien said:

No need to apologise - yes, it's running:

Okay, maybe it's using the wrong resolution, your Player log has this.

Quote

displaymanager screen (0)(DisplayPort-0): 1680 x 1050
displaymanager screen (1)(DVI-0): 1600 x 1200

If you delete the prefs file at ~/.config/unity3d/Squad/Kerbal Space Program/ and the settings.cfg from the ~/.steam/steam/steamapps/common/Kerbal Space Program/ folder will the KSP.x86 file start KSP when used directly?

[reinderien]

6 minutes ago, sal_vager said:

Okay, maybe it's using the wrong resolution, your Player log has this.

If you delete the prefs file at ~/.config/unity3d/Squad/Kerbal Space Program/ and the settings.cfg from the ~/.steam/steam/steamapps/common/Kerbal Space Program/ folder will the KSP.x86 file start KSP when used directly?

Quite interesting. In dramatic fashion, as soon as I did that and ran again, KSP got further, a black window appeared, and then my entire X session crashed... So, progress?

[sal_vager]

2 minutes ago, reinderien said:

So, progress?

Actually yes, this is what progress looks like 

I think you need this.

Because of this.

http://bugs.kerbalspaceprogram.com/issues/11382

Which Unity knows about and have switched to SDL in Unity 5.6, which might fix it.

[reinderien]

4 minutes ago, sal_vager said:

Actually yes, this is what progress looks like 

I think you need this.

Victory! After prepending that, with no config files, my game loads. I had actually tried this before but with config files present, and kept seeing the same immediate crash.

So in addition to the localization bug, is there some kind of bad-resolution bug?

[sal_vager]

2 minutes ago, reinderien said:

is there some kind of bad-resolution bug?

Yes, Unity will send a bad window size to the Linux window manager, this usually results in excessive memory being requested causing OOM Killer to kill either KSP or in some cases the window manager itself.

This can be triggered by empty Unity projects and Unity tutorials, and has been a problem since at least KSP 1.1

SDL in the Linux version of Unity might solve this, but it's unknown at this time, KSP is still on Unity 5.4.0p4