On Fri, Apr 25, 2008 at 01:22:53PM +0000, Goedson Teixeira Paixao wrote: > Em Sex, 2008-04-25 às 07:51 +0200, Yves-Alexis Perez escreveu: > > > > From this > > > > terminal, do you have the following env var: $GPG_AGENT_INFO > > > > > > > > > $env |grep GPG > > > GPG_AGENT_INFO=/tmp/seahorse-vMaArS/S.gpg-agent:4166:1 > > > > Ok so evolution should be aware of GPG agent running. But as it's > > seahorse I don't know how it works nor how it may bug. > > > > If you try to sign something from commandline (using gpg), does a window > > popup to ask you your passphrase? > > OK. I've finally found the problem. My ~/.gnupg/gpg.conf had the > "use-agent" option commented out. Enabling it and installing > pinentry-gtk2 made the signing work again. > > So I think evolution should at least recomment pinentry-gtk2 and mention > the need for the use-agent option in the README file (or force the > use-agent option). > > Thanks for the help in spoting the problem.
Well, I dont know how seahorse work. But if you start seahorse and if it exports the GPG_AGENT_INFO, all apps assume there is a gpg agent running. In this case, evo wont use it's internal popup to ask you the passphrase, but will pass this to $GPG_AGENT. Afaict, it's the agent responsibility to make sure user can enter the passphrase. gnupg-agent Recommends pinentry, and I dont know about other agents. If $GPG_AGENT_INFO isn't detected (user doesnt run a gpg agent), evo takes care of this, so in this case the bug may lie in evo. Can you try running evo with $GPG_AGENT_INFO unset? If it asks you a passphrase, no problem in evo. Cheers, -- Yves-Alexis _______________________________________________ Pkg-evolution-maintainers mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-evolution-maintainers
