Paul, When I migrated to gpg 2.1, I've had issues with "secret key not found" errors. This was caused by the fact that pass had installed gnupg2 as a dependency long ago but I was still using gpg 1.4 for a good while before migrating, so there were indeed keys missing.
If this sounds like your current situation, you might want to try to reimport your keys to gnupg2 with: gpg --import ~/.gnupg/secring.gpg before doing that, you can list files in ~/.gnupg/private-keys-v1.d/ . each file is named after a "keygrip". You can show keygrips with: gpg -k --with-keygrip y...@uid.tld If that solves your issue, the bug was not with pass but rather an incomplete migration to gnugp2. then you might want to get more information about this migration and what you need to adjust in your configuration to use gpg 2. hope that helps! p.s.: Thadeu: your issue seems rather quite different than the one reported first. If your issue is still persisting you might want to report it in a seperate bug report.
signature.asc
Description: OpenPGP digital signature
