Arch Linux User Repository

Changing package name to dangerzone-bin.

Extremely late comment but I rewrote the package and it works perfectly well on my machine, please let me know if it fails to work on yours

Thank you - from this comment on that given GH issue, I was able to get Dangerzone working with these commands:

$ sudo usermod --add-subgids 10000-75535 <your-linux-username>
$ sudo usermod --add-subuids 10000-75535 <your-linux-username>
$ podman system migrate

@taivlam https://github.com/containers/podman/issues/12715

No, Dangerzone has not been working for me, at least for a few months on Manjaro Unstable. (Sorry for the delay in response, as I didn't turn on notifications for comments.)

This is the error I encounter when I launch Dangerzone's GUI:

Traceback (most recent call last):
  File "/usr/lib/python3.13/site-packages/dangerzone/gui/main_window.py", line 411, in run
    installed = self.dangerzone.isolation_provider.install()
  File "/usr/lib/python3.13/site-packages/dangerzone/isolation_provider/container.py", line 194, in install
    if not Container.is_container_installed(raise_on_error=True):
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.13/site-packages/dangerzone/isolation_provider/container.py", line 245, in is_container_installed
    raise ImageNotPresentException(
        "Image is not listed after installation. Bailing out."
    )
dangerzone.isolation_provider.container.ImageNotPresentException: Image is not listed after installation. Bailing out.

(For the former, I'm not sure if this is an upstream issue.)

Also, this is what I see in stdout when I launch Dangerzone via a terminal emulator:

$ dangerzone
[DEBUG] Inferred system color scheme as OSColorMode.DARK
[DEBUG] Setting up Dangerzone updater
[DEBUG] Consulting updater settings before checking for updates
[DEBUG] Checking platform type
[DEBUG] Running on Linux, disabling updates
[DEBUG] Will not check for updates, based on updater settings
[INFO] Installing Dangerzone container image...
Getting image source signatures
Copying blob 7bb051c100d5 done   | 
Copying blob 4583886482d8 done   | 
Copying blob 3634f457d5c9 done   | 
Copying blob d580a9afc67b done   | 
Copying blob e6af67fe3d46 done   | 
Copying blob 3e01818d79cd done   | 
Copying blob b6d1d382257b done   | 
Copying blob 8efd04803bf5 done   | 
Error: payload does not match any of the supported image formats:
 * oci: open /var/tmp/podman3602617448/index.json: not a directory
 * oci-archive: loading index: open /var/tmp/container_images_oci1807094057/index.json: no such file or directory
 * docker-archive: writing blob: adding layer with blob "sha256:3e01818d79cd3467f1d60e54224f3f6ce5170eceb54e265d96bb82344b8c24e7"/""/"sha256:3e01818d79cd3467f1d60e54224f3f6ce5170eceb54e265d96bb82344b8c24e7": unpacking failed (error: exit status 1; output: potentially insufficient UIDs or GIDs available in user namespace (requested 0:42 for /etc/shadow): Check /etc/subuid and /etc/subgid if configured locally and run "podman system migrate": lchown /etc/shadow: invalid argument)
 * dir: open /var/tmp/podman3602617448/manifest.json: not a directory
[ERROR] Container installation problem

I just updated and tested, program seems to work so I am not able to reproduce.

After bumping the package version to 0.8.1 (and updating the sha256) I am also getting that StopIteration error. I think there's another dependency still, as the entrypoint doesn't seem to be getting set up correctly.

OK package is fixed now. Removed pyside2, which python3.12 does not support, and changed to pyside6. Thanks @archipalago_lost for the suggestion. Let me know if you have any other issues. I will try to maintain and keep up to date. Thanks!

I just updated the package and experienced the same error, I tried to fix it but got stuck.

First I detected all the unneeded packages by running pacman -Qqd | pacman -Rsu --print -

After I removed them all, I saw this error ModuleNotFoundError: No module named 'PySide6'

Then I installed pyside6, now I could open dangerzone but it shows this [ERROR] Docker is not running

So maybe we should change dependencies and rebuild?

Update:

I found the cohort: I disabled the user namespaces.

After rebuilding with pyside6 and enabling user namespaces I fixed the error.

Please change the dependency from pyside2 to pyside6, thanks.

OK thanks for the info. I would like to get confirmation if the program actually can start properly after installation. On my system, i'm getting a segfault, would like to know if it's just me or if it's a problem with everyone. thanks.

@username227 Thank you for the update. Please change the license as well.

New license: AGPL v3

Dangerzone was originally licensed under the MIT License until version 0.5.1. The PyMuPDF project though, which we are including in this release thanks to its significant improvements to Dangerzone, is licensed under AGPLv3. In order to comply with the license's terms, we have decided to switch the Dangerzone license to AGPLv3 as well. This change should affect only entities who are offering Dangerzone commercially, as part of a closed-source offering.