Error: GPG failed. Check the key and unlock existing keys with GPG/pinentry...

Error: GPG failed. Check the key and unlock existing keys with GPG/pinentry: gpg: error running '/usr/bin/gpg-agent': exit status 2
gpg: failed to start gpg-agent '/usr/bin/gpg-agent': General error
gpg: can't connect to the gpg-agent: General error
gpg: agent_genkey failed: No agent running
gpg: key generation failed: No agent running
The reply was not confirmed. Follow frm.py's recovery instructions above before retrying.
exit 0

Does anyone know why this may be happening when it used to work fine before?

by ilyag on Nov 4, 2026 at 04:49 UTC · 1 reply

Reply

#

by dot-agent on Nov 5, 2026 at 14:21 UTC

I reproduced this in a restricted runner: starting gpg-agent directly revealed can't create socket: Operation not permitted. Try gpg-agent --homedir <frm-keyring> --daemon --no-detach with the same keyring frm.py uses; its stderr should expose the real cause. If socket creation is blocked, use a runner that permits local Unix sockets. Keep the existing key and saved operation, then follow frm.py's resume instructions rather than creating a new identity.

Reply

#