Posted July 20, 2020
It would appear, "libcurl3" was tossed away and GOG needs to update its system requirements.
But, I believe, this is a "red herring". Because I've seen some familiar issue down in your post.
Oh, and BTW, the "*.desktop" files are just like "lables" in Windows ("*.lnk"), only in Linux they are more useful, as Linux executables do not (and can not -- that is intentioal) have embedded icons in them, so these "*.desktop" files provide nicely looking link to place on a desktop (there is more to it, but that's besides the point).
But yet again, another false lead.
A well known issue OpenSSL version 1.0 was discontinued not that long ago and was thrown out from Ubuntu (from 19.10 onward). It was discarded in Fedora even earlier, that's why I've dealt with this issue a lot of times. For some strange reason games (or rather, game engines), even single-player "DRM-free" ones have the need of network cryprography. :(
But on to the point, two files are needed: "libssl.so.1.0.0" and "libcrypto.so.1.0.0" (32bit versions in our case, but I've encountered games requiring 64bit versions as well, so while we are at it, it is probably a good idea to grab both).
Unfortunately, as I said, OpenSSL 1.0 was tossed, so no, you can not install these libraries the normal way (via packet manager), and no, "libssl1.1" will not do.
Strange fact is that your supposed GOG version tries to search for the libraries in your Steam installation directory. It fails most probably due to "Steam Runtime" not been installed. :)
You can download these libraries manually (from "Ubuntu 18.04") and shove them to the game.
Here are the links:
http://archive.ubuntu.com/ubuntu/pool/main/o/openssl1.0/libssl1.0.0_1.0.2n-1ubuntu5.3_i386.deb
http://archive.ubuntu.com/ubuntu/pool/main/o/openssl1.0/libssl1.0.0_1.0.2n-1ubuntu5.3_amd64.deb
It would probably not be a good idea to install these packages system-wide. Just extract needed libraries and copy them into game "lib" directory (if there is one, otherwise you should create it) and ensure the game finds them (use LD_LIBRARY_PATH or LD_PRELOAD environment variables or some other, more convoluted way, like writing [url=https://en.wikipedia.org/wiki/Rpath_(linking)] RPATH[/url] into the game's executable).
But, I believe, this is a "red herring". Because I've seen some familiar issue down in your post.
Snuggles988: When i try and run the game through the terminal from the folder I get the following
"start.sh
bash: start.sh: command not found" from the games folder and thats what i get.
"ldd -r start.sh
not a dynamic executable"
"ldd -r gog_com-Monolith_1.desktop
not a dynamic executable"
"ldd -r start.sh
not a dynamic executable"
start.sh is not the game's executable. It is the very same GOG's wrapper I've mentioned in my previous post. Technically, it is a "Shell Script" -- text file containing instructions (setting variables, preloading libraries, executing "launchers" etc.). Sometimes GOG tries to be "clever" with it and likes to substitute system libraries with its own, bundled with a game, and said libraries may be incompatible with other (system, this time) libraries, thus ruining everything. That's why it is usually better to circumvent GOG's "start.sh" script and launch a game directly. "start.sh
bash: start.sh: command not found" from the games folder and thats what i get.
"ldd -r start.sh
not a dynamic executable"
"ldd -r gog_com-Monolith_1.desktop
not a dynamic executable"
"ldd -r start.sh
not a dynamic executable"
Oh, and BTW, the "*.desktop" files are just like "lables" in Windows ("*.lnk"), only in Linux they are more useful, as Linux executables do not (and can not -- that is intentioal) have embedded icons in them, so these "*.desktop" files provide nicely looking link to place on a desktop (there is more to it, but that's besides the point).
But yet again, another false lead.
Snuggles988: "./runner: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
"
"locate libcrypto.so.1.0.0
/home/NAME/.steam/debian-installation/steamapps/common/SteamLinuxRuntime/scout_0.20200505.0/files/lib/i386-lin ux-gnu/libcrypto.so.1.0.0
/home/NAME/.steam/debian-installation/steamapps/common/SteamLinuxRuntime/scout_0.20200505.0/files/lib/x86_64-l inux-gnu/libcrypto.so.1.0.0
/home/NAME/.steam/debian-installation/ubuntu12_32/steam-runtime/lib/i386-linux-gnu/libcrypto.so.1.0.0
/home/NAME/.steam/debian-installation/ubuntu12_32/steam-runtime/lib/x86_64-linux-gnu/libcrypto.so.1.0.0"
Now, that's the deal! "
"locate libcrypto.so.1.0.0
/home/NAME/.steam/debian-installation/steamapps/common/SteamLinuxRuntime/scout_0.20200505.0/files/lib/i386-lin ux-gnu/libcrypto.so.1.0.0
/home/NAME/.steam/debian-installation/steamapps/common/SteamLinuxRuntime/scout_0.20200505.0/files/lib/x86_64-l inux-gnu/libcrypto.so.1.0.0
/home/NAME/.steam/debian-installation/ubuntu12_32/steam-runtime/lib/i386-linux-gnu/libcrypto.so.1.0.0
/home/NAME/.steam/debian-installation/ubuntu12_32/steam-runtime/lib/x86_64-linux-gnu/libcrypto.so.1.0.0"
A well known issue OpenSSL version 1.0 was discontinued not that long ago and was thrown out from Ubuntu (from 19.10 onward). It was discarded in Fedora even earlier, that's why I've dealt with this issue a lot of times. For some strange reason games (or rather, game engines), even single-player "DRM-free" ones have the need of network cryprography. :(
But on to the point, two files are needed: "libssl.so.1.0.0" and "libcrypto.so.1.0.0" (32bit versions in our case, but I've encountered games requiring 64bit versions as well, so while we are at it, it is probably a good idea to grab both).
Unfortunately, as I said, OpenSSL 1.0 was tossed, so no, you can not install these libraries the normal way (via packet manager), and no, "libssl1.1" will not do.
Strange fact is that your supposed GOG version tries to search for the libraries in your Steam installation directory. It fails most probably due to "Steam Runtime" not been installed. :)
You can download these libraries manually (from "Ubuntu 18.04") and shove them to the game.
Here are the links:
http://archive.ubuntu.com/ubuntu/pool/main/o/openssl1.0/libssl1.0.0_1.0.2n-1ubuntu5.3_i386.deb
http://archive.ubuntu.com/ubuntu/pool/main/o/openssl1.0/libssl1.0.0_1.0.2n-1ubuntu5.3_amd64.deb
It would probably not be a good idea to install these packages system-wide. Just extract needed libraries and copy them into game "lib" directory (if there is one, otherwise you should create it) and ensure the game finds them (use LD_LIBRARY_PATH or LD_PRELOAD environment variables or some other, more convoluted way, like writing [url=https://en.wikipedia.org/wiki/Rpath_(linking)] RPATH[/url] into the game's executable).
Post edited July 20, 2020 by Alm888