Control: tags 795639 + moreinfo Control: reassign 795639 gnupg2 2.1.7-2 Control: affects 795639 assword
Hi Russ--
On Sun 2015-08-16 01:03:16 +0200, Russ Allbery wrote:
> strace seems to back that up. It chats with the agent for a bit, and
> then it fails. See the partial trace below. It seems to get as far
> as realizing that I don't currently have the secret key unlocked, but
> then rather than popping up a dialog to prompt me, just immediately
> fails.
Thanks for sending this report. I've been using gpg 2.1.7 for
several months now, and i haven't had this problem. Hopefully we can
diagnose what's going on here.
fwiw, i agree that this is most likely a bug we should deal with in
gnupg2, not in assword.
> Running gpg manually on a file pops up the agent dialog like I would
> expect.
does this succeed with gpg2 --decrypt as well, or just gpg --decrypt?
do you see files listed when you look at the GnuPG 2.1 secret key storage:
ls -l ~/.gnupg/private-keys-v1.d/*.key
what about checking to see the date that GnuPG 2.1 did the keyring
migration:
ls -l ~/.gnupg/.gpg-v21-migrated
?
> I tried killing all the agents and logging out and then back in again to
> force the agent to respawn, but unfortunately there was no change in
> behavior.
Depending on the output of the above, maybe you can try importing your
secret keyring again:
gpg2 --import < ~/.gnupg/secring.gpg
(this should have been imported automatically for you upon your first
use of gpg 2.1 after the upgrade)
Please let me know if this solves the problem for you, or if you learn
any new information.
Regards,
--dkg
signature.asc
Description: PGP signature
