batocera.conf reset to default after changing RGB LED configuration

[c64chrom]

Knulli build version

firefly 2024/12/04 03:10 [o]

Your architecture

RG40XX H, RG40XX V

Issue description

On an already configured system, if you go to "tools/RGB settings" and change some parameter, then exit, the RGB LED options are applied to /system/batocera.conf but all the other configurations are reset to the default in the same file

Detailed reproduction steps

on a stock firefly installation:

• change some settings from the interface (eg. CPU governor, brightness)
• go to tools/RGB settings and change the LED settings to anything, save and exit
• open an emulator and change some settings. Exit the emulator and the setting is saved in /system/batocera.conf (as an alternative step just manually edit /system/batocera.conf with a text editor adding any retroarch option like "global.retroarch.input_shader_next_btn=nul" to disable the shader hotkey or "saturn.shaderset=none" to disable the shader for saturn emulation and save the file)
• reboot the system and check your custom config is still there
• go again in tools/RGB settings and change the LED settings to anything, save and exit
• at this point check the /system/batocera.conf and it is reset to near-stock configuration

Details of any attempts to fix this yourself

No response

Details of any modifications you have made to Knulli.

Applied the Firefly hotfix v1.02 (h700), and made custom configurations to batocera.conf that do not interfear with frontend controlled configurations

Logs and data

No response

[IM0001GT]

I ran into this same issue. Settings save fine until you touch the RGB tool which seemed to work fine for one reboot, but after that everything comes up default on all subsequent reboots until I reflash the OS to the card.