It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
When running the start.sh I'm getting the following error:

./runner: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory

I can manually link libcrypto.so.1.0.0 to libcrypto.so.10 to get around this. I then receive a similar error for libssl.so.1.0.0, which I get around by manually linking to libssl.so.10.

After manually linking the two libraries I receive the following error:

Running The Red Strings Club
./runner: /lib/libcrypto.so.1.0.0: version `OPENSSL_1.0.0' not found (required by ./runner)
./runner: /lib/libssl.so.1.0.0: version `OPENSSL_1.0.0' not found (required by ./runner)

I'm not sure how to proceed.

I'm using Fedora 27, btw.
No posts in this topic were marked as the solution yet. If you can help, add your reply
Same thing on Mint 18.3. Quite the cock up on Devolver Digital's part
avatar
street-samurai: When running the start.sh I'm getting the following error:

./runner: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory

I can manually link libcrypto.so.1.0.0 to libcrypto.so.10 to get around this. I then receive a similar error for libssl.so.1.0.0, which I get around by manually linking to libssl.so.10.

After manually linking the two libraries I receive the following error:

Running The Red Strings Club
./runner: /lib/libcrypto.so.1.0.0: version `OPENSSL_1.0.0' not found (required by ./runner)
./runner: /lib/libssl.so.1.0.0: version `OPENSSL_1.0.0' not found (required by ./runner)

I'm not sure how to proceed.

I'm using Fedora 27, btw.
The game is 32-bit for some reason, so I'd start by removing those symlinks and then installing the 32-bit versions of the libraries. Doing so allowed me to start the game (openSUSE Tumbleweed).
avatar
quantamm: The game is 32-bit for some reason, so I'd start by removing those symlinks and then installing the 32-bit versions of the libraries. Doing so allowed me to start the game (openSUSE Tumbleweed).
who the hell is still gaming on a 32-bit computer?
Quick fix: install lib32-openssl or openssl:i386 (depend of your system).

Who's still gaming on a 32-bit computer? I dunno, at least, with this low bar to pass, you can have everyone playing your game. You'd rather have the other way? "You need 2 GTX Titan in SLI, an Intel Bi-Xeon, 32Go of ram and 1.5To of space to play". Fuck this shit. I'd rather get a small ass game with soul than the new fancy shit that will run only on a kidney-priced machine.
avatar
killiox: Who's still gaming on a 32-bit computer? I dunno, at least, with this low bar to pass, you can have everyone playing your game. You'd rather have the other way? "You need 2 GTX Titan in SLI, an Intel Bi-Xeon, 32Go of ram and 1.5To of space to play". Fuck this shit. I'd rather get a small ass game with soul than the new fancy shit that will run only on a kidney-priced machine.
I think you're thinking that 32-bit processors are more common than they are. At this point, the 32-bit x86 architecture is all but dead. The last 32-bit chip that I can think of was the Intel Atom N280 and that came out in February 2009. And considering that every Linux distribution is either 64-bit only, or at least defaults to 64-bit, means that the developers of this game created a bunch of unnecessary compatibility problems.
Since I've made this post, I've run into this problem multiple times. It seems to be an issue with GameMaker Studio, as all of the games that have had this issue were made in this engine.

Fedora doesn't provide any packages that have compatible libraries. The way I was able to get around this was to link the libssl and libcrypto libraries from my Steam install (~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/lib/i386-linux-gnu/libssl.so.1.0.0 and ~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/lib/i386-linux-gnu/libcrypto.so.1.0.0).
I'm on Arch so 1.0.2 isn't even the default openssl installed any more.

I just build the lib32-openssl100 from the AUR without installing and take the libs and put them in a folder "libs" in the install folder so :
libs
libcrypto.so.1.0.0 libssl.so.1.0.0

then add :

export LD_LIBRARY_PATH="${CURRENT_DIR}/libs:${LD_LIBRARY_PATH}"

to the start.sh. Saves installing the package.

If you look at the store page it mentions libcurl as being needed that doesn't appear to be the case but libcurl would pull in the openssl library.

As an aside I don't allow any of my games to connect to the internet so out of date libs or the like don't matter so much.
I just bought this game today and I ran into the same issue, thanks to cusit and street-samurai here's how I fixed it:

1) Go to the install directory and create a folder called "libs"
2) Copy the missing libs from steam to that "libs" folder:
- ~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/lib/i386-linux-gnu/libssl.so.1.0.0
- ~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/lib/i386-linux-gnu/libcrypto.so.1.0.0
3) Edit "start.sh" from the install directory, and add:

export LD_LIBRARY_PATH="${CURRENT_DIR}/libs:${LD_LIBRARY_PATH}"

AFTER the "Initialization" bloc.

Thanks again my fellow linux users !
I also couldnt launch it in my Debian 10 system with amd64 arch cpu.

i managed to make the game launch and play by following Novarno's instructions but with
a twist.

I didnt use any steam lib but found some old debian packages. with the lib missing
that i downloaded and extracted their content.

We download libssl1.0.0_1.0.1t-1+deb8u12_i386.deb from https://packages.debian.org/jessie/i386/libssl1.0.0/download
(there is a danger debian to stop host such an old version in the future ?)

$ cd ~/Downloads
$ ar x libssl1.0.0_1.0.1t-1+deb8u12_i386.deb
$ tar xvf data.tar.xz
$ cd /usr/lib/i386-linux-gnu
$ mkdir ~/GOG\ Games/The\ Red\ Strings\ Club/libs/
$ cp libssl.so.1.0.0 ~/GOG\ Games/The\ Red\ Strings\ Club/libs/
$ cp libcrypto.so.1.0.0 ~/GOG\ Games/The\ Red\ Strings\ Club/libs/
$ cd ~/GOG\ Games/The\ Red\ Strings\ Club
$ nano start.sh
and add:
export LD_LIBRARY_PATH="${CURRENT_DIR}/libs:${LD_LIBRARY_PATH}"
AFTER the "Initialization" bloc.

Thats worked for for me , i did it two times back to 3/2020 and now 5/2021
in my Debian 10 x64 system
Post edited May 03, 2021 by chomwitt
Linux version segfaults on launch at Debian 11.

i386 compoatibility is enabled, all necessary libraries are installed.

> uname -rvm
5.10.0-3-amd64 #1 SMP Debian 5.10.12-1 (2021-01-30) x86_64

> ldd --version
ldd (Debian GLIBC 2.31-9) 2.31

> glxinfo | grep OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce RTX 3070/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 460.39

> ./start.sh
Running The Red Strings Club

***************************************
* YoYo Games Linux Runner V1.3 *
***************************************
CommandLine: -game game.unx
ExeName= /home/yura/Games/GOG/The Red Strings Club/game/runner�)�
MemoryManager allocated: 17920

***************************************
* YoYo Games Runner v1.0(999)[r32908] *
***************************************
RunnerLoadGame: game.unx
RunnerLoadGame() - assets/game.unx
Checking if INIFile assets/options.ini Exists
assets/options.ini file contents: [Linux]
DisplayName="The Red Strings Club"
NewDebugger=0

INI DisplayName=The Red Strings Club
Reading File assets/game.unx
Loaded File assets/game.unx(95892518)
IFF wad found
Get Resolution
Get Header Information
InitGMLFunctions
HighScore..SavePrePend /home/yura/.config/TRSC2017/
Game..Math..Graphic..Action..File..Resource..Interaction..3D..Particle..Misc..DS..Sound..Physics..Gamepad..GAM EPAD: Initialising Ubuntu support
GAMEPAD: 4 axis values (last) at 0xf71ef640
GAMEPAD: Enumerating 3
GAMEPAD: device name Microsoft X-Box 360 pad
GAMEPAD: buttons - 11, axes - 8
GAMEPAD: 4 axis values (last) at 0xf71ef600
GAMEPAD: 4 axis values (last) at 0xf71ef5e0
GAMEPAD: 4 axis values (last) at 0xf71ef5c0
Buffers..Networking..Shaders..InitPushFunctions...YoYo..Fini
Code_Load()
VARI_Load()
got 38 global variables
got 844 instance variables
got 26 local variables
ID_STRG
Create Window
Display Size(Pixels): 1920,1080
GameDisplayName=The Red Strings Club
Win #1
XF86VidModeExtension-Version 2.2
Only Singlebuffered Visual!
glX-Version 1.4
./start.sh: string 16: 17065 Segmentation fault ./"runner"
Post edited February 06, 2021 by wild_wolfman
As already said before by others: this game should have come out as 64 bit in 2018!
I can start it without error, though, but not for long before 1st error message appears:
* https://www.gog.com/forum/the_red_strings_club/broken_game_no_devs_support
Maybe this is normal for Windows - but not for GNU/Linux.
This game could not pass any QA - not even in 2018.

And even if 32 bit is no sign of trash (I own 58 of these 32 bit games - most to see
if I can get them to run) - but GMS with 32 bit after 2015 means, that devs don't care
about quality of life.
Changing game engine after 3 years when this is a game changer is not to much to ask!
So it is a shame for both: developer and publisher.
I managed to run the game again in a debian distro ( Devuan).
This time doing the libssl fix was more difficult since debian dropped it!
but i found it in Ubuntu!

https://packages.ubuntu.com/bionic/i386/libssl1.0.0/download

Also regarding wild_wolfman errors:
Win #1
XF86VidModeExtension-Version 2.2
Only Singlebuffered Visual!
glX-Version 1.4
./start.sh: string 16: 17065 Segmentation fault ./"runner"

in my run it says:
XF86VidModeExtension-Version 2.2
Got Doublebuffered Visual!
glX-Version 1.4
Icon: w=64 h=64
sw=1920 wh=1200
WindowCentre: 480,330
Depth 24
Congrats, you have Direct Rendering!
Post edited September 09, 2021 by chomwitt
avatar
Novarno: 1) Go to the install directory and create a folder called "libs"
2) Copy the missing libs from steam to that "libs" folder:
- ~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/lib/i386-linux-gnu/libssl.so.1.0.0
- ~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/lib/i386-linux-gnu/libcrypto.so.1.0.0
3) Edit "start.sh" from the install directory, and add:

export LD_LIBRARY_PATH="${CURRENT_DIR}/libs:${LD_LIBRARY_PATH}"

AFTER the "Initialization" bloc.
This method is still viable and probably easiest to obtain files if you have Steam installed.
Post edited December 17, 2022 by ssling