Hello, I just switched to Manjaro and tried running some of gog games when I launch them from start menu all of them are not launching. But when I launch them from their directory, all of my games are showing "failed to execute child process (No such directory found)". Is there a way to solve it?
If the games do not launch, that means, most probably, that there are some dependencies missing.
1) Try to consult the games' system requirements on their respective pages; there is some information on which libraries should be present (preferably both 32 and 64 bit versions).
2) But given that the requirements are for Ubuntu only, it is entirely possible Manjaro lacks some of the Ubuntu's libs that are assumed by GOG to be present by default and were not mentioned in the requirements. In this case it may be necessary to manually determine the missing parts. Try consulting related games' subforum topics.
3a) Provided the above did not help, it is time to resort to "heavy artillery". :) You can go to the game's directory, find the executable and analyze its dependencies. Please note, that in most cases GOG "wraps" its games in redundant (most of the time) launch scripts ("*.BAT" analogues) and all automatically created desktop and menu icons point to the script, not the game executable directly and the "failed to execute child process" error message is actually triggered by the script which somehow failed to find the game executable. There should be a sub-directory called "game" in the installation directory, residing alongside the aforementioned "start.sh" script and "docs" and "support" sub-direcrories. It is this "game" subdirectory which is needed and it contains the game itself.
Inside, there are differences and the contents are dependent on the game in question. E.g. there should be "Some_Game.x86" and/or "Some_Game.x86_64" executables alongside "Some_Game_Data" directory in case of Unity3D engine; "Some_Game.sh" and "game", "lib" and "renpy" directories script in case of Ren'Py, or there can be something entirely different for custom engines.
3b) After locating the executable you can open its directory in a console (AKA "Scary Black Window") and analyze the executable by typing
$ ldd -r ./Some_Game_Executable
This should list the required libraries and their actual location in the system. The missing ones will be in cursive
and will lack the location. You can write down their names and use specialized Internet sites like pkgs.org
in order to find out how exactly the package containing the missing library is called in your Linux distribution. After that it is only a matter of installing the libs and trying again.
Hope that helps. :)