Arch Linux User Repository

@MrAureliusR

Hey. Thanks for pointing out this issue. Technically my fault it wasn't noticed sooner, but unfortunately not something I can fix, it appears. Minor correction, that is a text file, not an image. I spent about 2.5 hours looking into this and trying to fix this for you. I have failed, but at least I know why. https://github.com/firstlookmedia/dangerzone/issues/154 I made an issue with the developer to attempt to resolve this. It explains it further.

Essentially, that text file contains the ID of the container, and without it, dangerzone won't run. They want you to build this container yourself, at time of install. The mechanisms through with pkgbuilds are generally run, and honestly all ways I can run it, appear to cause this build to fail instantly. I have contacted the podman community discord trying to look into this, but wasn't able to find a quick fix.

I have suggested several in that issue, including turning maintainer status over to them.

I can absolutely fix the issue you mentioned, very easily. I just have to touch that file. But this will create a 404 issue when it tries to find the image, and, ultimately, changing where the error happens isn't a solution, so I won't push a change like that. Feel free to like/comment on that issue if you want more developer attention (maybe?), or post a solution if you find one that works with PKGBUILD. I will try to implement it.

Can you update the repo URL to https://github.com/freedomofpress/dangerzone to have better transparency? Thanks

When I try to make this package it gave me the output as follows:

[notice] A new release of pip available: 22.2.2 -> 22.3.1
[notice] To update, run: pip install --upgrade pip
Installing dependencies from lock file

Package operations: 26 installs, 2 updates, 0 removals

  • Installing pyparsing (3.0.9)
  • Installing exceptiongroup (1.0.0)
  • Installing iniconfig (1.1.1)
  • Updating packaging (22.0 -> 21.3)
  • Installing pluggy (1.0.0)
  • Installing mypy-extensions (0.4.3)
  • Installing py (1.11.0)
  • Installing pytest (7.2.0)
  • Installing shiboken2 (5.15.2.1)
  • Installing typing-extensions (4.4.0)
  • Installing click (8.1.3)
  • Installing coverage (6.5.0)
  • Installing execnet (1.9.0)
  • Installing mypy (0.982): Failed

  RuntimeError

  Hash for mypy (0.982) from archive mypy-0.982-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl not found in known hashes (was: sha256:37f98d89d45589358f145331129f3c4cab3cf9eafcd1e515ac7a1135c6dfcfd7)

  at dangerzone/lib/python3.10/site-packages/poetry/installation/executor.py:673 in _validate_archive_hash
      669│         archive_hash: str = "sha256:" + get_file_hash(archive)
      670│         known_hashes = {f["hash"] for f in package.files}
      671│ 
      672│         if archive_hash not in known_hashes:
    → 673│             raise RuntimeError(
      674│                 f"Hash for {package} from archive {archive.name} not found in"
      675│                 f" known hashes (was: {archive_hash})"
      676│             )
      677│ 

  • Installing pathspec (0.10.1)
  • Updating platformdirs (2.6.0 -> 2.5.2)
  • Installing pyside2 (5.15.2.1): Failed

  RuntimeError

  Hash for pyside2 (5.15.2.1) from archive PySide2-5.15.2.1-5.15.2-cp35.cp36.cp37.cp38.cp39.cp310-abi3-manylinux1_x86_64.whl not found in known hashes (was: sha256:0fe003f4aa12df9c085eb140868bb1a3bfee4190f5fae6d90294cb67360b38d4)

  at dangerzone/lib/python3.10/site-packages/poetry/installation/executor.py:673 in _validate_archive_hash
      669│         archive_hash: str = "sha256:" + get_file_hash(archive)
      670│         known_hashes = {f["hash"] for f in package.files}
      671│ 
      672│         if archive_hash not in known_hashes:
    → 673│             raise RuntimeError(
      674│                 f"Hash for {package} from archive {archive.name} not found in"
      675│                 f" known hashes (was: {archive_hash})"
      676│             )
      677│ 

  • Installing pytest-forked (1.4.0)

And then the makepkg failed, without knowing what happened because I have python-pip version 22.3.1 in my computer.

When I try to run dangerzone, it gives me this output:

>0 Terminal2 2022-1205-0023 jma@desktop:/home/jma/ dangerzone
bash: /usr/bin/dangerzone: /home/jma/.cache/yay/dangerzone/src/dangerzone-0.4.0/dangerzone/bin/python: bad interpreter: No such file or directory

>126 Terminal2 2022-1205-0023 jma@desktop:/home/jma/

In the beginning I have exit-code 0, afterwards it's exit-code 126

The output to whereis is:

>0 Terminal2 2022-1205-0032 jma@desktop:/home/jma/ whereis dangerzone
dangerzone: /usr/bin/dangerzone /usr/share/dangerzone

@MrAureliusR

Hey. Thanks for pointing out this issue. Technically my fault it wasn't noticed sooner, but unfortunately not something I can fix, it appears. Minor correction, that is a text file, not an image. I spent about 2.5 hours looking into this and trying to fix this for you. I have failed, but at least I know why. https://github.com/firstlookmedia/dangerzone/issues/154 I made an issue with the developer to attempt to resolve this. It explains it further.

Essentially, that text file contains the ID of the container, and without it, dangerzone won't run. They want you to build this container yourself, at time of install. The mechanisms through with pkgbuilds are generally run, and honestly all ways I can run it, appear to cause this build to fail instantly. I have contacted the podman community discord trying to look into this, but wasn't able to find a quick fix.

I have suggested several in that issue, including turning maintainer status over to them.

I can absolutely fix the issue you mentioned, very easily. I just have to touch that file. But this will create a 404 issue when it tries to find the image, and, ultimately, changing where the error happens isn't a solution, so I won't push a change like that. Feel free to like/comment on that issue if you want more developer attention (maybe?), or post a solution if you find one that works with PKGBUILD. I will try to implement it.

This builds but fails to run due to a missing image:

Settings file doesn't exist, starting with default
Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/dangerzone/gui/main_window.py", line 98, in run
    self.global_common.install_container()
  File "/usr/lib/python3.10/site-packages/dangerzone/global_common.py", line 426, in install_container
    if self.is_container_installed():
  File "/usr/lib/python3.10/site-packages/dangerzone/global_common.py", line 461, in is_container_installed
    with open(self.get_resource_path("image-id.txt")) as f:
FileNotFoundError: [Errno 2] No such file or directory: '/usr/share/dangerzone/image-id.txt'

Going to build directly from their github source for now.

Works or doesnt work? Previous version? Deb version? other alternatives to manage pdf in this way?

Released the podman version but I'll be honest I can't get podman to work in general. It works with sudo (Yes I read the wiki).
Sudo dangerzone wasn't working either.
Directions just said "Install podman and run dangerzone" but it's not that simple. Most of the changes made seem like user specific ones, so see https://wiki.archlinux.org/title/Podman

Yeah, docker containers for this? lolno. Dropping this.