Using Thunderbird with the crypt use flag needs pinentry for the enigmail password prompt. If eselect pinentry was set to the ncurses backend (not sure but I think this even may be the default), then mail de-/encryption silently fails without any further hints at all. Instead the pinentry-gtk backend is required for Thunderbird's enigmail addon to work correctly. This is a hard to debug issue, since there is no error description whatsoever visible for the user, not even when starting Thunderbird from the terminal. Reproducible: Always Steps to Reproduce: 1. emerge thunderbird with crypt use flag 2. try to decrypt/encrypt mail with enigmail and pinentry-ncurses backend Actual Results: enigmail fails without silently further hints Expected Results: emerging thunderbird check for the selected pinentry backend or at least print a warning to not use pinentry-ncurses.
urgh, this use flag shouldn't really exist in the first place. literally all it does is install an extension. re: this problem specifically, it should be diagnosable through OpenPGP -> Debugging Options -> View Console.
(In reply to Alex Xu (Hello71) from comment #1) > urgh, this use flag shouldn't really exist in the first place. literally all > it does is install an extension. Then please remove it. > re: this problem specifically, it should be diagnosable through OpenPGP -> > Debugging Options -> View Console. The OpenPGP console only shows the command invokation: > enigmail> /usr/bin/gpg --charset utf-8 --display-charset utf-8 --batch --no-tty --status-fd 2 --decrypt --use-agent But nothing more. If I de-/encrypt another mail I see another line like this -- that's it, no more details are given.
What might make more sense is if we can call the pinentry backend directly, somehow... although (and this is just conjecture as i have no idea if said thing exists) if there are hardware-based pinentry options, these would no longer work with enigmail.
(In reply to Ian Stakenvicius from comment #3) > What might make more sense is if we can call the pinentry backend directly, > somehow... although (and this is just conjecture as i have no idea if said > thing exists) if there are hardware-based pinentry options, these would no > longer work with enigmail. For non GUI pinentry (i.e. ncurses) it is also possible to specify another TTY to get the password request on that can be used for password entry. I fail to see how calling pinentry backend should help, as it'd only increase complexity and needed for the password to be provided to gpg again through some other means. FWIW, your conjecture would be applicable to smartcards with pinpads.
If you feel I have closed your bug and it is still a current issue, please reopen and update it completely. We will not work bugs that have no ebuild in tree any longer or can not be reproduced with a current system. Thank You for your support and understanding The Mozilla Team
