@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.
Pinned Comments
username227 commented on 2024-06-09 14:17 (UTC)
Changing package name to dangerzone-bin.
Proudmuslim commented on 2023-09-29 15:42 (UTC)
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