Simon McVittie

Or, trying to rephrase that in a way that is maybe more suitable for both layers and ICDs: It is safe for a consumer to load manifest files with a...

For some context that I should probably have mentioned first, I'm working on some code to pick up Vulkan ICDs from the host system outside a container, and make them...

> r-o map host /usr into flatpak and use libcapsule to load mesa libs into their own linker namespace (steam solution) In Steam's "pressure-vessel" container tool, we don't actually use...

> I'm aware that those libraries all need to match, but that doesn't make a glibc flatpak extension any harder, does it? It would include all the glibc libraries instead...

`flatpak-portal` has similar code but does not seem to have the same bug: it correctly uses `g_auto(GStrv) env = NULL` ensuring that the local copy of the environment gets freed....

Given the age and vagueness of this bug report (and the fact that the original reporter has disappeared from Github), if anyone can get an actually useful debug log or...

> I don't see how the original reporter disappearing is relevant, given a lot of people over the years have reported facing the same, even very recently. "App won't start"...

> User will save a file outside of allowed `xdg-documents`. File will disappear. It's bad. If this is the failure mode that you're interested in, then I think it would...

> flatpak should `persist=.` as a default. `com.valvesoftware.Steam` does this, and it has caused several weird issues in the past, so I don't think this would be a great default...

> or read-only mounting (like `bwrap --tmpfs /foo --dir /foo/bar --remount-ro /foo`). Read-only mounting is probably the better answer here because it gives a distinctive error code, `EROFS` For this...