Press F4 in Emulation Station to go to the command console. Then enter:

sudo apt clean # clears the update cache sudo apt autoremove # removes installed packages that are no longer needed by other packages (so-called dependencies) exit # exits the console back to Emulation Station

Thanks for your responses.

@greenhawk84
I remember reading in the github page somewhere there was an update involving the joy2key package and you may need to manually update this package.

EDIT: Found the related thread:
https://retropie.org.uk/forum/topic/31092/controller-no-longer-works-in-retropie-setup-launching-menu-es-themes

@breadncup There is a new version of Kodi, but with my limited technical knowledge, basically, many of the older apps on it won't work on it.

See https://retropie.org.uk/docs/Updating-RetroPie/

@roslof @mitu

Thanks for exploring this one - I assumed that my RetroPie upgrade had overwritten my retroarch.cfg files. The advice here has fixed my missing shaders in my install (a 64-bit Raspberry Pi OS install).

Running and updating the setup script, navigating
P Manage packages
C Core
43 Retroarch
U Re-install (from source)
has fixed the problem for me.

@greenhawk84 said in How often do you fresh build?:

Hello, just curious about something I have never done until I have to with a new Pi model or mandatory change, which is start over again with a fresh install. How often do you do this?

Like others here, I also don't do it without good reason, e.g. when I switched from my Pi 3b to my new Pi 4 last spring. I also have customised my installation pretty much, so a new installation would require a good amount of re-configuration, even if most configurations can just be copied over from the old system.

I often wonder if so many updates through a package update eventually cause regressions.

RetroPie is built on Linux which in my long lasting experience doesn't "litter" the system over time as much as Windows does. You usually don't have to clean up or re-install a standard Linux system at all. As far as I can tell as a mere (power) user, RetroPie itself is also pretty neatly designed in the same way, so you shouldn't fear any regressions by just updating it via the RetroPie setup.

All that said, one important thing for any system is to back it up on a regular basis. Apart from failed updates or operating errors, every hardware can break any day for a number of reasons. See the Docs about Making a Backup.

@sleve_mcdichael Thank you. That worked for me. I'll make sure not to change my login in the future -_-

@valabrax said in Which files/directories should I restore after doing a fresh image install?:

Looking at the backup methods on https://retropie.org.uk/docs/Updating-RetroPie/ I think the best one for me in this situation is to backup the bios, configs, and roms directories via the samba shares. However, assuming the update works perfectly, which of these directories should I copy back over to preserve my roms, save states/files, and configurations (like controller configs and core-level configs). I'm assuming just the roms and configs directory and that I should not copy bios back over to the new image, but I wanted to check and be sure.

as the docs says, you'll want to backup all 3 https://retropie.org.uk/docs/Updating-RetroPie/#backup-option-2

By installing from source and now doing a new image install, am I nuking my micro-sd card with writes? I have no idea how many writes an install from source does, but it took hours to finish.

it's not ideal but during development i do many days worth of rebuilds and my SD cards tend to last years before crapping out.

If you have a Linux system, yes. Windows cannot read the SDcard's contents. You may take a backup as an .img (with Win32DiskImager, as mentioned in the docs) and try to open it with 7Zip.

The favorites are stores in the gamelist.xml file of each system. As @Lolonois said, if you copy the config you should be alright.

Update your Retropie-Setup script - make sure you're using the latest version - and see if you get the same issue during update.

@mitu , @BuZz Thank you both :)

@shavecat To elaborate a bit (because I'm a little bored this evening): You pretty much don't ever need to be acting as the actual root user. Especially if you are new to Linux. There is a high chance of messing things up if you start working directly as the root user.

Instead, as we've mentioned, you should use sudo. But only when you need to! sudo stands for super user do. The super user is the root user. In other words: When you run a command with sudo in front of it, you are running it as the root user for just that one command. It's a nice way to elevate your rights temporarily when needed.

But I can't stress this enough: Don't run commands as sudo unless you absolutely have to! Any file or path that is created while sudo'ing, will be owned by root. And if that was not the intention, you will have issues later on, when the ordinary pi user tries to access those files or paths.

I know this is an old thread, but its one of the many I have been over while trying to find a solution to this problem.

Mind you I'm running Steamlink as a port from RetroPie on a Pi4B 8GB.

Heres what I had to do to resolve the issue for myself.

In the Rapberry Pi Config file; Disable Underscan Disable Screen Blanking

Make sure Steamlink and other packages on your device are up to date.

Make sure that your Pi is outputting the same resolution or lower to your TV or monitor as the PC that the games are actually running on are outputting to its monitor. Eg. If your PC is running the games on a 1080p monitor, you likely wont be able to steam link from the Pi on a 4K TV @ 2160p without the black screen issue. I just set the display output in both my pi config and retro pie to 1080p to match my PC monitor and now Im playing without issue.

Hope this helps anyone whos still stuck with this issue.

Thanks for the heads up.

Thanks for the info. I will look into the script issues you mention and will move it to optional when I've tested.

Ok, I could solve it. There must have been a problem with IPv6, deactivating it solved the problem as in this thread:

https://retropie.org.uk/forum/topic/28939/updating-broken-connection-time-out/7

Maybe this should be added to the documentation or the FAQ or somewhere as it seems to affect some people.

I deactivated it according to this guide:

https://www.leowkahman.com/2016/03/19/disable-ipv6-raspberry-raspbian/

@mcreek Please show a screenshot of the usb stick on your PC with the folder name.

@retro81 Actually I may make it ask the user to update from RetroPie-Setup, to keep updating handled in one place.