Comment 11 for bug 42199

I've had the same bug, and about an hour of looking and trying figure where's that number and what's locking gpg... I found that the numbers held actually are the .lock files on ~/.gnupg/ .

I still don't understand why this happen but the workaround i can find right now and worked for me is really to erase the *.lock .