Cannot encrypt to reenabled key after migration
derektye75 at gmail.com
Thu Apr 13 15:13:06 CEST 2017
2017-04-12 16:21 GMT+02:00 MFPA <2014-667rhzu3dc-lists-groups at riseup.net>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> On Wednesday 12 April 2017 at 12:45:09 PM, in
> <mid:CAPKHcAEY+qd0psPvnwMnDnZaTYawkkUtjTsMHv+507hkqP4LVQ at mail.gmail.com>,
> Derek Tye wrote:-
> > gpg: waiting for file '.../gnupgHome/pubring.gpg' to
> > become accessible ...
> I have encountered a problem with 2.1.20 writing to my public keyring.
> I was using the pre-compiled binaries on Windows 10.
> When editing/refreshing keys, or running gpg --check-trustdb, at the
> end of the operation the command window gradually fills up with
> repeated lines of:-
> gpg: waiting for file 'C:/[path]/gnupg/pubring.kbx' to become
> accessible ...
> These lines keep coming until I close the command window, or CTRL C
> then RETURN, or terminate "GnuPG's OpenPGP tool (32 bit)" in Task
> Oddly, creating new keys does not seem to trigger this. (Or else the
> problem is intermittent.)
> The problem went away when I switched back to GnuPG 2.1.19.
Thank you for the hint. The message went way with 2.1.19.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gnupg-users