[Bug]: Duplicated majestic.yaml in /etc from work overlay

[ibnHatab]

Requirements

• I checked the troubleshooting section in the README to verify that I have the latest Configurator version.
• I did a search to see if there is a similar issue or if a pull request is open.

Current Behavior

Where found: master+4c53cf5, 2025-12-25
List shows 2 files with identical names:
root@openipc-ssc30kq:/etc# ls
TZ inittab openipc_donors ssl
alink.conf issue os-release sysctl.conf
crontabs libnl passwd system.ok
drone.key majestic.yaml profile timezone
dropbear majestic.yaml profile.d txprofiles.conf

To reproduce:
Flash Sphere using companion: /tmp/openipc.ssc30kq-nor-fpv.tgz (this image not listed in configurator)
Copy overlay to Ubuntu: scp -r root@192.168.1.10:/overlay/root/etc/ .
diff etc/majestic.yaml "etc/majestic.yaml^M"

Assumption: 'good' written by 'configurator', 'bag' file comes from flushing from 'companion' in .
In image:
/tmp/openipc.ssc30kq-nor-fpv » sudo mount -o loop pwd/rootfs.squashfs.ssc30kq pwd/rfs
/tmp/openipc.ssc30kq-nor-fpv » ls -li "rfs/etc/majestic.yaml"
123 -rw-r--r-- 1 root root 1009 Dec 25 06:19 rfs/etc/majestic.yaml
File content is default parameters.

Expected Behavior

No response

Steps To Reproduce

No response

Context

YAML state

Environment

- Config Version:

Anything else?

No response

[mikecarr]

I am trying to understand what is going on here, I don't have a sphere so I cannot test. First off, where did you get 'openipc.ssc30kq-nor-fpv.tgz'? So you flash this and majestic.yaml is corrupt? or there are two majestic.yaml in etc?

[ibnHatab]

1. openipc.ssc30kq-nor-fpv.tgz was flushed into board with 'companion'. Somehow 'configurator' don't list it. 'companion' is from releases binary OpenIPC-Config-linux-x64.zip showing OpenIPC Configurator v0.7.12.
2. I configured camera and wbf from 'configurator' from Windows vbox, also binary from release.
3. I saw issue when I ssh to SOC and give ls in /etc. It shows majestic.yaml two times. They differ in permissions, one root exclusive and another root with o+r.
4. I saw overlay mount from /overlay/root but its not how overlays work. File path from overlay shod take over path in root fs and if deleted default is restored. Right?
5. Digging deeper, there was: majestic.yaml and majestic.yaml^M
6. Escape ^M did not show in console, busybox ignores it. 'find' on ubuntu show it as majestic.yaml?. zsh expand it to ./etc/majestic.yaml$'\r'.
7. What I can see: rootfs - good name default content. 'configurator' writes good name and my parameters. 'companion' - writes good name my parameters. majectic - use good file.

IMO, functionality consistent.
Evil twin file can be ignored until somebody spend few hours debugging installation.

I can help to debug if you give minimal instructions, but Sphere don't have serial to monitor progress. Maybe we can check on other SOC?

[mikecarr]

Can you attach the logs? I have not been able to reproduce this, Companion uses openipc sysupgrade under the covers and only echo's its output for progress and logging. Are you on Telegram?

[mikecarr]

1. openipc.ssc30kq-nor-fpv.tgz was flushed into board with 'companion'. Somehow 'configurator' don't list it. 'companion' is from releases binary OpenIPC-Config-linux-x64.zip showing OpenIPC Configurator v0.7.12.
2. I configured camera and wbf from 'configurator' from Windows vbox, also binary from release.
3. I saw issue when I ssh to SOC and give ls in /etc. It shows majestic.yaml two times. They differ in permissions, one root exclusive and another root with o+r.
4. I saw overlay mount from /overlay/root but its not how overlays work. File path from overlay shod take over path in root fs and if deleted default is restored. Right?
5. Digging deeper, there was: majestic.yaml and majestic.yaml^M
6. Escape ^M did not show in console, busybox ignores it. 'find' on ubuntu show it as majestic.yaml?. zsh expand it to ./etc/majestic.yaml$'\r'.
7. What I can see: rootfs - good name default content. 'configurator' writes good name and my parameters. 'companion' - writes good name my parameters. majectic - use good file.

IMO, functionality consistent. Evil twin file can be ignored until somebody spend few hours debugging installation.

I can help to debug if you give minimal instructions, but Sphere don't have serial to monitor progress. Maybe we can check on other SOC?

Did you get this sorted?