Mupen64Plus Next Continues To Crash On Load?

Libretro Lakka
#1

When loading a game, the core immediately crashes. I’ve had this issue happen on Lakka since late 2020 on mutliple versions (32-Bit & 64-Bit) and clean installs. I thought it may be Raspberry Pi 3B related, but I was pretty floored seeing it repeated on the Pi4 out the box.

I checked out the log today, and this is the only error tags I’m seeing:

[ERROR] Failed to open libretro core: “/storage/cores/mupen64plus_next_libretro.so” [ERROR] Error(s): libpng16.so.16: cannot open shared object file: No such file or directory

The core is in the directory, and I’ve even updated it to the latest available. I also updated to the latest version of Lakka and had no change in behavior (I since rolled back to 3.4). My video driver is GL.

Any ideas how to get this work? I’m usually pretty good figuring this stuff out, but I’m tapping out on this one lol.

#2

oh dang, there’s nothing you can do about that, AFAIK, but that should be easy for the lakka folks to fix. @gouchi

#3

@paqman3D Might open an issue so that we don’t forget about it :wink:

Thank you.

#4

[ERROR] Failed to open libretro core: “/storage/cores/mupen64plus_next_libretro.so” [ERROR] Error(s): libpng16.so.16: cannot open shared object file: No such file or directory

Are you using the core from Lakka or you did add it from the Libretro buildbot ?

Because it should be loaded from

/tmp/cores/mupen64plus_next_libretro.so

Thank you.

#5

Hey, I’ll get around to making an issue on GitHub later, but I did change the directory and ended up with the same error :frowning:

“[ERROR] Failed to open libretro core: “/tmp/cores/mupen64plus_next_libretro.so” [ERROR] Error(s): libpng16.so.16: cannot open shared object file: No such file or directory [INFO] [Core]: Content ran for a total of: 00 hours, 00 minutes, 01 seconds.”

#6

It is strange I don’t see the need for libpng in mupen64plus_next_libretro.so

ldd ./mupen64plus_next_libretro.so
	linux-vdso.so.1 (0x00007ffc1c7d6000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f140aeb3000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f140ae90000)
	libGL.so.1 => /usr/lib/x86_64-linux-gnu/libGL.so.1 (0x00007f140ae08000)
	libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f140ac26000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f140aad7000)
	libmvec.so.1 => /lib/x86_64-linux-gnu/libmvec.so.1 (0x00007f140aaab000)
	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f140aa8e000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f140a89c000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f1415a84000)
	libGLdispatch.so.0 => /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0 (0x00007f140a7e4000)
	libGLX.so.0 => /usr/lib/x86_64-linux-gnu/libGLX.so.0 (0x00007f140a7b0000)
	libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007f140a673000)
	libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f140a647000)
	libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007f140a641000)
	libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007f140a639000)
	libbsd.so.0 => /usr/lib/x86_64-linux-gnu/libbsd.so.0 (0x00007f140a61f000)
#7

you got the same error, because the files stored in /storage/cores overlay/supersede the “shipped” cores. Remove the file from /storage/cores, reboot and try again.

1 Like
#8

Okay, that did the trick. I had previously changed the directory of the cores, but did not remove them all from the folder. I just trashed everything in /storage/cores and set it to /tmp/cores. Bam, n64.

Granted, pi4 didn’t enhance much here but at least it works lmao. Thanks!