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

×
"Linux" returned 4 posts
Clear search criteria
I'm guessing you're having trouble because you're on 64 bit linux b/c >currentyear, but beamdog and other developers insist on programming for 32 bit linux even in this The Year of Our Lord Two Thousand Seventeen.

I was able to play after running the following command in terminal:
sudo apt-get install libjson0:i386

If that doesn't work you can access any error messages being thrown by running the executable script from a terminal line, instead of clicking the icon it installs on your desktop. Right click the icon, go to properties, and look at the "Command:" field to see where the executable script is on your machine.
avatar
grabsener: my game didnt start,which libs do i need? xubuntu 16.04.2 64bit.

dear Beamdog/GoG: why no snap or flatpak packages? would be so much more convienient cause you could add all needed libs to the game itself ,make it way more easy for da tux people!

thanks!
Hi grabsener,

The game requires 32 bit compatibility libraries - we will put that information on the product page as soon as possible. If you're on Ubuntu (or a derivative), you can install those packages using the following command:

sudo apt-get install libc6:i386 libasound2:i386 libasound2-data:i386 libasound2-plugins:i386 libjson-c2:i386 libopenal1:i386 libstdc++6:i386 libssl1.0.0:i386 libexpat1:i386 libx11-6:i386 libxau6:i386 libxcb1:i386 libxcursor1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxinerama1:i386 libxrandr2:i386 libxrender1:i386 libjson0:i386

As for your question regarding Snap and Flatpak: for now, we don't see many advantages of using these packaging formats and we're going to stick with installers on Linux.
avatar
linuxvangog: The game requires 32 bit compatibility libraries
linuxvangog, I hope this packaging can be improved in future GOG releases.

In several previous GOG releases (e.g. Icewind Dale: Enhanced Edition), you bundled too many libraries with the game... including libstdc++ and libxcb-dri3 (which break 3D rendering on systems with Mesa-based graphics drivers if Mesa is compiled against a different version of them), and things like libX11 (which is nonsensical because every desktop Linux system already has it).

But now, with Planescape: Torment: Enhanced Edition you've erred too far in the opposite direction, by bundling no libraries - not even things like libjson or libssl of which many Linux systems don't have the required version installed by default, and which you could have bundled without causing problems.

The optimal solution lies in the middle: Don't bundle libraries for which bundling causes problems or which are already installed on pretty much every Linux, but do bundle the remaining ones.

---

Also, please insist that game developers include both 32bit and 64bit Linux builds of each game's executable, and make the ./start.sh script choose the correct one. Shipping only 32bit builds in 2017 (when virtually all Linux gaming rigs are 64bit) is kinda embarrassing, and exacerbates the library dependency problems described above because it makes it less likely that a given library is already installed on a typical system, and also makes it more difficult for users to identify and install the correct package to provide the library.
Post edited May 13, 2017 by archy2
avatar
linuxvangog: The game requires 32 bit compatibility libraries
avatar
archy2: linuxvangog, I hope this packaging can be improved in future GOG releases.

In several previous GOG releases (e.g. Icewind Dale: Enhanced Edition), you bundled too many libraries with the game... including libstdc++ and libxcb-dri3 (which break 3D rendering on systems with Mesa-based graphics drivers if Mesa is compiled against a different version of them), and things like libX11 (which is nonsensical because every desktop Linux system already has it).

But now, with Planescape: Torment: Enhanced Edition you've erred too far in the opposite direction, by bundling no libraries - not even things like libjson or libssl of which many Linux systems don't have the required version installed by default, and which you could have bundled without causing problems.

The optimal solution lies in the middle: Don't bundle libraries for which bundling causes problems or which are already installed on pretty much every Linux, but do bundle the remaining ones.

---

Also, please insist that game developers include both 32bit and 64bit Linux builds of each game's executable, and make the ./start.sh script choose the correct one. Shipping only 32bit builds in 2017 (when virtually all Linux gaming rigs are 64bit) is kinda embarrassing, and exacerbates the library dependency problems described above because it makes it less likely that a given library is already installed on a typical system, and also makes it more difficult for users to identify and install the correct package to provide the library.
Hey archy2,

Thank you for your input. We realized that bundling libraries with Linux games by us was a step in the wrong direction, as it brings more problems than profit. If the game has an active developer, we always let them know that the game should ship a 64 bit binary and all of the dependencies needed to make the game run immediately after the installation.

However, if the developer does not do that, it is better to let the end-user fix dependencies on their side, to avoid library conflicts - that's why we always inform about the game dependencies on the product store page.

We are investigating other solutions for this problem, but for now we decided, that the choice explained above is the best option.