Hello, I found a solution. :)

I uninstall and reinstall the retropiemenu.

Thanks!

okay thanks

@MWGemini
For my Pi Zero's I have a couple of the Anker 2-4-port USB wall chargers around the house. They output up to 2.1 amps (might be 2.4) per channel, and I've switched everything over to Amazon Basics micro USB cables which seem very nice. The power supply/cables hopefully aren't the problem as they power all the other working Zero's I have just fine.

@BuZz
I have another topic open about getting my ethernet adapter working since my 2.4ghz wireless has been flaky. Will RetroPie (like version 4.0.2. or maybe 4.1.0) give me a warning if it fails to compile or update something like EmulationStation for example? I know you mentioned RetroPie was JUST updated to NOT clear error messages for better troubleshooting.

I'm wondering because I'm now actually watching my other Pi (not this one I'm having problems with) run all the updates and I don't think I've ever seen that much code flash across the terminal window on the ones which have had issues (it's up to like 15+ pages of code, and it's been doing the update for maybe an hour so far and I don't know how much longer it has to go). I can never remember the problematic ones taking longer than maybe 20-30 minutes to update something which has me wondering if they're really failing to update, and I missed any error message which flashed up, and that's been why I could never fix them.

--once I'm done updating this working Pi Zero I'll see if the malfunctioning one can use the Ethernet adapter (but I'm pretty sure only newer versions of RetroPie can use that ethernet adapter since I could never get it working before - so I might be stuck without internet access to test anything out on the malfunctioning Pi Zero).

@ScottF80 That's it - and you solved all by yourself ;)

@Pixel0501 when you say "my" password, you aren't talking about your Mac OS password are you? The default password for retropie is ........ raspberry. Another question is have you logged in via ssh before? Because if you have and had to start over by reinstalling retropie, Mac OS has a security feature that keeps logs of MAC addresses and ssh keys, and when you try to log in again it will stop you since the new retropie install will not be using the same key. Mac OS tells you though and tells you what file you have to edit to remove that log.

Hi everyone, thanks for the answers, I formated the sd card and reinstalled RetroPie and the problem has not happened again... I think something went wrong when I installed several themes or updated the software. If it happens again I will copy the logs but now everything is allright.

I guess it was not a good idea to test all themes with the first model of raspberry, I'm considering upgrading to a better hardware...

Thanks :)

I tried to setup a script and possible extension for retropie here: https://github.com/daeks/jslisten-abort
The intention of this extension is to be able to kill all emulators only with a controller (for example: scummvm if you have no keyboard available)

Unfortunately emulators like scummvm are started with bash script. Is there a better way to fetch the binary for such emulators?

@chanh55 yes. Remove the eed=1 part

The behavior I'm seeing now a days is consistent between EmulationStation and the RetroPie-Setup Script. The big outlier for me is the Raspi-Config menu being the opposite of everything else. Has anyone discovered a way to swap the confirm/cancel button behavior for Raspi-Config?

@Joebo happy to help - glad you got it working