Alex Pyrgiotis
Alex Pyrgiotis
Resolved as part of #1225, which will be soon pushed to `main`.
Hm, given that many folks have started reporting the same error recently (see also #919), I start to believe there's a new Docker Desktop release that somehow breaks Dangerzone. To...
Yeap, you have the latest Docker Desktop release alright. I have managed to reproduce this as well, and I have a workaround. For those who are affected, please take a...
Thanks for the report! Let's dig deeper. Could you run the command you see in the logs, and some variations of it, and paste here (or in https://gist.github.com) the output...
Good question: The logs are taken from within the Dangerzone container, so they should not contain any information about your host. In practice though, there are stuff that may leak...
> My guess without looking at how this works: Probably the point is that the issues don't look cluttered with long log excerpts and remain readable. Oh right, it's a...
Ok, that's the default configuration I believe, so we're good. I'll dig deeper and let you know. Thanks for the info!
Yeap, it's just a different configuration. Yours is the pristine one :-)
I managed to install Fedora 40 in a VM, and reproduced the issue you're seeing @sudwhiwdh. The root cause of this error is that Dangerzone 0.7.0 does not work with...
Hey @sudwhiwdh. I'm happy to report that we have a fix out for Fedora systems. For an explanation about the fix and our solution, you can check out https://github.com/freedomofpress/dangerzone/issues/880. tl;dr:...