Alexis Métaireau

> Thanks for debugging this! I'm assuming that the problem was that the VM configuration lima uses for `/proc/sys/kernel/unprivileged_userns_apparmor_policy` changed after the one I tested with (0.22.0). I haven't found...

From 0.10.0 onwards, we do only support the Podman container runtime.

Hi @LuciaSoft and thanks for opening the discussion here. We've recently started discussing this in https://github.com/freedomofpress/dangerzone/discussions/1142 If that's possible to you, could you add more context, so we can better...

The `Error: No such option: -B` is actually not the source of the error and just adds some confusion. It's tracked at https://github.com/freedomofpress/dangerzone/issues/873. It's a good reminder that we should...

> Alexis, can you reproduce it as well? I will have access to my macOS machine later today only, unfortunately. Using a nightly to ensure that the issue is gone...

Part of the reason is that pyinstaller (that we're using to package Dangerzone on macOS) is not configured properly, setting `sys.executable` to `dangerzone`, and `multiprocessing` is then passing options to...

@eloquence I added a comment here on purpose, because the issue is at least closely related to the error you're seeing. We don't know yet if this `no such option:...

Okay, I've been able to reproduce the error on macOS! The error happens after an upgrade to macOS 15.2, and happens only when running the OCR. This is why we...

After poking a bit more at this, we've been able to produce a minimal reproducible example, which shows the error we're facing: ```python import shlex import subprocess import sys import...

We got a response from upstream, and it seem that this is a CLI bug, which doesn't happen on versions prior to `v27.5.1`. Meaning we have a mitigation: ask our...