"gpgconf --kill all" solved my problem, but I'd still advise y'all to
look into where it got wedged and why -- this was an incredibly annoying
problem to solve, and the total lack of debugging output elevated it to
tremendously frustrating.
I'm such an idiot, I forgot I was sshed into another
Try attaching gdb to see where it hangs.
(gdb) run
Starting program: /usr/local/bin/gpg --list-keys
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Detaching after fork from child process 41865]
^C
"gpgconf --kill all" s
Which version exactly are you using?
2.3.3.
Try attaching gdb to see where it hangs.
(gdb) run
Starting program: /usr/local/bin/gpg --list-keys
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Detaching after fork from
On Montag, 6. Dezember 2021 02:28:07 CET Robert J. Hansen via Gnupg-users
wrote:
> rjh@ripley:~$ gpg - --list-keys
> gpg: using character set 'utf-8'
> gpg: Note: RFC4880bis features are enabled.
> gpg: key 1DCBDC01B44427C7: accepted as trusted key
> gpg: key 1E7A94D4E87F91D5: accepted as trus
