On Thursday, 19 October 2017 19:46:47 BST Lucas Ramage wrote: > Oh that's odd. I wonder if it's an issue with gpg?
I suspect something in my configuration has deviated from vanilla and this is
causing the problem of 'set crypt_use_gpgme' not being enough. This is what
I'm running here:
app-crypt/gpgme-1.8.0-r3
Installed versions: 1.8.0-r3(1)(08:33:15 05/10/17)(cxx qt5 -common-lisp
-python -static-libs PYTHON_TARGETS="python2_7 python3_4 -python3_5")
dev-libs/libgpg-error-1.27-r1
Installed versions: 1.27-r1(09:15:46 03/21/17)(nls -common-lisp -static-
libs ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64"
ABI_X86="32 64 -x32")
app-crypt/gnupg-2.1.20-r1
Installed versions: 2.1.20-r1(10:45:25 05/21/17)(bzip2 gnutls ldap nls
readline smartcard usb -doc -selinux -tofu -tools -wks-server)
mail-client/mutt-1.7.2
Installed versions: 1.7.2(06:14:56 07/11/17)(crypt gdbm gpg imap mbox
nls nntp pop sasl sidebar smime smtp ssl -berkdb -debug -doc -gnutls -idn -
kerberos -libressl -notmuch -qdbm -selinux -slang -tokyocabinet -vanilla)
I haven't tried troubleshooting gpgme when running mutt to see what the logs
spew out. xsession-errors and syslog does not reveal anything. I should give
this some attention when I get a free moment.
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
