I cannot confirm but I think the device might have got into this state of an empty `00-default-nm-renderer.yaml` because of a power loss sometime during device setup in first boot of Ubuntu Core. I am thinking that a way to recover from this is instead of Network Manager snap checking if file exists (https://git.launchpad.net/~snappy-hwe-team/snappy-hwe-snaps/+git/network-manager/tree/snap-common/bin/snap-config.sh?h=1.22.10-10#n160) to determine if it should write it out, it could check if it does not exist OR the file is empty. Then it could recover on a subsequent boot.
Could also consider using `_replace_file_if_diff`.
I cannot confirm but I think the device might have got into this state of an empty `00-default- nm-renderer. yaml` because of a power loss sometime during device setup in first boot of Ubuntu Core. I am thinking that a way to recover from this is instead of Network Manager snap checking if file exists (https:/ /git.launchpad. net/~snappy- hwe-team/ snappy- hwe-snaps/ +git/network- manager/ tree/snap- common/ bin/snap- config. sh?h=1. 22.10-10# n160) to determine if it should write it out, it could check if it does not exist OR the file is empty. Then it could recover on a subsequent boot.
Could also consider using `_replace_ file_if_ diff`.