Settings.cfg file not being obeyed

[halrick]

I hope someone can help me. The problem I'm having is that the settings.cfg file isn't being followed. After getting this bug with only editor extensions installed, I figured I'd go back to basics with a fresh Install, I checked the camera sensitivity inside the vab & on the launchpad; in both cases normal. With no changes to settings made, I launched ksp again, only to be blasted by the music at 1000% (that's what it said in the options menu). After reducing ALL audio settings back to the previous value (all values were at 1/100th of the faulty value, so I set the music volume back to 10%), I entered the VAB and did a sensitivity test with the camera. I'll just say it wasn't anywhere near stock. What would have been a 10° change in perspective, became almost a 360° change (checked mouse hardware sensitivity, to ensure that that's not the cause). Same glitch with the camera on the launch pad.

In essence, it's like this:

fresh install

1st launch of ksp; all is normal

2nd launch of ksp; volume beyond funny and camera sensitivity nowhere near acceptable

I figured that perhaps ksp somehow changes the settings file upon closing ksp. So I did another fresh install, launched ksp, checked settings, did resolution change, pressed both accept and apply, and then, without closing ksp, set the settings.cfg file to "read-only". Despite this drastic measure, KSP still boosts the volume to extremes and the camera sensitivity problem still persists.

Values of the influenced settings (at least as far as I can tell) as they are in the config file:

VAB_CAMERA_ORBIT_SENS = 0.04

VAB_CAMERA_ZOOM_SENS = 0.1

FLT_CAMERA_ORBIT_SENS = 0.04

FLT_CAMERA_ZOOM_SENS = 0.5

SHIP_VOLUME = 0.40

AMBIENCE_VOLUME = 0.30

MUSIC_VOLUME = 0.10

UI_VOLUME = 0.30

VOICE_VOLUME = 0.20

Any help is greatly appreciated.

Final Update: Problem solved thanks to vexx32

Edited December 28, 2014 by halrick
Problem solved

[vexx32]

You might need to be launching KSP with the LC_ALL=C command; see the main Linux thread for details.

[halrick]

You might need to be launching KSP with the LC_ALL=C command; see the main Linux thread for details.

Thank you! It seems that this solved the issue.