-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Roberto C. Sanchez wrote: > But why would cancelling the key retrieval midstream leave gpg like it did? > When I reproduced the bug the second time, I initiated a key retrieval > (from pgp.mit.edu, if it makes a difference) and after about 60 seconds of > waiting, I cancelled it. That was what caused the locks and tmp files > to be > left behind. Could that be indicative of a gpg bug?
OK, now we're getting closer :-) This /should/ not happen (i.e. gpg should be terminated by Enigmail), but maybe this didn't happen. Did you search for a key using the Enigmail key manager, or did you try to import a key when reading a message? And what precise version of Enigmail did you use? - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCkycl2KgHx8zsInsRAhyuAJ9vK3cF+7byAPZm3MFZGOGIsEAAsQCgkRZF LUHV31/KAlh30DliuedVgwk= =g1ja -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
