[Linux] controller axis screwed up on game-start: float -> int

[The-Grim-Sleeper]

Every time I start the game, all the controller axis settings get screwed up. I've found that the problem involves the settings.cfg file, it gets rewritten every time the game starts up, but it is only another symptom, as setting the file to read-only still causes the problem in-game.

What seems to be happening is that the float numbers for 'sensitivity' and 'deadzone' are being read out as integers.

Before:
        sensitivity = 4.04848957
        deadzone = 0.0229729917

After:
        sensitivity = 404848960
        deadzone = 229729920

 

Update: went through the usual 'delete settings.cfg, reconfigure' stuff, but after another start-up, the axis setings are bad, and integers are back.

==============

I am running on Ubuntu 16.04 (64x-bit), which seems to work fine in all other respects.

Kerbal version 1.3.1, build id = 01891

Settings.cfg before start-up: https://drive.google.com/open?id=1PWpeJCByMksyvK4gDbWCNvMvUXJ5E9yV

Player.log before start-up: https://drive.google.com/open?id=1bQsRLYqQwXCc1nd3A27308ak23EE1XwO

Settings.cfg after start-up: https://drive.google.com/open?id=1SYWygkgeZXrBStXH8B1HlD53DjE_RhvE

Player.log after start-up: https://drive.google.com/open?id=1fhJ_yCrmhfyvlcPo8qKDNFCb4wUAxRGJ

This is my first time reporting an error here so I'm not sure what other information is required.
 

Edited January 4, 2018 by The-Grim-Sleeper
wrong log

[The-Grim-Sleeper]

So can anybody tell me anything about how KSP reads out the settings.cfg?

Or confirm that I've posted the required information in the correct thread?