MacGPG2 #148: Signing and Decoding fails due to defect PIN Entry
Hi
I see someone has brought this up previously, Anselm on Dec. 4, 2014. I recently upgraded to beta 4 and occasionally I am also getting the same problem:
gpg: problem with the agent: No pinentry gpg: skipped "2BC9E1DD1021E5983CD619004FFEF4EEBB088944": Operation cancelled gpg: signing failed: Operation cancelled
Is this due to sleep mode changes? Recently I changed the security settings so that my login password is required to unlock the screensaver 15 minutes after it begins - it used to be required instantly. How does this affect pinentry?
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Steve on 22 Jan, 2015 08:10 PM
Hi Pertinax77,
thanks for continuously sending in useful reports! That's very welcome.
The "no pinentry" bug has been plaguing us for a long time. Only recently we discovered that it is indeed related to sleep mode. If we know what exactly is going on, we would have fixed this already. We hope to find a solution. If you have a reproduce pattern which is releable, please do let us know.
To workaround, a restart will bring you back to working state.
I've connected this discussion with the existing ticket and we'll update it, as we have news.
All the best,
steve
Steve closed this discussion on 28 May, 2015 05:17 PM.
Steve re-opened this discussion on 05 Jul, 2015 03:17 PM
Support Staff 2 Posted by Steve on 05 Jul, 2015 03:17 PM
Hi Pertinax,
good news. We think, this issue has been fixed. If you want to test the fix, please download our latest nightly GPG Suite. That page also has sig and SHA1 to verify the download. It would be very helpful, if you can provide feedback, as to whether the fix works as expected.
If you have other questions you can open a new discussion any time.
Best, steve
Disclaimer: This is a development version which has not been thoroughly tested yet, so bugs or crashes are to be expected. Thanks for helping us test this fix.
Steve closed this discussion on 24 Jul, 2015 09:15 AM.