Simon McVittie

> Setting the members of privsep_sockets[] to -1 ... is not (currently) something that `cleanup_fdp()` does, so this PR is wrong.

The solution I would suggest would be to link at least `libMangoHud_shim.so` (ideally all libraries) with `gnu_symbol_visibility: "hidden"`, and decorate each function that is intentionally being exported with (a macro...

> Without this addition, the Steam flatpak is unable to handle adding another filesystem You can give the unofficial Steam Flatpak app direct access to locations where you want to...

For the diagnostic tool, fixing `check-va-api` to use a supported surface format seems plausible as a correct fix, and https://github.com/ValveSoftware/steam-runtime/issues/752 is a good place to track that. However, for Steam's...

If you temporarily change the `ExecStart` to something like ``` ExecStart=/usr/bin/flatpak run --command=bash org.wiki.fed -c "echo this is stdout; echo this is stderr >&2; sleep infinity" ``` do the messages...

> Why does the process log to the terminal when ran manually, but journald is not able to pick this up? When it's run from a systemd unit, stdout and...

> How could I simulate and reproduce Flatpak's socket behaviour locally, outside of the Flatpak's sandbox? There is no special Flatpak socket behaviour: it is the systemd unit that sets...

If you read *all* of the messages from the Journal, *without* filtering to limit it to just this systemd unit, do this process's messages turn up there? (`this is stdout`...

> I don't know how you knew, but indeed the logging output for both cases of `ExecStart` show in `journalctl -xn --user -f` without supplying the `-u app-org.wiki.fed.service` flag. It...

> Would there be another way to tell Flatpak to report another `USER_UNIT`, even with the transient unit being created? No. Flatpak doesn't report it, systemd picks it up by...