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

×
Greetings
I have installed Baldur's gate EE and Baldur's Gate 2 : EE in my linux system. Installation was successful but when i press
to start, nothing happens.
I tried few solution I found in GOG forums.
1. I installed the lib was missing (libjson.so.0 ) and write :
$ cd /usr/lib32
$ sudo ln -s libjson-c.so libjson.so.0
Still don't start. I have installed the lib32 as well needed. So something I miss ?
I run the newest version of Manjaro
Thanks
No posts in this topic were marked as the solution yet. If you can help, add your reply
No one can help ?
avatar
darias: No one can help ?
If nobody does here, be sure to post in the subforum for BG, too.

Have you tried PlayOnLinux?

I found someone with your problem and they posted a solution:

I've got mine working now. What I eventually did was the following: 1. Uninstall the game and remove the libraries (just to clean things up). 2. Download the play.it installer script. 3. Place the play.it installer script, the games install file and the libssl file in the same folder. 4. Run the play.it installer script. When this happens it will build deb files that can be used to install the game using apt. Once this is done, it will give the commands required to run the install.

Reading full source will help, too:
https://www.reddit.com/r/baldursgate/comments/7wcrlt/need_help_running_baldurs_gate_enhanced_edition/
Post edited March 15, 2020 by Tallima
avatar
darias: No one can help ?
Contact GOG Support.
Post edited March 15, 2020 by PainOfSalvation
I'd also recommend to scan the NWN EE forums on Steam, even if you don't like Steam; the forums there are much more active than here and the issue with the EE not starting after the last update comes up quite often, so maybe you'd be able to find a solution there.
Post edited March 15, 2020 by Leroux
avatar
darias: No one can help ?
Can you launch the game from the terminal and post the output? Usually this is done by executing start.sh in the game directory.
avatar
darias: No one can help ?
avatar
igrok: Can you launch the game from the terminal and post the output? Usually this is done by executing start.sh in the game directory.
Hi ..sorry due internet issues I had, wasn't able to come online these days.
I installed 4 games actually, BG: EE 1&2 , Planescape :Torment EE and Pilars of eternity with all DLCs
The only game work well is Pillars on Linux. Anything esle has the same issue. They don't start .
Here what Konsole gives when i try to run from CLI:
Running Baldur's Gate Enhanced Edition
./BaldursGate64: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory
avatar
darias: No one can help ?
avatar
Tallima: If nobody does here, be sure to post in the subforum for BG, too.

Have you tried PlayOnLinux?

I found someone with your problem and they posted a solution:

I've got mine working now. What I eventually did was the following: 1. Uninstall the game and remove the libraries (just to clean things up). 2. Download the play.it installer script. 3. Place the play.it installer script, the games install file and the libssl file in the same folder. 4. Run the play.it installer script. When this happens it will build deb files that can be used to install the game using apt. Once this is done, it will give the commands required to run the install.

Reading full source will help, too:
https://www.reddit.com/r/baldursgate/comments/7wcrlt/need_help_running_baldurs_gate_enhanced_edition/
Will try this solution , see if will work. Thanks
Post edited March 20, 2020 by darias
avatar
darias: (…)
./play.it might be the kind of tool you are looking for, as it makes the installation of these games easier by automatically handling their specificities, including their dependency on libssl.so.1.0.0 (and libjson.so.0 for the older versions).

You can read more about it in the games specific sub-forums:
[./play.it] Install the Baldur's Gate games on Linux
[./play.it] Install Planescape: Torment on Linux

---

By the way, this is the same software described in the reddit thread Tallima linked to.
Post edited March 20, 2020 by vv221
avatar
darias: Running Baldur's Gate Enhanced Edition
./BaldursGate64: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory
Ah, so you are missing this particular version of libssl library which is part of openssl. You should check whether openssl is installed in your system. One way to do it is to run locate libssl.so which will show you all installed versions. You can also check which version is installed using the package manager of Manjaro. Probably the version you have is too new. One crude solution is to get libssl.so.1.0.0 elsewhere and copy it to /usr/local/lib64 (if this is the location which Manjaro uses for local system-wide libraries). For example, non EE version of Baldur's Gate from GOG comes with this file already included.

You can also run ldd BaldursGate64 in the terminal to check whether you are missing any other library dependancies.

Also, since your system is 64-bit, you don't need any 32-bit libraries to run this game.
Post edited March 20, 2020 by igrok
The problem is Beamdog updated BG:EE to version 2.6.6 but kept its dependencies as in versions 2.5.x. However in the meantime most GNU/Linux distributions upgraded said dependencies. So BG:EE 2.6.6 won't play in modern distributions because it expects openssl-1.0.x installed on your system (old library), while most distributions now have openssl-1.1.1.

The solution is simple, provided your distribution keeps older libs in their repositories.
(1) Find a file named openssl-1.0.x. in your distribution repositories. It is a compressed library, and the compression method depends on the distribution. Extract the files libssl.so.1.0.0 and libcrypto.so.1.0.0 to a new folder, say "old_libs_needed". Alternatively, if you have access to a computer running an older version of your distribution, locate those two files in /usr/lib64 (or usr/lib, depends on the distribution), and just copy them to your new folder.
(2) Move the folder "old_libs_needed" in your main BG:EE directory, where "start.sh" exists. This is a simple shell script that launches the game, and you have to modify it a little. Edit start.sh and add one line, so that it looks like that:

...
# Initialization
CURRENT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$CURRENT_DIR/old_libs_needed
cd "${CURRENT_DIR}"
....

(bold line is what you add in start.sh). Save and exit. The game should now run as usual.

For example if you are running Slackware 15.0 the old openssl you need can be found in Slackware 14.2 repositories (e.g., here), and it can be decompressed with the xz utility.
The same problem exists in BG2:EE and Icewind Dale:EE. It can be solved the exact same way. I don't have the other games mentioned above but if I were to bet, I'd say the solution should work there as well.

Now, I have nothing against Beamdog. In fact I believe the Enhanced Editions for the old Infinity games they released are great, and the best way to play those games nowadays. I also realize they can't prevent all kinds of problems caused by different versions of shared libraries. However in this case they could just include the old libraries needed in the game files.
Post edited September 07, 2022 by Archimidis
Funny, I didn't even realize there were separate Linux versions of these games on GOG...

Namely, I have earlier installed the GOG Windows version of Planescape Torment EE on Linux (using WINE, not sure if I used Lutris as well), and been happily playing that.

So I wonder, what advantage would it even give me to try to run the Linux version of PT: EE instead, when the Windows version works just fine in Linux for me?
Post edited September 07, 2022 by timppu
avatar
timppu: So I wonder, what advantage would it even give me to try to run the Linux version of PT: EE instead, when the Windows version works just fine in Linux for me?
Better performance and increased stability. While new versions of Wine may introduce bugs, a Linux native version of a game only depends on the underlying OS.
Post edited September 07, 2022 by WinterSnowfall
avatar
WinterSnowfall: Better performance and increased stability. While new versions of Wine may introduce bugs, a Linux native version of a game only depends on the underlying OS.
Wine may introduce bugs but updating OS not? This whole topic is about how updated libraries broke game compatibility on modern systems.

For performance you would need actual data from tests. There are cases where Windows game game in Wine/Proton performs better than native port, usually there is no difference especially with not demanding games like Baldur or Torment.
avatar
ssling: This whole topic is about how updated libraries broke game compatibility on modern systems.
libSSL 1.0.0 has been deprecated for a very long time already. As in "almost ten years" kind of long.
It was already deprecated at the time of the initial game release, in 2012.

The mistake here is with no doubt the fault of the game developers, not with the maintainers of OpenSSL libraries who dropped support for a long dead unsupported release.
Post edited September 08, 2022 by vv221
avatar
ssling: This whole topic is about how updated libraries broke game compatibility on modern systems.
avatar
vv221: libSSL 1.0.0 has been deprecated for a very long time already. As in "almost ten years" kind of long.
It was already deprecated at the time of the initial game release, in 2012.

The mistake here is with no doubt the fault of the game developers, not with the maintainers of OpenSSL libraries who dropped support for a long dead unsupported release.
If only it would be isolated case but it isn't. Cossacks 3 on Steam is unplayable due to version changes in Steam runtime. Loop Hero on GOG is another (or at least was few months ago when I played it).
Point being it's happening and will happen. We can't realistically expect lifetime support from devs and update everytime something becomes deprecated.