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