Cannot encrypt to reenabled key after migration

[MFPA]

-----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
Manager.

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.

- --
Best regards

MFPA                  <mailto:2014-667rhzu3dc-lists-groups at riseup.net>

Keep them dry and don't feed them after midnight
-----BEGIN PGP SIGNATURE-----

iNUEARYKAH0WIQQzrO1O6RNO695qhQYXErxGGvd45AUCWO439F8UgAAAAAAuAChp
c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0MzNB
Q0VENEVFOTEzNEVFQkRFNkE4NTA2MTcxMkJDNDYxQUY3NzhFNAAKCRAXErxGGvd4
5C8pAQD7LfN2DrFXaJHJdxmpzM9sBcr2Pi6SOgvT7lJxkUVy2AD/fbKlrk+gDlCf
d08/GjB62q3FYY/i6vPKTx21bFm5fAiJAZMEAQEKAH0WIQSzrn7KmoyLMCaloPVr
fHTOsx8l8AUCWO439F8UgAAAAAAuAChpc3N1ZXItZnByQG5vdGF0aW9ucy5vcGVu
cGdwLmZpZnRoaG9yc2VtYW4ubmV0QjNBRTdFQ0E5QThDOEIzMDI2QTVBMEY1NkI3
Qzc0Q0VCMzFGMjVGMAAKCRBrfHTOsx8l8FcMCACl1XxPWIFDz0BaAgDIdLRtjWU2
tIOz5iVAi1UUNLZYdrX3Gwb5lBjGViJlTo6I/fO3TQPWgZf9VynnHYhFXB4I0aOs
zlH/WvpRfOzVTN9cBWciFdyF8U1VIgSyjyQNXEzlxHgh4jiYFUnZ04UaSM9NLU0i
dErHpNq6aB2TLcvxmfRqoh7BvBDX9I038CI5sv00sldt5hbt1x8Vq8p49JxoA/iD
7UN9pVRQC4mtIeo7ZrTG8ATWYLoZ70lW047OozEiHzEpFgH3id4I1h/wiFb1be5c
pUt5m1gp7PTw4EkThOLCX8uPJjMflEECd+rYxV/JSKxaNq3SfmLSJpIq9DRT
=yvI/
-----END PGP SIGNATURE-----