Skip to main content
Participant
September 23, 2021
Answered

Adober Reader DC crashing because /usr/lib/libcrypto.dylib

  • September 23, 2021
  • 4 replies
  • 4556 views

Hi, since I updated my MacBook to v.11.6, Adobe Reader DC v.21.007.20091 is crashing every time I try to open it. The error message is the following:

 

Process: AdobeReader [16711]
Path: /Applications/Adobe Acrobat Reader DC.app/Contents/MacOS/AdobeReader
Identifier: AdobeReader
Version: 21.007.20091 (21.007.20091)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: AdobeReader [16711]
User ID: 501

Date/Time: 2021-09-23 16:48:57.438 -0300
OS Version: macOS 11.6 (20G165)
Report Version: 12
Anonymous UUID: A9C7C342-E452-6FBD-B5B4-ADB4F803FBE1


Time Awake Since Boot: 160000 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:
/usr/lib/libcrypto.dylib
abort() called
Invalid dylib load. Clients should not load the unversioned libcrypto dylib as it does not have a stable ABI.

 

Someone knows how to fix this? I've find similar issues in this forum, but no one with a practical way to solve it. 

 

Thanks.

 

This topic has been closed for replies.
Correct answer default9qfdmzdv18a4

use XCode or any other plist editor and remove everything under DC/Security/ASPKI (click on Item 0, Item 1 and delete (Fn backspace)). Worked for me, thank you very much @Prashant. 

4 replies

Celso5C9EAuthor
Participant
September 30, 2021
Hi all,

I couldn’t find the file com.adobe.reader.plist located at "/Users//Library/Preferences". The one I’ve found is com.adobe.acrobat.pdfviewer.plist, but it doesn’t contain the entry you mentioned 🙁

Thanks.

Celso.
Adobe Employee
September 28, 2021

Hi @Celso5C9E ,

 

Looks like the etoken module that you are using is not compatible with Reader.

You can first try deleting the entry "Adobe_P11CredentialProvider" in com.adobe.reader.plist located at "/Users/<user directory>/Library/Preferences" under DC/Security/ASPKI. Deleting this key would remove all the pkcs11 modules that you   have attached. Once that is removed your reader would start working correctly . Then you can download and install the latest etoken driver and then try to attach the latest module to pkcs11 module settings in Reader Preferences.

  1. Open Preferenes->Signature – Identities & Trusted Certificates; 
  2. Select PKCS11# Modules and Tokens;
  3. Select Attach Module and then provide the correct dylib path for your etoken.
  4. Select your token provider's name and select Login and type the password of the token.

After that try signing.

Let us know if this helps.

 

Thanks,

Prashant.

Participant
September 28, 2021

As I have the same problem, could you please let me know how do I actually delete the entry "Adobe_P11CredentialProvider"?

As you can see in the attached screenshot, when I open the com.adobe.reader.plist file, I don't understand where the entry starts and where it ends. I mean, what exactly do I have to delete? 

 

Thank you for your time.

Adobe Employee
September 28, 2021

Hi @Roby_B ,

 

You can use any Plist editor to make changes in plist. Common one being Xcode.

If you do not want to delete the entry "Adobe_P11CredentialProvider" or for some reason you are not able to, then you can skip this step and can simply try to reinstall the latest etoken driver from your token provider's website and then try to attach the latest module to pkcs11 module settings in Reader Preferences.

JR Boulay
Community Expert
Community Expert
September 24, 2021

MOVED TO THE ACROBAT READER FORUM

Acrobate du PDF, InDesigner et Photoshopographe
Participating Frequently
September 27, 2021

Hi, I can't find further information how to fix this in the forum.

Do you know where can I find it?

 

Thanks

Legend
September 27, 2021

Adobe say they will fix it, some day. Meanwhile we must wait. 

Amal.
Community Manager
Community Manager
September 24, 2021

Hi Celso

 

Hope you are doing well and sorry for the trouble.

 

This issue is already reported to our engineering team and they are working in it to find the fix.

 

We will share the update as soon as we will hear anything from them.

 

Thanks for your time and patience on this

 

Regards

Amal

Celso5C9EAuthor
Participant
September 24, 2021

Thanks Amal. I'll be waiting for the fix.

 

Best regards.

 

Celso.