Simon McVittie

> Does running `flatpak run -vv ...` shed any more light on the situation? You didn't answer this. What messages do you get when you run in the mode that...

The problem here appears to be: * the Flatpak app manifest is configured to give the app access to Wayland if available, or X11 if Wayland is not available *...

> Unfortunately, installing Flatpak 1.10.x from buster-backports does not work using this guide (due to broken dependencies) What you need is the same instructions that are described there for `bullseye-backports`,...

Running this app with `flatpak run --socket=wayland --env=QT_DEBUG_PLUGINS=1 com.valvesoftware.SteamLink` might help to figure out why it isn't using the Wayland socket?

Hello, I am a Flatpak contributor. I would **not** recommend setting the setuid bit on `/usr/bin/bwrap` unless your Linux distribution requires it for basic functionality of Flatpak. It's needed on...

> XIVLauncher _is_ a flatpak app, unless I'm misunderstanding what you're saying. Sure, but the FAQ recommends Steam launch options for a `flatpak run` command that include `--parent-pid=1`, and process...

> we need to activate FFXIV in steam What does this mean, precisely? There might be some other way to achieve what you want. Does XIVLauncher do any launching of...

> XIVLauncher needs to initialize Steam API for authentication ticket and Steam Overlay purposes. What does this mean in terms of concrete API calls, or sockets, or pipes, or shared...

As I said, using `--parent-expose-pids --parent-share-pids --parent-pid=1` is not how those options were ever intended to be used: the only way they were ever intended to be used was for...

I can certainly see the argument for making this discovery be something that happens "above" Vulkan/EGL/OpenXR/etc., so that new dispatchers that are "the same shape" as Vulkan can take part...