It looks like the launcher script named `games/Subliminal` tries to run the binary named `Superliminal.x86_64` while the binary shipped with GOG version is named `SuperliminalGOG.x86_64`.

The workaround is to open this launcher by your favorite text editor and replace:

`Superliminal.x86_64` string with `SuperliminalGOG.x86_64`

`Superliminal_Data` string with `SuperliminalGOG_Data`

Thanks for the diagnosis. I don't see any 'Superliminal.x86_64' or 'SuperliminalGOG_Data' string in "start.sh", but removing the 'GOG' from the file names works for me.

This problem was introduced with 1.11 (43363) of 14. Dec. 2020 - the former 1.06 (42669) did work.

The start.sh script in the install directory only invokes game/Superliminal as second script which really starts Superliminal.
Thus the two changes:
1) Superliminal.x86_64 -> SuperliminalGOG.x86_64
2) Superliminal_Data -> SuperliminalGOG_Data
are to be applied to game/Superliminal (when you are in the installation directory incl. start.sh).

But removing string GOG from the name of script and binary in game sub-directory will do the job, too.

But it is interesting that it is still not fixed ... and I am late with my updates ... ;)
(fixed it on my own and just wanted to give a hint here - but of cause two solutions are already given here ...).
So I will wake up GOG support (or who may be responsible) maybe next week ... such problems should never reach Download area!