-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 07.03.13 05:02, Patrick Fleming wrote: > Patrick Brunschwig <patrick <at> enigmail.net> writes: > >> >> > >>> >>> >>> I ended up downgrading Thunderbird to 10.0.7.el6.centos.x86_64 >>> but could not get that version of enigmail to install. I was >>> able to get enigmail-1.4-sm+tb.xpi to install. 1.4.4 shows it's >>> for Thunderbird 14 and refused to install. I guess if I want >>> encryption I have to stay at this earlier version. >>> >>> Thanks for the suggestion - be nice if I could be all the way >>> up to date though. >> >> I think the problem may be related to the used GnuPG version. >> Here is why: GnuPG launches gpg-agent automatically when needed >> as of version 2.0.16. If an older version of GnuPG is found _and_ >> no running gpg-agent is detected, then Enigmail will launch >> gpg-agent. This is however an issue, as it often ends up with >> "unresponsive JavaScript" with a not completely started gpg-agent >> and Enigmail failing to complete initialization. I have tried to >> fix this, but I cannot see how -- I have given up. >> >> I see two solutions: a) upgrade to GnuPG 2.0.16 b) start >> gpg-agent during login, e.g. add this to .xsession: eval >> $(gpg-agent --daemon) >> >> -Patrick > > I did try to see if gpg-agent was the culprit based on some other > posts. If I reinstalled gpg and then immediately ran Thunderbird > all was good, but one can't reinstall software each time you want > to run another program. I also tried to run gpg-agent --daemon > prior to loading Thunderbird eg: $gpg-agent --daemon $thunderbird > > and it would work - sometimes. But all running instances of > gpg-agent had to be killed or Thunderbird would not close > completely and would be running in the background. > > I don't see where I can upgrade my production system to 2.0.16 > until it's pushed down through CentOS. What is the difference > between your command and mine? eval $(gpg-agent --daemon) and > gpg-agent --daemon ? I may try this second solution at some point.
The difference is that my version of the command sets the GPG_AGENT_INFO environment variable, and yours doesn't. GnuPG (and Enigmail) dectect that gpg-agent is running based on the environment variable. That's the reason why Enigmails tries to start a new instance of gpg-agent on your system and you have to kill everything manually. - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQEVAwUBUThHBMk25cDiHiw+AQh8Qwf9FXhFQuelSAU6Pjdlqd/O9SzQG+NEusSr pwdTfFnMMAaIAJncqgZbLAvIhyJAp+A8EC6KJqQKG2PHS9TUiV5cDInzjA4Olklz +0Z+tH4s7JJ9AiyEYC4ECWgP7oFOmq6p7P8DaPkjvKNHI8Mju99n45JpxPcpI6Xx OQqfesWlDAO67mHni1Y17bKQ0cNFi2zj2eYD2ZOUllqPqKrdZNX4mjNB2toD1KQL p24aoZkoNcwPx1ApVf3i7z3EvDVqXMNThkOFI8HdChqdEbZveUPdNevv24Lx3z88 e6l/4NgicASiDwnO3TLSPm7fkn60K8JFUrhc+zbpiPnP8Nth62gcgQ== =DDSR -----END PGP SIGNATURE----- _______________________________________________ enigmail-users mailing list [email protected] https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
