I'm using the Zotero Integration for Obsidian, which relies on pdfannots2json when pulling in citations from Zotero. On a Mac M2 machine, I consistently run into the error I copied below.
but to no avail. Also, the exact same setup works from a windows machine, so I was wondering if this might have something to do with the M2 chipset not being supported as of yet? If so, do you plan to add support for it anytime soon?
Thanks in advance.
Best,
David
Error processing PDF: Command failed with
EACCES: /Users/david/pCloud Drive/Obsidian/pdfannots2json
/Users/david/Zotero/storage/PSWM8L7T/Kot elnikov et al. - Accurate ligand-protein docking in CASP15 using th.pdf -n image -d
120 -f jpg-o /Users/david/pCloud Drive/Obsidian/Research/Literature
Notes/kotelnikov -q 90 spawn /Users/david/pCloud
Drive/Obsidian/pdfannots2json EACCES
I get a similar error when I try to re-load the executable from a different path in Obsidian. (PDF Utility Path Override)
Error checking PDF utility version: Command
failed with EACCES:
/Users/david/Zotero/pdfannots2json -v
spawn /Users/david/Zotero/pdfannots2json
EACCES
Interestingly, when I delete the custom path and it tries to fall back to the default location, it quotes "pdfannots2json-darwin-arm64", so it might have fetched a version for the wrong chipset (in lack of M2)?
Error checking PDF utility version: Command failed with EACCES: /Users/david/pCloud Drive/Obsidian/Research/.obsidian/plugins/ob sidian-zotero-desktop-
connector/pdfannots2json-darwin-arm64 -v spawn /Users/david/pCloud
Drive/Obsidian/Research/.obsidian/plugins/ob sidian-zotero-desktop-
connector/pdfannots2json-darwin-arm64
EACCES
Hi,
I'm using the Zotero Integration for Obsidian, which relies on pdfannots2json when pulling in citations from Zotero. On a Mac M2 machine, I consistently run into the error I copied below.
I tried troubleshooting based on these issues: https://github.com/mgmeyers/obsidian-zotero-integration/issues/58 https://github.com/mgmeyers/obsidian-zotero-integration/issues/95
but to no avail. Also, the exact same setup works from a windows machine, so I was wondering if this might have something to do with the M2 chipset not being supported as of yet? If so, do you plan to add support for it anytime soon?
Thanks in advance.
Best, David
Error processing PDF: Command failed with EACCES: /Users/david/pCloud Drive/Obsidian/pdfannots2json /Users/david/Zotero/storage/PSWM8L7T/Kot elnikov et al. - Accurate ligand-protein docking in CASP15 using th.pdf -n image -d 120 -f jpg-o /Users/david/pCloud Drive/Obsidian/Research/Literature Notes/kotelnikov -q 90 spawn /Users/david/pCloud Drive/Obsidian/pdfannots2json EACCES
I get a similar error when I try to re-load the executable from a different path in Obsidian. (PDF Utility Path Override)
Error checking PDF utility version: Command failed with EACCES: /Users/david/Zotero/pdfannots2json -v spawn /Users/david/Zotero/pdfannots2json EACCES
Interestingly, when I delete the custom path and it tries to fall back to the default location, it quotes "pdfannots2json-darwin-arm64", so it might have fetched a version for the wrong chipset (in lack of M2)?
Error checking PDF utility version: Command failed with EACCES: /Users/david/pCloud Drive/Obsidian/Research/.obsidian/plugins/ob sidian-zotero-desktop- connector/pdfannots2json-darwin-arm64 -v spawn /Users/david/pCloud Drive/Obsidian/Research/.obsidian/plugins/ob sidian-zotero-desktop- connector/pdfannots2json-darwin-arm64 EACCES