On Sun, 22 Jun 2025 21:46, Suhas Srivastava said: > library. After examining that issue, the author suggested that the leftover > lock files may be a gpg issue and not a library issue. The whole error
These lock files like ~/.gnupg/#lk0x0000558d3fe5e990.foo.24728 are created as part of atomic updates. If an update fails for example due to improper spawning of the gpg binary, gpg's cleanup can't run and thus the files will not removed. All classical Unix installations employ a cron job to remove files name ".#*" after a few days. If you have a lot of them there might be a problem in your python-gnupg library (SIGPIPE ignored?). I would suggest to switch to a gpgme based library like gpgme 1.24 or the new gpgmepy 2.0.0. Salam-Shalom, Werner -- The pioneers of a warless world are the youth that refuse military service. - A. Einstein
openpgp-digital-signature.asc
Description: PGP signature
_______________________________________________ Gnupg-users mailing list [email protected] https://lists.gnupg.org/mailman/listinfo/gnupg-users
