deeplow

I have some updates here. ## (1) It affects also Fedora 38 (and the Qubes versions) ## (2) Shebang WARNING is unrelated I think the shebang warning line is unrelated....

> Turns out that these two base images do differ from each other, albeit in small ways. Still, using the (seemingly working) Fedora image from registry.fedoraproject.org/fedora does not fix this...

> - [ ] build the PDF as pages are created (we currently first convert everything and only then do the rest) I added one more topic to the list.

While looking into [seccomp](https://github.com/freedomofpress/dangerzone/issues/225) policies generation (I can't find the specific reference) I came across an interesting approach: execute over a test set and find all the binaries called. Then...

I was just bitten by their "[brownout periods](https://discuss.circleci.com/t/linux-image-deprecations-and-eol-for-2024/50177)". But I don't think it's worth tacking this issue since we should migrate to GitHub actions this reaches EOL.

Thanks for reporting this. Just to be clear, you're trying to run Dangerzone from the source code, correct? (I see some [DEBUG] messages that seem to indicate that). If that's...

OK. That's a bit more concerning. And thanks for reporting. I'll look into it.

> > OTOH podman run --network none -u dangerzone doesn't mean that a dangerzone user should exist? > > In the package's postint file there's no such user created! >...

Thanks for pasting that in (RIP pamela :cry: ). Unfortunately, it appears that no warning appeared there before the issue, so we'll have to dig deeper in an fully ubuntu...

Thanks for checking. Another dead-end. It's not a space issue either.