freedomofpress / dangerzone

Take potentially dangerous PDFs, office documents, or images and convert them to safe PDFs
https://dangerzone.rocks/
GNU Affero General Public License v3.0
3.36k stars 153 forks source link

Dangerzone not opening on macOS after installation. #783

Closed tenzyns closed 1 month ago

tenzyns commented 2 months ago

I had docker desktop already installed when I installed Dangerzone. But It doesn't open ever after a system reboot. I'm on mac Monterery verstion 12.7.4

apyrgio commented 2 months ago

Hi! Really sorry for the late reply, but we're wrapping up things for 0.6.1, and it's a bit hectic. I'll need you to clarify a bit the "doesn't open" situation, if you have some time.

tenzyns commented 2 months ago

Hi, thanks for getting back. I have Dangerzone version 0.6.0-i686. I didn't face any issue during the installation. I got this message after the command suggested.

[2039] Error loading Python lib '/Applications/Dangerzone.app/Contents/Frameworks/libpython3.11.dylib': dlopen: dlopen(/Applications/Dangerzone.app/Contents/Frameworks/libpython3.11.dylib, 0x000A): Symbol not found: (_mkfifoat)
  Referenced from: '/Applications/Dangerzone.app/Contents/Frameworks/libpython3.11.dylib'
  Expected in: '/usr/lib/libSystem.B.dylib' 

my python version is 3.10.4

apyrgio commented 2 months ago

Perfect, that's one of the issues we'll be tackling in the upcoming hotfix release: https://github.com/freedomofpress/dangerzone/issues/471

We'll build the macOS .dmg with a different Python version, and our understanding is that this should fix this issue. The release will be out in 1-2 weeks I believe. Once it's out, I'll make sure to circle back here and ask you to test the new installer.

In the meantime, I wish I could give a workaround, but I'm not aware of one :-/

apyrgio commented 1 month ago

Dangerzone 0.6.1 is out :partying_face: . I would appreciate it if you could check that the new build solves your issue.

apyrgio commented 1 month ago

Another user has reported that the original issue ("Symbol not found") has been resolved. I'm closing this issue, but if you still encounter this problem, we can reopen it.