Catastrophic lr-VICE failure

JimmyFromTheBay

So, I should be experienced enough by now not to make such a stupid rookie mistake, but today I updated lr-VICE and boy do I ever wish I hadn't.

I'm still running (I think) Buster and the update has completely destroyed C64 support (haven't checked other Commodore platforms yet so it may be even worse than it seems).

If I try to load .D64 files they load, very slowly, and run for a bit, then lock up Retroarch. If I try to run .CRT files they crash, producing a 71MB runcommand.log file over a million lines long (1,220,801 lines to be precise), most of which are this:

[INFO] [Environ]: RETRO_ENVIRONMENT_SET_CORE_OPTIONS_DISPLAY.

but buried in amongst those are a few like this:

[libretro INFO] Migrating 'zoom_mode' to 'crop'..
[INFO] [Environ]: UNSUPPORTED (#70).
[libretro INFO] Migrating 'zoom_mode_crop' to 'crop_mode'..
[INFO] [Environ]: UNSUPPORTED (#70).
[libretro INFO] Migrating 'mapper_zoom_mode_toggle' to 'mapper_crop_toggle'..

So that would seem to be the heart of the problem. The big question, then, is "How in the bejeesus do I undo this accursed update?"

I have a working backup of the entire OPT directory (and therefore the entire OPT>RETROPIE>EMULATORS>VICE directory, but every file currently in OPT>RETROPIE>EMULATORS>VICE>BIN says it was last updated in 2021 so I'm not sure replacing those would help.

Is there a way out of this horrific mess?

(NB Please please please do not answer "Yeah, install a newer version of Retropie and rebuild it from your backup", because that would represent a minimum of about a month's work, not least because I have about 100 systems installed through @Folly's module script generator that would all have to be redone from scratch since it now works in a completely different way.)

sleve_mcdichael

@JimmyFromTheBay said

I updated lr-VICE

every file currently in OPT>RETROPIE>EMULATORS>VICE>BIN says it was last updated in 2021

You updated libretro-vice but that's the folder for stand-alone. Try check /opt/retropie/emulators/libretrocores/lr-vice instead.

JimmyFromTheBay

@sleve_mcdichael Ha, I'd just figured that out as your reply popped up. So it looks like I actually need to put my old vice_x64_libretro.so (dated 2021) into opt>retropie>libretrocores>lr-vice to replace the one in there now dated 2025 (actually, probably need to restore the whole 2021 lr-vice folder), but WinSCP won't let me do that because of permissions. I can never ever ever remember how to get round this, can someone remind me?

JimmyFromTheBay

Ah, found it:

sudo chown pi:pi /opt/retropie/libretrocores/lr-vice

Did that for the main and subfolder and managed to replace the crappy broken new files with the working old ones. All fixed. Thanks for the reply :)

Folly

@JimmyFromTheBay said in Catastrophic lr-VICE failure:

Ah, found it:
sudo chown pi:pi /opt/retropie/libretrocores/lr-vice
Did that for the main and subfolder and managed to replace the crappy broken new files with the working old ones. All fixed. Thanks for the reply :)

I see how you have done it otherwise you would not be able to replace the files.
If you don't mind you can leave it that way.
However, notice that these folders normally have root user rights.
In principle you should turn them back to root.