Retroarch not loading citra core.

[ShadMessa]

trafficstars

Hi , I installed retroarch 1.7.3 from snap, it's working properly with all cores that i use, but when i try to load citra for 3ds it just won't do anything it send me back to the main menu with out loading it . i use ubuntu lts 18.04.1 and a 660 ti with 390 driver vesion can any one help me please ?

[tabetai]

Same, not loading Citra core. Error:

[ERROR] Error(s): /home/username/snap/retroarch/129/.config/retroarch/cores/citra_libretro.so: symbol _ZTINSt6thread6_StateE, version GLIBCXX_3.4.22 not defined in file libstdc++.so.6 with link time reference

[hizzlekizzle]

Yeah, this has to do with a mismatch in the libc version in the snap vs the one used to build the core. I'm not sure what can be done about it, unfortunately. AFAIK, the buildbot isn't building it any differently than any other cores, so I'm not sure why it's the only core that's giving us this issue. :/

[ShadMessa]

is there a way to activate debug mode to check what is wrong ???

[soichih]

I am having a similar issue with dolphin-libretro. I don't know much about snap, but is there a work around? I tried to copy the libstdc++ from my /usr/lib to /snap/retroarch/current/lib/x86_64-linux-gnu but it says that it's read only file system.. Does anyone know how I can edit the content of snap?

[hizzlekizzle]

The key would be to build the cores (dolphin and citra) with Trusty, which is the distro that the snap builds are based on. Then, you could just drop those Trusty-built libs into your snap's cores directory instead of the buildbot versions.

We could also try using Trusty on our buildbot instead of the newer release we currently use, but that would be a lot of work on our end, unfortunately.

[soichih]

@hizzlekizzle I am not sure how to do this > "drop those Trusty-built libs into your snap's cores directory instead of the buildbot versions". Could you point me to some doc/readme showing how to do this? I tried to update the content under /snap/retroarch but it says that it's read only file system..

[hizzlekizzle]

Set up a Trusty system in a VM or something just to build the core libraries, then take those cores and put them into ~/snap/retroarch/current/.config/cores/.

[Athorus]

Any progress about this bug ? Will Snap package work one day ?

[orbea]

Yeah, this has to do with a mismatch in the libc version in the snap vs the one used to build the core.

Fwiw the buildbot runs this script on built cores in an effort to fix issues like this, but I'm not sure why its not working here.

https://github.com/libretro/libretro-super/blob/master/retrolink.sh

This link may still offer clues.

http://www.lightofdawn.org/wiki/wiki.cgi/NewAppsOnOldGlibc

[hizzlekizzle]

I made both cores statically link glibc which gets past the original issue, but they both crap out on other, less obvious issues now.

[orbea]

I'd guess the less obvious issues are a consequence of the statically linked glibc.

[hizzlekizzle]

Possibly, but I suspect it's related to the snap sandboxing. I've been meaning to ask @RobLoach if they work with the FlatPak package now or not.

[RobLoach]

Had a similar issue on Flatpak: https://github.com/flathub/org.libretro.RetroArch/issues/81 ... Buildbot uses different development libraries than what's available on the different platforms. orbea and hizzlekizzle fixed it in Dolphin by statically linking the libraries.

Haven't tested Citra.

[Mored4u]

Still not load Citra Core (Tested RetroArch v1.8.1 x64)

[hizzlekizzle]

This should be fixed now in the edge channel

[gouchi]

@ShadMessa @tabetai @Mored4u Please reply so that we can close this issue if it is fixed. Thank you.