EmulationStation Crashes After Launching A Game or Config Menu On Debian / Ubuntu

mitu

I couldn't reproduce the error with up-to-date Ubuntu installation. Maybe this is specific cu Lubuntu or to an update/configuration, but it's not something that happens generally on Debian/Ubuntu.

You can run the EmulationStation through strace and see where it's getting stuck - waiting for some resource/file/GPU ? Is the GPD having a different video output and starting the emulator uses the other output ? Can't think what could be causing to not work - after initially working. A system update or configuration ?

gare

@mitu So I kind of got this fixed. I decided to switch from Lubuntu 24.04.1 LTS to the daily build of Lubuntu 24.10 and once I set that and Retropie up, it's pretty much been working perfectly.

The only issue I'm having now is a couple of packages are failing to install (from the main lr-mame2003 and lr-mupen64plus. lr-ppsspp also failed, but that's the only optional package I tried). They all report that their respective x_libretro.so was not found whenever trying. Here's what reported in the log for the lr-mame2003 for example:

src/common.c:1948:34: note: in expansion of macro ‘ROMREGION_GETTYPE’
1948 | int regiontype = ROMREGION_GETTYPE(region);
| ^~~~~~~~~~~~~~~~~
src/common.c:1973:101: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
1973 | log_cb(RETRO_LOG_DEBUG, LOGPRE "Allocated %X bytes @ %08X\n", romdata.regionlength, (int)romdata.regionbase);
| ^
make: *** [Makefile:901: src/common.o] Error 1
make: *** Waiting for unfinished jobs....
Removing additional swap
Could not successfully build lr-mame2003 - Arcade emu - MAME 0.78 port for libretro (/home/gare/RetroPie-Setup/tmp/build/lr-mame2003/mame2003_libretro.so not found).
/home/gare

mitu

@gare said in EmulationStation Crashes After Launching A Game or Config Menu On Debian / Ubuntu:

Here's what reported in the log for the lr-mame2003 for example:

That's an incomplete log and the error is probably printer earlier on. Which version of gcc is in the 24.10 preview ? lr-mupen64plus is not going to get anymore updates, you should use lr-mupen64plus-next instead.

gare

@mitu Apolgies, I'll provide the complete log underneath this post. My gcc version is 14.2.0. I'll try installing lr-mupen64plus-next instead now.

mitu

@gare Please use pastebin.com for large logs.

gare

@mitu Sorry again. I'll edit my post to remove the log. Here's the pastebin version https://pastebin.com/sFDf494m

lr-mupen64plus failed in a similar manner when trying to install

mitu

Yes, it seems there's a new warning promoted as error in gcc 14, the error is:

....
src/common.c: In function ‘read_wav_sample’:
src/common.c:439:46: error: assignment to ‘INT16 *’ {aka ‘short int *’} from incompatible pointer type ‘signed char *’ [-Wincompatible-pointer-types]
  439 |                         flac_file.write_data = result->data;
      |                                              ^
src/common.c: In function ‘readsample’:
...

As for lr-mupen64plus, it's probably best to disable it for anything except a Pi3 and below, since it's an archived project and will not get any updates. Use lr-mupen64plus-next, ~~which works fine.~~, but seems it's also not compiling due to another error.

gare

@mitu Is there anything I can do about that? Also here's the lr- mupen64plus log https://pastebin.com/hv4pKMAh . The lr-ppsspp log is too big for Pastebin

mitu

Use a LTS release so you don't get this kind of errors, gcc14 is rather 'new' and until projects are patched to fix the new errors they won't be working in RetroPie also.

gare

@mitu Thank you, switching to gcc-12 seems to have fixed the issue, as lr-mame2003 was able to compile fine. I'll try the others and will report back if I have anymore issues.

gare

@mitu not sure if I should make a new thread for this or not but I'm having a new issue where games open Retroarch fine but playing a game for a few minutes, Retroarch will hang, causing the sound to freeze making a single noise until the Terminal is forcibly closed. Doesn't seem to be emulation core specific as I had it happen with different systems. I tried running in debug but since it executes after the runcommand there wasn't any output, and the runcommand log didn't have any additional info

mitu

@gare You can get RetroArch to run in verbose mode by choosing to launch with verbose logging. Seems like an issue with the audio - perhaps PulseAudio/Pipewire gets stuck ? Does it happen also with standalone emulators (i.e. Mupen64plus or PPSSPP) ?