Iceberg "Use custom SSH keys" setting is not initialized correctly from settings file, and does not survive image restart

[belaroesener]

Problem

The settings for the SSH keys 1. are not initialized when starting a fresh image and 2. do not persist over image restart. Yet, loading them from the settings file does work.

Reproduction

Im using MacOS 26 on an Arm64 mac as well as an older version of MacOS on Amd64. This affects both Pharo 14 as well as Pharo 13 (I'm using PharoLauncher).

1. The settings file contains

...
	StoredSetting {
		#settingNodeIdentifier : '#icebergCredentials#useCustomSsh',
		#realValue : true
	},
	StoredSetting {
		#settingNodeIdentifier : '#useCustomSsh#publicKey',
		#realValue : '/Users/belarosener/.ssh/pharo-git-key.pub'
	},
	StoredSetting {
		#settingNodeIdentifier : '#useCustomSsh#privateKey',
		#realValue : '/Users/belarosener/.ssh/pharo-git-key'
	}
...

2. Fresh Pharo 14 Image via PharoLauncher
3. 
4. Load Settings (using SettingBrowser)
5. 
6. Save image and restart
7. 

All other settings work just fine

[Ducasse]

Thanks for the report.

[belaroesener]

This behaviour was caused by start up actions defined in a file in the general preferences folder. I wasn't aware of this file, because it was created from a template by the Menu entry "World Menu | System | Startup | Define a global preference file". This template happens to overwrite the Custom Key settings with nonsensical values (that also happen to look platform specific). I must have triggered this menu entry by accident and ignored the Inspector window opening up.

I'm closing the issue because it's not a bug, but my own fault. I'm also opening a PR to change the template string to not overwrite settings.