I've tried with Thunderbird version 52.6.0 on Debian 9 and Thunderbird version 52.4.0 on Fedora 25.
The vault is based on Fedora 25, but I've also tried running it on the Debian 9 template and nothing changed.
Also de-activating PEP and Autocrypt doesn't seem to work.
Thank you for any suggestion.
I too am experiencing the same thing. Thunderbird automatically updated Enigmail to version 2.0 and now split gpg is not working. I opened up the Enigmail console and it is using the wrapper, but nothing is happening:
Initializing Enigmail service ...
EnigmailAgentPath=/usr/bin/qubes-gpg-client-wrapper
enigmail> /usr/bin/qubes-gpg-client-wrapper --batch --no-tty --charset utf-8 --display-charset utf-8 --version --version
gpg (GnuPG) 2.2.5
libgcrypt 1.8.2
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Home: /home/user/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2
enigmail> /usr/bin/gpgconf --list-dirs
enigmail> /usr/bin/qubes-gpg-client-wrapper --charset utf-8 --display-charset utf-8 --no-auto-check-trustdb --batch --no-tty --status-fd 2 --with-fingerprint --fixed-list-mode --with-colons --list-keys
enigmail> /usr/bin/qubes-gpg-client-wrapper --charset utf-8 --display-charset utf-8 --no-auto-check-trustdb --batch --no-tty --status-fd 2 --with-fingerprint --fixed-list-mode --with-colons --list-secret-keys
enigmail> /usr/bin/qubes-gpg-client-wrapper --charset utf-8 --display-charset utf-8 --no-auto-check-trustdb --batch --no-tty --status-fd 2 --sender eric@EDITED --max-output 149800 --decrypt
enigmail> /usr/bin/qubes-gpg-client-wrapper --charset utf-8 --display-charset utf-8 --no-auto-check-trustdb --batch --no-tty --status-fd 2 --with-fingerprint --fixed-list-mode --with-colons --list-keys
enigmail> /usr/bin/qubes-gpg-client-wrapper --charset utf-8 --display-charset utf-8 --no-auto-check-trustdb --batch --no-tty --status-fd 2 --with-fingerprint --fixed-list-mode --with-colons --list-secret-keys
Enigmail is using the qubes-gpg-client-wrapper, but nothing is happening and I am not sure where to look next to see why this is the case.
I, too, am interested in a solution.
Eric
Thanks, Michael. That worked for me. How can we follow any updates if this is an Enigmail bug, at least in so far as we can know when we can update to the latest version?
Eric
couldn't figure out a fast solution so I downgraded back to v1.9.9 for
the time being.
You can do the same by downloading v1.9.9 and manually installing in
thunderbird (and unchecking "update addons automatically"):
https://www.enigmail.net/download/release/1.9/enigmail-1.9.9-sm+tb.xpi?type=application/octet-stream
I will email Enigmail mailing list so that they are aware.
Is anyone else who downgraded back to 1.9.9 getting stuck with a big autocrypt header being displayed and a missing email body when receiving emails from enigmail 2.0 users?
Any persons got the workaround listed here: https://github.com/QubesOS/qubes-issues/issues/3750 to work in 3.2? Is there a particular line it needs to be done on. When I add it to the file, all that happens is my work VM connects to my vault VM and I get a blank email no decrypted message
cubit.
--You received this message because you are subscribed to the Google Groups "qubes-users" group.To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users...@googlegroups.com.To post to this group, send email to qubes...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/L8c6SKz--3-0%40tutanota.com.For more options, visit https://groups.google.com/d/optout.
Any persons got the workaround listed here: https://github.com/QubesOS/qubes-issues/issues/3750 to work in 3.2? Is there a particular line it needs to be done on. When I add it to the file, all that happens is my work VM connects to my vault VM and I get a blank email no decrypted message
Is there plans to move the patch from r3.2 testing to stable any time soon?