2.3 keydb problems

Robert J. Hansen rjh at sixdemonbag.org
Sat Feb 27 18:20:17 CET 2021


> int keyboxd.conf, gpgconf --kill keyxboxd, and try again.  This should
> at least show where it hangs.

gpgconf hanged while trying to kill keyboxd.  Interesting.

I 'sudo kill'ed the keyboxd process and tried again.  It appears to be 
waiting forever for a stale lock:

[rjh at localhost ~]$ tail -f keyboxd.log
2021-02-27 12:17:04 keyboxd[65434] listening on socket 
'/run/user/1000/gnupg/S.keyboxd'
2021-02-27 12:17:05 keyboxd[65435] waiting for lock (held by 535569) ...
2021-02-27 12:17:06 keyboxd[65435] waiting for lock (held by 535569) ...
2021-02-27 12:17:08 keyboxd[65435] waiting for lock (held by 535569) ...
2021-02-27 12:17:12 keyboxd[65435] waiting for lock (held by 535569) ...
2021-02-27 12:17:20 keyboxd[65435] waiting for lock (held by 535569) ...
2021-02-27 12:17:28 keyboxd[65435] waiting for lock (held by 535569) ...

There is no process with PID 535569.

The same stale lock is responsible for gpgconf not being able to kill 
the process.



More information about the Gnupg-devel mailing list