Yuzu: SEGFAULT when opening configuration on linux distros shipping OpenSSL

Created on 7 Oct 2019  Â·  30Comments  Â·  Source: yuzu-emu/yuzu

Hello! Whenever I try to open the configuration window, yuzu segfaults.

First when launching yuzu I had an issue of missing libsndio.so.6.1, so I symlinked to libsndio.so.7.0.

regression

Most helpful comment

I'm currently working on a Flatpak version of yuzu. That will simplify things greatly.

All 30 comments

Can confirm, this is very real. Seems to have started after mainline 804 roughly, and it isn't an issue in 799.

After replicating this behaviour, I have confirmed that this is not an issue with yuzu. You are experiencing the segfault because you are only providing libraries derived from OpenSSL (https://www.openssl.org/) and not LibreSSL (https://www.libressl.org/). Either compile yuzu from source (as described at https://github.com/yuzu-emu/yuzu/wiki/Building-For-Linux and using the provided Git submodules, which includes LibreSSL), or build these libraries using the latest release of LibreSSL and then use the precompiled version of yuzu (specifying the path to the LibreSSL libraries with LD_LIBRARY_PATH).

I'm not compiling the build myself, I just use binary artifacts from https://yuzu-emu.org/downloads/

Yes, I suspected as much. Your issue is that the OpenSSL versions of the required libraries are installed on your system. If you provide the LibreSSL versions also (being careful to avoid conflicts), then all will work as expected.

Any chance for a build with the correct libraries packaged together?

I'm currently working on a Flatpak version of yuzu. That will simplify things greatly.

That's great to hear! Any chance for an AppImage build also?

That is also a possibility. I have been looking into qtlinuxdeploy, but the Flatpak version will probably make such a thing redundant. You can expect to see the Flatpak version over the coming days.

On 9 Oct 2019, at 22:56, Valters notifications@github.com wrote:

That's great to hear! Any chance for an AppImage build also?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

@7eia We are currently internally developing an official flatpak that should release very shortly. We would appreciate if you did not distribute your flatpak as it would cause confusion amongst our linux users. Thanks for your cooperation.

@DarkLordZach Close call. I was about to publish my finalised and fully-functioning yuzu Flatpak. I'll hold back though. Having said that, I was actually instructed to put this together by yuzu developers over on the Discord sever. More internal communication would probably be beneficial for all. Regardless, since you are already working on this, I will stop work on it immediately.

@7eia We would like your assistance in ironing out the remaining issues on ours.
Feel free to hop on our Discord server and shoot me a message.

Yeah, building from source seems to let me open the configuration.

Still, this shouldn't be an issue, many linux distros use OpenSSL and flatpaks are a bandaid fix in my opinion.

@FaithLV if it works, its worth a try though.

Linux generally requires some maintenance and customization in order to get the desired setup so I'm sure most people wouldn't mind.

@FaithLV Flatpaks were specifically designed to solve this dependency issue...
https://www.flatpak.org/

Regardless I'm glad you got it working.

I know what flatpaks are and I dislike packaging dependencies for each program separately. But that's beside the point.

Another segfault when launching a game ;)

@FaithLV separate issue or??

How close are we to a fix yet, just making sure the thread hasn't died. :3

[ 3.579842] Service.ACC core/hle/service/acc/profile_manager.cpp:ParseUserSaveFile:325: Failed to load profile data from save data... Generating new user 'yuzu' with random UUID.
Process 39571 stopped

thread 9, name = 'Thread (pooled)', stop reason = signal SIGSEGV: invalid address (fault address: 0x0)
frame #0: 0x0000000000000000
error: memory read failed for 0x0
gdb wouldnt work gave Starting program: /usr/local/bin/yuzu
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".

Temporary breakpoint 1, 0x0000000000551e80 in main ()
(gdb) q

thats the debug info i got from QT on the crash it still happens on downloaded builds

I'm experiencing this issue or one very similar on Mint 19.1, after building it from source myself.

Same issue on Kubuntu 19.10 (and 19.04).
Compiled using the standard build instructions (using yuzu-mainline in release mode).

BT from the latest attempt attached.
yuzu-bt-20191216.log

Ran into the same problem and decided to compile it myself, which did work until I tried today and got this error. Does Yuzu require a newer version of QT than what comes with Ubuntu 18.04?

` * The installation package was faulty and contained

 "/usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5Gui_QWaylandEglPlatformIntegrationPlugin.cmake"`

I've both built it and used provided binaries, but I can't open configure :(

I'm also experiencing the crash, both with the provided binary and building from source.

Hey @FearlessTobi , I tried applying your patch and rebuilding locally, it still crashed when opening the configure menu... :(

@victords Have you tried changing bcat_backend to null in your ~/.config/yuzu/qt-config.ini file? The patch does not have any effect if you already have one, I assume. That fixes it for me.

@EliaGeretto thanks, it worked!

Now I was able to load a game (Snipperclips), but the input doesn't work at all... I tried with the keyboard and with a joystick (the joystick is recognized in the configuration screen, I was able to set all the keys correctly).
Should I open a different issue for this or is there some simple solution/something I'm missing?
Thanks!

Probably fixed by #3675 as now httplib and libzip agree on SSL library.

Can somebody confirm that https://github.com/yuzu-emu/yuzu/pull/3675 does indeed sort this. My Linux machine is headless, so can't confirm myself.

It looks like it's fixed, yes. Setting BCAT Backend to Boxcat does not cause the crash when opening the Configuration window anymore.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

youwereeatenbyalid picture youwereeatenbyalid  Â·  4Comments

CptFoda-se picture CptFoda-se  Â·  3Comments

Ktuky picture Ktuky  Â·  4Comments

Rayz320 picture Rayz320  Â·  4Comments

spotanjo3 picture spotanjo3  Â·  3Comments