search

ppy / osu

rhythm is just a *click* away!
https://osu.ppy.sh
MIT License
15.37k stars 2.29k forks source link

No usable version of libssl was found #7994

Open maciozo opened 4 years ago

maciozo commented 4 years ago

Describe the crash: Trying to run osu.x86_64.AppImage throws the following error and exits.

Screenshots or videos showing encountered issue: 

~/Downloads
❯ ./osu.x86_64.AppImage
No usable version of libssl was found
[1]    8655 abort      ./osu.x86_64.AppImage

~/Downloads
❯ sha256sum osu.x86_64.AppImage 
c731fe6c9e17da31bafcc0ef510ce739ea183a508443a95e04a3457da3b8a9c8  osu.x86_64.AppImage

osu!lazer version: 2020.225.0

Logs: please attach logs here, which are located at:

Computer Specifications: Void Linux (Kernel 5.5.4) Lenovo ThinkPad A485 w/ Ryzen 7 16 GB RAM

jai-x commented 4 years ago

Void Linux uses libressl instead of openssl as it's system TLS library. libressl is not official supported by the dotnet core runtime which osu!lazer uses.

You could use a workaround and try and symlink the libraries, but that may not work:

See https://github.com/dotnet/runtime/issues/24869

maciozo commented 4 years ago

Am I mistaken in my understanding of how AppImages are supposed to work? I thought that all the dependancies would be contained within the AppImage.

jai-x commented 4 years ago

The AppImage is very basic, as an MVP of getting Linux releases out for people to use.

Packaging system dependencies properly is most likely something that will be done in the future.

I think ffmpeg, openssl and maybe glibc (for the musl based distros) would have to be packaged for the AppImage to be fully self contained. At the moment, none of these are packaged yet.

maciozo commented 4 years ago

Symlinking libssl.so.1.0.0 to libssl.so.47.0.6 seems to work fine. I've logged in and can view multiplayer lobbies. Haven't actually tried playing anything yet though.

Single player and osu!direct work fine. I haven't tried multiplayer yet.

Dadoum commented 4 years ago

Should be fixed soon, got it working on my fork with auto updates

gustavoalpizar commented 4 years ago

Hi, @Dadoum just having this issue with Dotnet core latest version running on a mac.

The workarounds on the web are not working for me, just needed to do a rollback of the version that I have installed on my machine to .NET Core 3.1 SDK (v3.1.102) - macOS x64 Installer

Hope this can be fixed soon.

peppy commented 4 years ago

This issue is specific to linux. Are you trying to run an appimage on mac somehow?

aquaspy commented 4 years ago

@maciozo how can I symlink it in my void?

maciozo commented 4 years ago

@aquaspy ln -s /lib/libssl.so /lib/libssl.so.1.0.0 as root

aquaspy commented 4 years ago

@aquaspy ln -s /lib/libssl.so /lib/libssl.so.1.0.0 as root In user root or with root permission? I did with sudo but I still not able to open :\