• Recent
  • Tags
  • Popular
  • Home
  • Docs
  • Register
  • Login
RetroPie forum home
  • Recent
  • Tags
  • Popular
  • Home
  • Docs
  • Register
  • Login
Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

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

Scheduled Pinned Locked Moved Help and Support
kiosk modeemulationstaioncrash
32 Posts 2 Posters 3.3k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M
    mitu Global Moderator
    last edited by 10 May 2019, 16:11

    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 ?

    H 1 Reply Last reply 10 May 2019, 16:32 Reply Quote 0
    • H
      hooperre @mitu
      last edited by 10 May 2019, 16:32

      @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

      4B ~ RPi PSU 5.1V / 3.0A ~ 32GB SanDisk microSD ~ 128GB USB

      M 1 Reply Last reply 10 May 2019, 17:19 Reply Quote 0
      • M
        mitu Global Moderator @hooperre
        last edited by 10 May 2019, 17:19

        @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.

        H 1 Reply Last reply 11 May 2019, 00:04 Reply Quote 0
        • H
          hooperre @mitu
          last edited by hooperre 5 Nov 2019, 14:14 11 May 2019, 00:04

          @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)

          4B ~ RPi PSU 5.1V / 3.0A ~ 32GB SanDisk microSD ~ 128GB USB

          M 1 Reply Last reply 11 May 2019, 04:11 Reply Quote 0
          • M
            mitu Global Moderator @hooperre
            last edited by 11 May 2019, 04:11

            @hooperre Did you forget to post the log ?

            1 Reply Last reply Reply Quote 0
            • H
              hooperre
              last edited by hooperre 5 Nov 2019, 14:14 11 May 2019, 13:13

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

              4B ~ RPi PSU 5.1V / 3.0A ~ 32GB SanDisk microSD ~ 128GB USB

              1 Reply Last reply Reply Quote 0
              • M
                mitu Global Moderator
                last edited by mitu 5 Nov 2019, 16:21 11 May 2019, 15:09

                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 ?

                H 1 Reply Last reply 11 May 2019, 17:23 Reply Quote 0
                • H
                  hooperre @mitu
                  last edited by 11 May 2019, 17:23

                  @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.

                  4B ~ RPi PSU 5.1V / 3.0A ~ 32GB SanDisk microSD ~ 128GB USB

                  M 1 Reply Last reply 11 May 2019, 17:25 Reply Quote 0
                  • M
                    mitu Global Moderator @hooperre
                    last edited by mitu 5 Nov 2019, 18:38 11 May 2019, 17:25

                    @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 !.

                    H 1 Reply Last reply 11 May 2019, 17:40 Reply Quote 0
                    • H
                      hooperre @mitu
                      last edited by hooperre 5 Nov 2019, 18:41 11 May 2019, 17:40

                      @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?

                      4B ~ RPi PSU 5.1V / 3.0A ~ 32GB SanDisk microSD ~ 128GB USB

                      M 1 Reply Last reply 11 May 2019, 17:43 Reply Quote 0
                      • M
                        mitu Global Moderator @hooperre
                        last edited by 11 May 2019, 17:43

                        @hooperre Maybe Esc or Enter ?

                        H 2 Replies Last reply 11 May 2019, 18:50 Reply Quote 0
                        • H
                          hooperre @mitu
                          last edited by 11 May 2019, 18:50

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

                          4B ~ RPi PSU 5.1V / 3.0A ~ 32GB SanDisk microSD ~ 128GB USB

                          1 Reply Last reply Reply Quote 0
                          • H
                            hooperre @mitu
                            last edited by hooperre 5 Dec 2019, 14:35 12 May 2019, 13:35

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

                            4B ~ RPi PSU 5.1V / 3.0A ~ 32GB SanDisk microSD ~ 128GB USB

                            M 1 Reply Last reply 12 May 2019, 15:08 Reply Quote 0
                            • M
                              mitu Global Moderator @hooperre
                              last edited by 12 May 2019, 15:08

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

                              1 Reply Last reply Reply Quote 0
                              • H
                                hooperre
                                last edited by hooperre 13 May 2019, 01:14

                                @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.

                                4B ~ RPi PSU 5.1V / 3.0A ~ 32GB SanDisk microSD ~ 128GB USB

                                1 Reply Last reply Reply Quote 0
                                • M
                                  mitu Global Moderator
                                  last edited by 13 May 2019, 16:25

                                  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:

                                  1. Install gdb with
                                  apt -y install gdb
                                  
                                  1. 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.

                                  H 1 Reply Last reply 13 May 2019, 17:20 Reply Quote 0
                                  • H
                                    hooperre @mitu
                                    last edited by hooperre 13 May 2019, 17:20

                                    @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

                                    4B ~ RPi PSU 5.1V / 3.0A ~ 32GB SanDisk microSD ~ 128GB USB

                                    M 1 Reply Last reply 13 May 2019, 17:37 Reply Quote 0
                                    • M
                                      mitu Global Moderator @hooperre
                                      last edited by 13 May 2019, 17:37

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

                                      H 1 Reply Last reply 13 May 2019, 18:03 Reply Quote 1
                                      • H
                                        hooperre @mitu
                                        last edited by 13 May 2019, 18:03

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

                                        4B ~ RPi PSU 5.1V / 3.0A ~ 32GB SanDisk microSD ~ 128GB USB

                                        1 Reply Last reply Reply Quote 0
                                        • M
                                          mitu Global Moderator
                                          last edited by 20 May 2019, 16:24

                                          I did some tests and I can't get a crash because of Kid mode. Would it be possible to make a zip of all the gamelists.xml and collections you have (no ROMs) and upload it somewhere ? You can easily create an archive with

                                          # zip the gamelists
                                          find $HOME/RetroPie/roms/ .emulationstation/gamelists/ -name gamelist.xml | xargs zip -P retropie -@ gamelist.zip
                                          # zip the collections
                                          zip -P retropie -r collections.zip $HOME/.emulationstation/collections/
                                          H 1 Reply Last reply 21 May 2019, 01:23 Reply Quote 0
                                          12 out of 32
                                          • First post
                                            12/32
                                            Last post

                                          Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

                                          Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.

                                            This community forum collects and processes your personal information.
                                            consent.not_received