Adding scripts to ES events destroys system log output
Closed this issue · 1 comments
Batocera build version
v38
Your architecture
x64
Your Graphic Processor Unit (GPU)
Dedicated (e.g. GTX 1050; Radeon R9 380)
Graphical brand
Nvidia
Issue description
Adding ledspicer activation scripts to /userdata/system/configs/emulationstation/scripts/event folders turns the es_launch_stdout.log output into a mess of numbers and letters, and eliminates all output from es_launch_stderr.log entirely.
Expected result
No response
Reproduction steps
- Add the attached custom.sh script to /userdata/system, and run a chmod +x command on it to let it run as a startup script. This isn't part of the issue afaik, but it's my workaround for bug batocera-linux/batocera.linux#10388.
custom.zip - Add the contents of the ledspicer zip to /userdata/system/configs/ledspicer. Also not part of the issue afaik, but necessary.
ledspicer.zip - Add the contents of scripts.zip to /userdata/system/configs/emulationstation.
scripts.zip - Reboot, and run a game. Open es_launch_stderr.log and es_launch_stdout.log, and they're probably as messed up as mine.
Logs and data
There isn't anything special in any of these files, least of all the ES scripts. They're just making calls to the emitter part of ledspicer to load various led animation profiles when games start and end, and when the screensaver starts and ends.
This test was done on a recently factory reset copy of v38 batocera. I had seen this bug before (hence the factory reset), so I tracked it by loading a game and looking at the logs after every step of installing my ledspicer setup. Adding the ES scripts were the last step, and that's when the logs became corrupted.
Moving to batocera-emulationstation repo for resolution