I'm a bit frustrated by my Ubuntu (17.04) Setup with Enigmail 1.9.7/GPG 2.1.15. I think after changing from Ubuntu/Unity to Ubuntu GNOME (but I really don't know if that was the trigger), Enigmail stopped working: I can't decrypt incoming encrypted emails any more. I am not asked for my GPG key password, pinentry (despite generally working in tests) skips prompting for the password and gpg-agent just tells me that there was no password given.
Thunderbird/Enigmail tells me "Missing Passphrase", that's where I started. I then debugged the problem down as far as I could, using this link, the official Enigmail troubleshooting guide and many, many more links and guides.
- I CAN sign mails (sent to myself as test), verifying them is no problem within Thunderbird.
All the pinentry tests from the Enigmail troubleshooting guide are ok, I see the GNOME styled pinentry dialog.
~/.gnupg/gpg.confcontains a `use-agent' line (even if that is not needed any more in GPG 2.1)
~/.gnupg/gpg-agent.confcontains a line
pinentry-program /usr/bin/pinentry-gnome3- even
pinentry-program /usr/bin/pinentryworks here, as it automatically detects the
I've started a gpg-agent using
gpg-agent --debug-level expert --daemon /bin/sh, logging all gpg agent activities, which outputs while trying to decrypt:
gpg-agent: DBG: chan_4 -> INQUIRE PINENTRY_LAUNCHED 22797 gpg-agent: DBG: chan_4 <- END gpg-agent: DBG: error calling pinentry: No passphrase given <GPG Agent> gpg-agent: failed to unprotect the secret key: No passphrase given gpg-agent: failed to read the secret key gpg-agent: command 'PKDECRYPT' failed: No passphrase given gpg-agent: DBG: chan_4 -> ERR 67109041 No passphrase given <GPG Agent> gpg-agent: DBG: chan_4 <- [eof]
If I save the encrypted mail to an eml file and do a
gpg -d file.eml manually. Same result as before:
$ gpg -d FM.eml gpg: encrypted with 4096-bit RSA key, ID XXXXXXXXXXXXXXXX, created XXXX-XX-XX "Christian Gonzalez <email@example.com>" gpg: public key decryption failed: No passphrase given gpg: decryption failed: No secret key
~/.gnupg/gpg.conf and removing the line
did help in the first place, but after a system restart, the old problem returned.
Does anyone have a hint for me?
Maybe it has to do with Ubuntu's "peculiarity" in using Gnome-Keyring as agent? Is that true?