Comment # 117 on bug 1094762 from Chris Bradbury

Tentatively reopening as I've found a way to consistently reproduce this issue;
it does require using AWS (but free tier should be sufficient).

Amazon Lightsail instances can currently only be created with Leap 42.2
'blueprints'. On creating a new instance and upgrading it first to Leap 42.3
and then to Leap 15.0 (as per 'System upgrade' on SDB) this issue will occur
100% of the time.

Behaviour is consistent regardless of reboots between upgrades, so the 'launch
script' can be used to automate the upgrade process and any other desired
behaviour.