RetroArch 1.6.9 Crashes When Navigating

hansolo77

@mitu said in RetroArch 1.6.9 Crashes When Navigating:

@hansolo77 Hm, seems something similar to https://github.com/libretro/RetroArch/issues/5768, recently reported and fixed.

The crash happens anytime I try to navigate around in the menus, not just when I try to browse the achievements. That was just an example. I get the crash by loading up RetroArch standalone, without any cores loaded.

@dankcushions said in RetroArch 1.6.9 Crashes When Navigating:

you shouldn't use this retroarch.cfg - it is not a retropie default. retropie default ones will be saved as retroarch.cfg.rp-distwithin the config folder after an update of retroarch - you should rename that to retroarch.cfg

Shouldn't the Setup script do all that automatically? Why would I have to manually manipulate the config files? And if I replace the retroarch.cfg files with the default one from RetroPie, won't that remove all the customizations currently inside the exiting one?

jonnykesh

@hansolo77 I'm using the latest RA (xmb menu)and it runs fine. It's most likely your customisations causing the issue. Just rename the file rather than deleting it. You can restore it later if needed.

dankcushions

@hansolo77 said in RetroArch 1.6.9 Crashes When Navigating:

@mitu said in RetroArch 1.6.9 Crashes When Navigating:

@hansolo77 Hm, seems something similar to https://github.com/libretro/RetroArch/issues/5768, recently reported and fixed.

The crash happens anytime I try to navigate around in the menus, not just when I try to browse the achievements. That was just an example. I get the crash by loading up RetroArch standalone, without any cores loaded.

@dankcushions said in RetroArch 1.6.9 Crashes When Navigating:

you shouldn't use this retroarch.cfg - it is not a retropie default. retropie default ones will be saved as retroarch.cfg.rp-distwithin the config folder after an update of retroarch - you should rename that to retroarch.cfg

Shouldn't the Setup script do all that automatically?

how do you mean? the setup script won't automatically overwrite your config with the defaults, as you may not want that. i have suggested that we add a function to "reset to defaults", but that requires a bit of work.

Why would I have to manually manipulate the config files? And if I replace the retroarch.cfg files with the default one from RetroPie, won't that remove all the customizations currently inside the exiting one?

yes, but my point is that you have obviously tweaked your retroarch.cfg manually as it's huyge. normally it would be a much smaller file, even if you have tweaked settings via supported methods.

eg, there's stuff in your pasted .cfg that is non-default, such as menu_driver = "xmb"

if you want to run your own setup, that's fine, but we can't support it :) however i suspect your issue is nothing to do with the settings. settings shouldn't cause a crash.

hansolo77

@dankcushions I'm not against trying. I just wanted to understand why and how this might help. I will attempt this again shortly. I'm on vacation this week so I have plenty of time. It's also not like my life depends on this, I have a working backup. :)

hansolo77

I did as suggested, and replaced the current retroarch.cfg with that of retroarch.cfg.rp-dist after updating RetroArch. Everything went to crap. The old original interface to RetroArch loaded (not really a problem) but when I tried to change it to the one I'm familiar with, I couldn't navigate. My Xbox360 pad, while being recognized (evident in the onscreen displays) wouldn't work. So I pulled out my keyboard. It too didn't work. I rebooted multiple times to try and see what was going on. My "new" retroarch.cfg still looked the same as the rp-dist one, with all the lines *commented out. I noticed during one of the reboots that it was indicating my Mayflash Adapter was being recognized as "Input 0". So I connected a controller to that port, and still nothing. I was about to pull my hair out and forget the whole thing. Then I took a gander at the link you posted (supported methods). I had never really used that method to change settings. I always made the changes INSIDE RetroArch, and enabled the "Save Configurations on Exit" option. Anyway, while in there, I saw a utility to let me change the controller mappings, so my Xbox360 controller would be in #1. After that, things started falling back into place. When I look at the retroarch.cfg file now, all the *comments are gone, and it's back to being a HUGE file. However, the original file was 1699 lines long, this new one is 1701. So there are at least 2 new lines, plus the things that might have changed, settings that were removed, etc. In either case, it looks like it's working now. Seems like a lot of unnecessary work to get a simple RetroArch update. I've updated plenty of times in the past and never had to do that. Weird.

madmodder123

@hansolo77 I am having this same issue after updating from RetroPie 4.3.6 to 4.3.7, I tried using the .cfg files from 4.3.6 but the issue still occurred. I then deleted all the cfgs and then it worked with only the keyboard, so now I have to set up all of my settings again :'(

I am still glad I keep backups though, it makes diagnosing issues or reverting back easy. I started a changelog file so I can track which changes have been made between backups.

Anyways I guess ill give the Configuration Editor a shot.. Thanks

hansolo77

Yeah after various attempts at fixing it, it looks like the problem is with the way RetroPie adjusts the retroarch.cfg file in preparation for the new RetroArch update (or possibly the LACK of preparation for it). In all my attempts, every single time I updated RetroArch into 1.6.9, it broke the config file.

Another off topic issue the new version of RetroArch is having is that it wants to create a new retroarch.cfg file for every system, and seems to ignore the default one located in /opt/retropie/configs/all. Specifically, if I delete the one located in /opt/retropie/configs/nes, then launch an NES game, it creates a new config file that has completely ignored the default settings (like the chosen menu driver, menu opacity, even RetroAchievement login, not to mention the controller setup). This is getting very upsetting, especially because I spent nearly my entire vacation last week coming to the conclusion that it's a new feature in RetroArch that RetroPie is not set up to work with yet.

Speaking of which, I will probably need to create a new support topic for that. But yes. Erasing the default retroarch.cfg file located in /opt/retropie/configs/all and replacing it with the "skeleton" config retroarch.cfg.rp-dist does seem to fix the problem with the crashing.

deviath

Running latest Retroarch on Nvidia Shield TV and when I navigate over N64 or NES collections specifically the whole system locks up and crashes

mitu

@deviath You might try the Libretro forums for reporting this, the forum is for the RetroPie project.

deviath

@mitu copy that. Thank you