package spawning the process

[saidbakr]

Whoa, there! Thanks for contributing by reporting issues, but before you do, check that you can answer all the following questions with a firm Yes:

• Are you sure this is a problem here and not in the server? NO
• Have I checked the existing open and closed issues? Yes
• If I've just installed or updated...
  • ... have I checked the CHANGELOG and the README?
  • ... have I tried removing and reinstalling the package and then restarting Atom to ensure Atom didn't break it?

On Ubuntu Linux that runs PHP from ppa:ondrej, The test settings always tells:

'/usr/bin/php' could not be spawned. Is it installed and on your path? If so please open an issue on the package spawning the process.

I have tried to change the binary path to /usr/bin/php7.2 without success. I don't know if the application has no execute permissions or not

Notice: The Atom that I have is a flatpak package!

[Gert-dev]

I've yet to get more familiar with Flatpak, but I think this depends on how (the) Flatpak is configured. IIUC, by default sandboxed applications do not have access to any host files in locations such as /usr/bin unless this was explicitly configured in the configuration or you overrode it.

If this is the case, you can try using an application such as Flatseal to "share" /usr/bin/php7.2 with the flatpak-ed Atom - or override the permissions via the command line, which is what Flatseal indirectly does, I think.

[saidbakr]

It looks like a structural limitation, simply flatpaks are sandboxes, could not be solved in Flatpak or at least it is very hard to solve it. The Flatseal itself is limited in applying permissions because it installed as flatpak package. So, in such type of applications that need to access another system applications or paths, flatpaks are not a good option. I just downloaded the debian package of atom and every thing worked fine!