Simon McVittie

@japtain-cack: > I believe this is because WSL2/Ubuntu You are not @mnyaa and you are not running Flatpak on Gentoo, so any errors that you are seeing probably do not...

I believe the Pipewire socket is always `$XDG_RUNTIME_DIR/pipewire-0` in practice, and apps can get access to that with `--filesystem=xdg-run/pipewire-0`. We only need a special `--socket` permission in cases where it's...

> Initially I had my HTTP_PROXY variable(s) uppercase It is intentional that general-purpose http libraries don't allow this. The CGI script interface and similar specifications put an attacker-supplied HTTP header...

Does this mean that WSL2's `/dev` doesn't have a `/dev/shm` subdirectory?

> Running it without all (not very useful for calls on Slack though), then there's a different issue [...] Failed to connect to session bus I'm going to ignore this...

Expanding on this a bit: WSL is not a typical Linux system. Some things that work on a typical Linux system will not work in WSL, and it's also possible...

> a symlink to /run/shm as is usual for Debian/Ubuntu That is not the usual arrangement for Debian/Ubuntu any more: `/dev/shm` is a real directory, with `/run/shm` a symlink to...

This is working as intended, unless you have evidence otherwise: the app's installation directory (the equivalent of `/usr` or `/usr/local` or `/opt`) will be in `/run/media/K0RR/watch&play/_GAMES/flatpak/`. `~/.var/app/${FLATPAK_ID}` is the app's...

If this is a problem with Mesa, libdrm or the app, then it will never be fixed *by a change in flatpak*, because flatpak is not responsible for the content...

> Tested on debian BookWorm, the problem no longer exists! That sounds like there was a bug in some printing-related component of Debian 9 (stretch), or possibly the proprietary driver...