Quoting James Troup <[EMAIL PROTECTED]>:
severity 310328 normal
thanks
Hi,
Unless someone can a) reproduce this and b) provide (the non-secret
parts of) the .gnupg directory and/or diagnose the actual problem,
there's nothing I can do about this and no reason for it to remain
grave.
Eureka! It appears to be more of an gpg issue. It actually happens when
importing a key through enigmail. If the key import takes a long time, the
extraneous files are left in ~/.gnupg and enigmail is totally unable to figure
out what is going on. Note that there a number of "dot" files in the
directory.
I have placed it on the web at http://nipl.net/~sanchezr/bug310328.tar.bz2
and it is HUGE (14MB) since I needed to use my public keyring with enough
keys to slow down gpg. The private key expires 30 May and is for Nobody
<[EMAIL PROTECTED]> with a pass phrase of "Fake key." without quotes.
Here are the directory contents:
[EMAIL PROTECTED]:~$ tar tvjf bug310328.tar.bz2
tar: Record size = 8 blocks
drwx------ sanchezr/sanchezr 0 2005-05-23 13:06:32 .gnupg/
-rw------- sanchezr/sanchezr 1051 2005-05-23 12:44:01 .gnupg/secring.gpg
-rw------- sanchezr/sanchezr 7558912 2005-05-23 13:04:11 .gnupg/pubring.gpg
-rw------- sanchezr/sanchezr 1280 2005-05-23 13:04:11 .gnupg/trustdb.gpg
-rw------- sanchezr/sanchezr 600 2005-05-23 12:54:51 .gnupg/random_seed
-rw------- sanchezr/sanchezr 7553299 2005-05-23 03:19:52 .gnupg/pubring.gpg~
-rw-r--r-- sanchezr/sanchezr 11 2005-05-23 13:04:11
.gnupg/.#lk0x811ff90.miami.8621
-rw-r--r-- sanchezr/sanchezr 11 2005-05-23 13:04:11
.gnupg/.#lk0x8120230.miami.8621
-rw-r--r-- sanchezr/sanchezr 11 2005-05-23 13:04:11
.gnupg/.#lk0x8120528.miami.8621
hrw-r--r-- sanchezr/sanchezr 0 2005-05-23 13:04:11
.gnupg/pubring.gpg.lock
link to .gnupg/.#lk0x811ff90.miami.8621
hrw-r--r-- sanchezr/sanchezr 0 2005-05-23 13:04:11
.gnupg/secring.gpg.lock
link to .gnupg/.#lk0x8120230.miami.8621
-rw------- sanchezr/sanchezr 5734400 2005-05-23 13:04:14
.gnupg/pubring.gpg.tmp
-rw-r--r-- sanchezr/sanchezr 11 2005-05-23 13:04:35
.gnupg/.#lk0x811ca40.miami.8706
-rw-r--r-- sanchezr/sanchezr 11 2005-05-23 13:04:35
.gnupg/.#lk0x811ca58.miami.8706
-rw-r--r-- sanchezr/sanchezr 11 2005-05-23 13:06:32
.gnupg/.#lk0x811a458.miami.8932
-rw-r--r-- sanchezr/sanchezr 11 2005-05-23 13:06:32
.gnupg/.#lk0x8117128.miami.8932
-rw-r--r-- sanchezr/sanchezr 11 2005-05-23 13:06:32
.gnupg/.#lk0x8117220.miami.8932
Also, here is what happens to gpg afterward:
$ wget
http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/powerpc/rc3/MD5SUMS
$ wget
http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/powerpc/rc3/MD5SUMS.sign
$ gpg --verify MD5SUMS.sign
gpg: Signature made Wed 23 Mar 2005 08:45:44 PM EST using DSA key ID F6A32A8E
gpg: checking the trustdb
gpg: waiting for lock (held by 8621 - probably dead) ...
gpg: waiting for lock (held by 8621 - probably dead) ...
gpg: waiting for lock (held by 8621 - probably dead) ...
gpg: waiting for lock (held by 8621 - probably dead) ...
gpg: waiting for lock (held by 8621 - probably dead) ...
gpg: waiting for lock (held by 8621 - probably dead) ...
gpg: waiting for lock (held by 8621 - probably dead) ...
gpg: Interrupt caught ... exiting
I have to Ctrl-C to get out of it.
Executing a `rm -f .#lk0x81* *.lock *.tmp` in ~/.gnupg seems to be enough
to let gpg recover, but I can't say anything for the consistency of the
keyrings.
I hope this helps. Sorry for all the uneccesary noise earlier :-)
-Roberto
--
Roberto C. Sanchez
http://familiasanchez.net/~sanchezr
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
