-
All replies
-
Helpful answers
-
Jul 28, 2016 9:35 AM in response to walkerapby stonesd,I am having the same issue on multiple systems. However, not all my 10.11.6 systems are having this issue. So, I went through the signing process on both systems and captured the logs. There was only a few noticeable differences between the two. On the system that IS working the following log entries are present, but they are not present in the system NOT working.
7/28/16 9:09:49.634 AM WindowServer[2852]: disable_update_timeout: UI updates were forcibly disabled by application "Acrobat Reader" for over 1.00 seconds. Server has re-enabled them.
7/28/16 9:09:51.020 AM WindowServer[2852]: common_reenable_update: UI updates were finally reenabled by application "Acrobat Reader" after 2.39 seconds [0.42fps] (server forcibly re-enabled them after 1.00 seconds [1.00fps])
I have no idea what this means, but I am hoping someone reading this might be able to use this info to help solve the problem.
-
Jul 28, 2016 2:50 PM in response to walkerapby Ajohnsto42,Same Problem Here....Started happening to me on Monday the 25th of July. Worked perfect on Sunday. I hope this gets fixed....major issue. Please let me know if anyone finds out a fix.
-
Jul 29, 2016 9:54 AM in response to walkerapby jnojr,I'm in the same boat. Some Macs will sign, some won't.
-
Jul 29, 2016 2:05 PM in response to walkerapby jnojr,I have first-hand confirmation that senior Apple engineers are aware of and working with Adobe on this issue. Hopefully there'll be a fix shortly.
-
Aug 4, 2016 10:49 PM in response to walkerapby Sghoover,I have this issue as well and somebody needs to fix this ASAP. I use my MAC for military duty and the only way I can digitally sign official documents is by using Adobe Acrobat. Without this I am not getting extremely important work done and orders signed.
Fix this NOW!
SFC SGH
-
Aug 8, 2016 7:06 AM in response to walkerapby stonesd,FYI, the optional hotfix 15.017.20053 Adobe released on August 2nd does not fix the issue.
-
Aug 11, 2016 7:59 AM in response to walkerapby m.ferreira,The same is happening to me when using both Acrobat Reader DC and Acrobat Pro together with the Portuguese Citizen Card (that holds the certificates for digital signing).
I don't know how many people are being affected by this issue, but if all the Portuguese Citizen Cards are not functioning since the update, this is a major issue for businesses and government transactions in Portugal that fully rely on digital signatures.
Hope a fix comes soon.
-
Aug 11, 2016 8:38 AM in response to m.ferreiraby jnojr,Anyone who uses a PKCS11 module might be able to fix by following along with:
Got digital signing working again. Had to add the CACKey PCKS#11 module (what Firefox uses) to Adobe Reader:
Instructions:
- Preferences —> Signatures —> Identities & Trusted Certificates —> More…
- Click "PKCS#11 Modules and Tokens”
- Click “Attach Modules”
- Enter path to your PKCS#11 module; for CACKey this is /Library/CACKey/libcackey.dylib
- Click “OK”
- Click the little triangles to open up the module until you see the card
- Click the card
- Click on the email signing certificate (look for one issued by DOD EMAIL CA-xx and includes Intended usage of Digital Signature)
- Click the “Usage Options” popup menu and select “Use for Signing”
- Click Close, then Click OK.
-
Aug 11, 2016 9:36 AM in response to walkerapby rde@vick,Thanks for the information jnojr. This works for some users but unfortunately this does not fix systems which utilize Centrify for CAC authentication. Installation of CACKey breaks Centrify and installing the PKCS11 module installed by Centrify results in an error along the lines of "the module could not be loaded." Apple, Adobe, someone really needs to address this situation soon. The ability to sign documents is a major work stoppage.
-
Aug 11, 2016 9:42 AM in response to jnojrby rde@vick,Have you heard anymore news from Apple on this issue ?
-
Aug 11, 2016 9:53 AM in response to rde@vickby jnojr,Understood, I'm in the same boat... we use PKard which also doesn't supply a PKCS11 module. This is one thing I hate... they say "We won't do that because the correct way to handle this stuff is with Keychain", while Mozilla, most notably, says, "We won't use Keychain because it isn't OS-agnostic, they should support PKCS11!"
-
Aug 11, 2016 9:54 AM in response to rde@vickby jnojr,I have been in communication with a pretty senior Apple engineer who is aware of this issue and who indicated he was in communication with Adobe. I can say with a pretty high degree of certainty that this will be fixed, I just couldn't guess when.
-
Aug 11, 2016 2:47 PM in response to walkerapby Scuba Steve007,It's really unfortunate to have this issue and neither side knows how to fix it. I've spent hours with Adobe in my computer and on the phone just to have them elevate my issue 3 times....still not fixed. Then to chat with Apple support and the only result was for me to install a program so they could monitor my Mac....no thanks. Fix it please so I'm not wasting more time and money.
-
Aug 11, 2016 8:49 PM in response to walkerapby etresoft,Hello everyone,
Software updates do not happen like they did in the past. All companies release updates very frequently and they are not going to be tested with 3rd party software. Often these updates are meant to address possible security exploits. Anyone who depends on any software needs to perform their own testing before updating any critical systems. Neither Apple nor Adobe will do this testing for you. There is no point in wasting your time complaining about it. This is the new normal.