[моё] Belated answer to a meaningless question
By the way, about pasta.
It turns out that Python (on which Lutris is written) has a sneaky flag in its subprocess submodule (used for actually launching applications) without which the process will start... hehe... not completely.
That is, wholly, but not fully.
In other words, completely, but not finally.
And it's precisely Chromium (and everything on it, from Thunderbird to the very Look Outside) that dies because of this.
In the terminal we write, say,
which pipa
and we get an empty string in response (or not empty if you have such an executable pipa) + successful process termination.
But in Python 3
import subprocess
try:
subprocess.check_output(["which", "pipa"],text=True)
except:
print("pipa not found")
will always go to the except.
Because by default Python can interact with the terminal. But invoking the system which even via subprocess – by default, CANNOT.
As far as I understand, neither environment variables are picked up nor command aliases work.
Including which (in the wild /usr/bin/which ).
Fix: add shell=True at the end, so it becomes
subprocess.check_output(["which", "pipa"],text=True,shell=True)
Because otherwise we can't even
which which
call which which to see where to invoke it from.
Now we need to understand why it was done that way.
Security for security's sake?
But if pests have gotten into /usr/bin/, the perimeter is already breached.
I'm too lazy to dig into Lutris's source code to find where to insert this flag (and why errno2 doesn't reach the logs).
Not to mention the hassles with pull requests.
That's not even the point.
I now have my own burden – and I'm pushing it.
Ratio of positive and negative votes: 1/0