Quoting Patrick Brunschwig <[EMAIL PROTECTED]>:
The lock files are normal and required. If enigmail opens several gpg
processes you might get into a deadlock situation. From you rlisting
it seems that 2 processes are running. Please provide more
information for example by attaching strace to the running gpg
processes.
Enigmail (or rather Mozilla) has some internal problems in handling
several gpg prcesses correctly, so wherever possible I try to prevent this.
I have tried to reproduce the problem with the files provided (on a
Windows system though; I don't have a Linux system available), but I
could not find anything to be wrong. It's true that recalculating the
trustdb takes a while, but Enigmail just waits happily until gpg is
ready with calculating.
-Patrick
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?
-Roberto
--
Roberto C. Sanchez
http://familiasanchez.net/~sanchezr
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
