Perhaps a quick way to test this would be to use lgogdownloader's galaxy install method current broken version results in this:
lgogdownloader --galaxy-install 2110182857 --galaxy-platform linux
Galaxy API doesn't have Linux support
Trying to use installers as repository
Getting file list for the_bards_tale_iv_directors_cut/en3installer1
Failed to get XML data
Failed to get file list

Galaxy backend doesn't have Linux files.
Hi and thanks for pinging GOG about it :) I suspect they are flooded with stuff and have very few people to handle Linux issues.

Was anybody bored enough to check why the installer does crash? I guess it's in binary way same stuff as in any other recent linux release, i.e. if the executable is damaged, maybe it can be replaced or checked how the damage happened. Is it just cut out? Or somebody did by accident open it in some less bright text editor and damaged something vital in the binary part of the script? Or the installer itself is ok, and it does crash when it tries to parse the data from the file?

(I still didn't buy the game, nor am I *that* bored... I prefer to spend my spare time developing open source, sorry).

Galaxy doesn't have linux but if you notice what I posted if the installer hadn't been corrupted it would have downloaded the files just like galaxy feel free to try running it on a game with a working linux installer. I will point out it will install the game so check where the files are going.
Its handy for those games that don't get patches, saves a spot of downloading.

Problem with new version (archive):
####################
7z t the_bard_s_tale_iv_director_s_cut_4_20_1_32050_linux.zip

7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
p7zip Version 16.02 (locale=ru_RU.UTF-8,Utf16=on,HugeFiles=on,64 bits,4 CPUs AMD Phenom(tm) II X4 925 Processor (100F42),ASM)

Scanning the drive for archives: 1 file, 38199133688 bytes (36 GiB)

Testing archive: the_bard_s_tale_iv_director_s_cut_4_20_1_32050_linux.zip

ERRORS: Unexpected end of archive

--
Path = the_bard_s_tale_iv_director_s_cut_4_20_1_32050_linux.zip
Type = zip
ERRORS:
Unexpected end of archive
Physical Size = 41116683022

ERROR: Data Error : the_bard_s_tale_iv_director_s_cut_4_20_1_32050.sh

Sub items Errors: 1
Archives with Errors: 1
Open Errors: 1
Sub items Errors: 1
####################

sha256sum the_bard_s_tale_iv_director_s_cut_4_20_1_32050_linux.zip:
e0cb526df8412ffc1da7698627f3c5197bb5f7095e20c975c9d86e76ea135e5b

Yeah, the new installer weirdly comes as zip file. Unpacking it with unzip fails right away. Unpacking with 7z gives: The above though produces an .sh file, but it's also broken: Files:

Is this a running gag?

I mean... like saying "ok Linux build ready in few hours!" and then this...
It would have been better to test the Linux build carefully and waiting some days before we can finally install it without issues on our machine.

makes me kinda wonder what "Verifying archive integrity... All good." line in the gog installer actually does... :D

It seems to check the integrity of the installer of itself, but not of the data to install.

But then the shell script was already produced from damaged installer and the script is ok. And I have hard time to imagine the installer crashing just because of truncated data file, that would be really sloppy code of unpacker, so it looks more like some weird damage of data... then again GOG was using some patched version of some installer to also encrypt the compressed data with password IIRC, so maybe it is sloppy code and just truncated file.

Ah, I'm trying not even comment on this, I lost pretty much all hope for GOG since LinuxVanGogh left and with each their web update, their precision and skill was on my scale (I'm programming computers for ~30 years and I'm pedantic asshole requiring perfection ad absurdum, far beyond the sensible point where it is profitable) on "kid amateurs" all the time, but apparently they managed to go even lower, which was initially hard to believe... But here we are. But it's not like this situation is making me worried more, for me it all makes sense. I just wonder if they will be able to fix it within a week or two.

And I absolutely agree about that part of letting devs post tar.gz/deb/7z/sh files themselves. Literally can't be worse. Or maybe they should give devs some "SDK" pack so the devs will build the shell script with the GOG ads during unpacking...

Looks like the joke is on us!

Considering the type of errors, it's clear that they haven't done any testing at all. How hard is it to try running an installer and see of it runs? It's not as though it's an issue that only occurs occasionally or is difficult to spot. Neither of the two packages could possibly run on any system.

Hopefully GOG will actually test it, before releasing it third time ;)