Mailing List Archive

iSee <isee.receive.list@126.com> writes:

> When gpg --edit-key .... quit,
> It didn't delete pubring.gpg.lock.
>
> Then I use gpg --edit-key again,
> When I save changed key,gpg said that:
>
> Command> save
> gpg: waiting for lock (hold by 24739 - probably dead) ...
>
> I think this is a bug of gpg.

There is a small chance of a race in the locking handling which cause
a left over lock file. delete the ockfile and try to figure out why
it happens. I have not seen this for a long time.

BTW, we need some more specific bug reports to solve a problem :-)

Anyway this is on my todo list


Werner

I am getting a similiar error message.

gpg: waiting for lock (hold by 9007 -probably dead)...

This was the first time I had done gpg--edit-key, I added two uids, and
did a save and got the above error until I quited. I am using gpg0.9.2 on
redhat 5.1 running Red Hat 5.1 kerenl 2.0.35

From,
Matthew M. Copeland
matthewc@designlab.ukans.edu
copeland@eagle.cc.ukans.edu

---------------------------------------------------------------
On Mon, 25 Jan 1999, iSee wrote:

> When gpg --edit-key .... quit,
> It didn't delete pubring.gpg.lock.
>
> Then I use gpg --edit-key again,
> When I save changed key,gpg said that:
>
> Command> save
> gpg: waiting for lock (hold by 24739 - probably dead) ...
>
> I think this is a bug of gpg.
>
> I use gnupg-0.9.2 on Redhat-5.1
>
> --
> Yu xin
>

"Matthew M. Copeland" <dyelar@rdl.ml.org> writes:

> This was the first time I had done gpg--edit-key, I added two uids, and
> did a save and got the above error until I quited. I am using gpg0.9.2 on

Found - I'll fix it in the next release.