EmulationStation Kiosk-USB Specific Crash - Can it be Replicated?

hooperre

~~Okay so appears I should have been looking at es_log.txt.bak. Here's a dump:~~

Edit: I see this is a clean exit now... oops.

lvl2: 	 req sound [detailed.launch]
lvl2: 	   (missing)
lvl2: 	Attempting to launch game...
lvl0: 	VolumeControl::init() - Failed to find mixer elements!
`lvl2: 		/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ nes /home/pi/RetroPie/roms/nes/Mega\ Man\ 4\ \(USA\).zip`
lvl2: 	Creating surface...
lvl2: 	Created window successfully.
lvl2: 	Added known joystick Wireless Controller (instance ID: 0, device index: 0)
lvl0: 	VolumeControl::init() - Failed to find mixer elements!
lvl2: 	Added known joystick Wireless Controller (instance ID: 0, device index: 0)
lvl2: 	Added/Updated 1 entities in '/home/pi/RetroPie/roms/nes/gamelist.xml'
lvl2: 	EmulationStation cleanly shutting down.

mitu

Looks like a case of 'USB not ready before ES starts' thus not finding any systems on the disk. Being in Kiosk Mode, the retropie system is also not available, so this might lead to a crash. Restarting ES works because the USB is available and the systems are correctly read.

The messages from the log don't seem related to your problem and neither the fact that you have sub-folders.
What you can do is to exit Kiosk mode and see what happens on the 1st run. If you get only the RetroPie system, then my guess is correct. Can you post your es_settings.cfg file from ~/.emulationstation ?

hooperre

@mitu said in EmulationStation Kiosk-USB Specific Crash - Can it be Replicated?:

Looks like a case of 'USB not ready before ES starts' thus not finding any systems on the disk. Being in Kiosk Mode, the retropie system is also not available, so this might lead to a crash. Restarting ES works because the USB is available and the systems are correctly read.

The messages from the log don't seem related to your problem and neither the fact that you have sub-folders.
What you can do is to exit Kiosk mode and see what happens on the 1st run. If you get only the RetroPie system, then my guess is correct. Can you post your es_settings.cfg file from ~/.emulationstation ?

Thanks for responding, @mitu.

https://pastebin.com/krfXpm0P

mitu

@hooperre There doesn't seem anything special with your settings. I was checking if you're using the Local Art option, since that's something new in Emulationstation 2.8, this year's release.
I'll see if I can reproduce this or get a simpler test case.
As a workaround, try adding a delay before Emulationstation starts, add a line with sleep 3 in the autostart.sh file in /opt/retropie/configs/all/autostart.sh, just before the line that starts emulationstation.

hooperre

@mitu Mannnn I hate to report this but sleep 3 sleep 5 and sleep 50 all failed.

I’ll paste the es_log.txt here: https://pastebin.com/6hJgYatE
es_log.txt.bak: https://pastebin.com/wq6Vc7jh (seems the same)

mitu

@hooperre Did you forget to post the log ?

hooperre

@mitu Posted. Seems like the log is just abruptly interrupted.

mitu

Yes, the logs are the same, it seems the crash happens when loading the collections starting with [space]. You say that it only happens on 1st load ? Did you have another ES version before this crash started happening ?

EDIT: is there any crash error message on the terminal ?

hooperre

@mitu To be honest, I only use Kiosk when copying my SD for my cousin and brother so I'm not sure pre vs. post update.

The crash message is the "Emulationstation has crashed" blue screen. Suggests I reset rom permissions / check gpu split. I can post a picture later if you're not sure what I'm referring to from memory.

Is there another character I can use to bring the collections to the top besides a space? I can test that when I'm back from work.

mitu

@hooperre said in EmulationStation Kiosk-USB Specific Crash - Can it be Replicated?:

The crash message is the "Emulationstation has crashed" blue screen. Suggests I reset rom permissions / check gpu split. I can post a picture later if you're not sure what I'm referring to from memory.

Aha, I know that message. It happens when ES crashes, but the actual crash might behind that message (in the terminal screen). Is there such message ?

EDIT:

Is there another character I can use to bring the collections to the top besides a space? I can test that when I'm back from work.

Try using _ or !.

hooperre

@mitu How would I get underneath the message? I've tried Ctrl+C but it seems that the keyboard doesn't work. I know there is an exit or back option, but there's no way for me to select it because it seems like all the inputs don't work at that point. Can I SSH in and somehow see it there? exit?

mitu

@hooperre Maybe Esc or Enter ?

hooperre

@mitu I’m fairly certain I’ve tried both as I have a keyboard with it currently. No other way to see that error?

hooperre

@mitu Confirmed. Basically freezes the system. No inputs work.

mitu

@hooperre Try to login to the system via SSG and run killall dialog when the message is on-screen. I forgot about this option.

hooperre

@mitu I basically just see the error screen above a regular terminal as if you exited EmulationStation after using the killall dialog command, but I don't see the actual error message anywhere.

Only have collections starting with letters. es_log.txt here: https://pastebin.com/hszxWE2V.

mitu

OK, time to bring up the big guns. If you have SSH access to the Pi, you can try to get a backtrace from the crash:

Install gdb with

apt -y install gdb

Replace the autostart.sh command to start ES with

gdb -batch -ex "run" -ex "bt" -ex "quit" /opt/retropie/supplementary/emulationstation/emulationstation 2>&1 > /tmp/es.log

So, instead of the normal autostart.sh which contains just

emulationstation #auto

you should have

# emulationstation #auto
gdb -batch -ex "run" -ex "bt" -ex "quit" /opt/retropie/supplementary/emulationstation/emulationstation 2>&1 > /tmp/es.log

You can find the autostart.sh file in /opt/retropie/configs/all/autostart.sh, do a backup of it just in case.

Reboot, get the crash message, but don't stop the Pi right away, just SSH in and get the /tmp/es.log file which should contain the crash place in Emulationstation.

hooperre

@mitu

My autostart.sh appears as follows:

emulationstation #auto
gdb -batch -ex "run" -ex "bt" -ex "quit" /opt/retropie/supplementary/emulationstation/emulationstation 2>&1 > /tmp/es.log

~~I did have to change file permissions to 777 in the created directories above to view them. Am I missing a sudo command anywhere? (sudo gdb doesn't seem to make it work.)~~

~~sudo nano /tmp/es.log shows nothing.~~

Am dumb was missing the comment part of # emulationstation #auto on line 1.

es.log: https://pastebin.com/BpXY8K3A

mitu

@hooperre Well, that's the error right there :|. Let's see how we can solve that.

hooperre

@mitu Haha hey thanks for sticking with me this far. It's all gibberish to me so hope you can come up with something! :)