If mail-client/evolution is built with crypt support, it calls app-crypt/pinentry to request the user's password when using the secret key for signing. If app-crypt/pinentry is built without 'gtk' USE flag, the user will never see the prompt and evolution will lock up; this freeze spreads to the rest of the system as evolution and pinentry use increasing amounts of resources. Rebuilding app-crypt/pinentry _with_ the 'gtk' USE flag allows the pinentry dialog to come up. Not installing pinentry causes evolution to fail to sign messages, stating that there have been 3 unsuccessful attempts to enter the user's gpg password. Reproducible: Always Steps to Reproduce: 1. Build mail-client/evolution with 'crypt' USE flag 2. Build app-crypt/pinentry without 'gtk' USE flag 3. Try to send a gpg-signed message Actual Results: evolution locks up; a pinentry process can be seen in 'top', but no dialog comes up. Overall system responsiveness is noticeably degraded. Expected Results: Perhaps the 'crypt' USE flag should cause evolution to depend on a gtk-enabled pinentry?
On further thought, the 'qt' use flag should work, too. Perhaps the evolution ebuild should fail and prompt the user to pick one or both flags.
Hmm... evo doesn't call pinentry itself. It legitimately doesn't have a dep on it. The question is, how does pinentry get called? gnupg doesn't have a dep on pinentry that I can see...
Okay, I was wrong. gnupg does dep on pinentry.
It looks like this is being addressed in bug 160302, which predates this one. *** This bug has been marked as a duplicate of bug 160302 ***
