Package Details: dangerzone-bin 0.10.0-2

Git Clone URL: https://aur.archlinux.org/dangerzone-bin.git (read-only, click to copy)
Package Base: dangerzone-bin
Description: Take potentially dangerous PDFs, office documents, or images and convert them to a safe PDF
Upstream URL: https://github.com/freedomofpress/dangerzone
Licenses: AGPL-3.0
Submitter: username227
Maintainer: username227
Last Packager: username227
Votes: 13
Popularity: 0.000244
First Submitted: 2024-06-09 13:17 (UTC)
Last Updated: 2026-01-11 20:38 (UTC)

Latest Comments

1 2 3 4 Next › Last »

lucaswerkmeister commented on 2025-08-29 15:47 (UTC)

I’m afraid now I get an error when building the package :(

==> Making package: dangerzone-bin 0.9.1-2 (Fr 29 Aug 2025 17:33:50 CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found dangerzone-0.9.1.deb
==> Validating source files with sha256sums...
    dangerzone-0.9.1.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!

I assume it’s because makepkg is reusing the DEB I had previously downloaded (for 0.9.1-1), but it doesn’t match the new sha256sum. (I’m using aurman but I assume this would affect any AUR helper.) I’m not sure what you could’ve done to avoid that, to be honest… give the file a new name like ${_pkgname}-${pkgver}-${pkgrel}.deb::? or maybe just not bump the pkgrel, so that only people newly building the package would’ve been affected?

username227 commented on 2025-08-27 21:17 (UTC)

Strange but confirmed. I just corrected it. sorry.

ncoder-2 commented on 2025-08-27 20:21 (UTC)

The sha256sum fails on the upstream .deb package. Any chance the PKGBUILD can be updated?

taivlam commented on 2025-02-13 15:40 (UTC) (edited on 2025-02-13 15:40 (UTC) by taivlam)

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

archipelago_lost commented on 2025-01-12 06:23 (UTC)

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

taivlam commented on 2024-12-31 11:42 (UTC)

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

username227 commented on 2024-12-24 19:10 (UTC)

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

gdorn commented on 2024-12-24 18:56 (UTC)

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.

1 2 3 4 Next › Last »