Simon McVittie

From the log in https://github.com/ValveSoftware/steam-for-linux/issues/10431#issuecomment-1918241124, we are likely to be using the container's root CA certificates (derived from Debian 11's `ca-certificates` package, and available in `/etc/ssl/`) rather than the host's...

@glabifrons, if you are comfortable with using unreleased software, one thing you could try is: * confirm that the bug is still reproducible on your system * rename `~/.steam/root/ubuntu12_64/steam-runtime-sniper/pressure-vessel` out...

If there is a way to do this, then it would involve including [Appstream metadata](https://www.freedesktop.org/wiki/Distributions/AppStream/) in the app, with one of the standard locations, named according to the app ID....

The problem here is that flatpak needs to run xdg-dbus-proxy in a new filesystem namespace, so that it will have `/.flatpak-info`, which portals and other services can look up in...

If you run an affected app with `flatpak run -vv`, what happens at the time that Flatpak is building up the command-line for `xdg-dbus-proxy`? Using `strace` might also be interesting....

I know more or less what bwrap is doing (it's very much mechanism rather than policy, and almost a CLI for making syscalls) so it's the strace on flatpak itself...

@ashleysommer: > I'm having this same problem, I use Keybase, that mounts a fuse filesystem in root fs at `/keybase` That's not quite the same problem: in the original report...

Generating pkg-config metadata would be a useful way to codify what is necessary to link to each of the API entry points provided by glslang. Sections of the API that...

The Fedora packaging at https://src.fedoraproject.org/rpms/glslang/tree/master seems to have patches for this, which have also been applied in Debian.

What desktop environment are you using (if any), and what value does it set `$XDG_CURRENT_DESKTOP` to? What handler(s) for `x-scheme-handler/https` exist on your system? What preferred handler(s) for `x-scheme-handler/https` are...