Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1006197: gpg hangs when importing keys with "gpg: waiting for lock (held by xxxxxxx) (deadlock?)"
1,058 views
Skip to first unread message
Ron Murray
Feb 20, 2022, 9:40:04 PM2/20/22
to
Package: gpg
Version: 2.2.27-3
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Dear Maintainer,
When importing public keys, gpg hangs for several minutes with
something like
gpg: waiting for lock (held by 1308345) (deadlock?) ...
Process 1308345, in this case, was
1308345 ? RL gpg --disable-dirmngr --batch --no-sk-comments --status-fd 21 --no-tty --charset utf8 --enable-progress-filter --exit-on-status-write-error --display :0.0 --logger-fd 25 --with-colons --with-secret --with-keygrip --list-keys --
... and the only other gpg process was
1307658 pts/2 SL+ 0:00 gpg --edit-key 5B80C5754298F0CB55D8ED6ABCEF7E294B092E28
I first noticed this problem almost a year ago, but didn't report
it at the time. I looks to me as if process 1308345 is waiting for an
input, but I don't see any prompts or dialog boxes.
Problem seems to time out eventually, so importing keys is still
(vaguely) possible, so I'm leaving this report marked as "normal".
Thanks,
.....Ron
- -- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.16.10.khufu (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gpg depends on:
ii gpgconf 2.2.27-3
ii libassuan0 2.5.5-1
ii libbz2-1.0 1.0.8-5
ii libc6 2.33-6
ii libgcrypt20 1.9.4-5
ii libgpg-error0 1.43-3
ii libreadline8 8.1.2-1
ii libsqlite3-0 3.37.2-2
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages gpg recommends:
ii gnupg 2.2.27-3
gpg suggests no packages.
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iQJCBAEBCgAsFiEETZlw4yMXM0sUHntjEvfoZbXi52EFAmIS9oYOHHJqbXhAcmpt
eC5uZXQACgkQEvfoZbXi52HiAg//eEasBs7zU9MefiCFcmgtg6Oi6hxPkYPlAgrH
b4BA3owGigPA/tEcAoDkY7IfKdslMrPGwV3JWCMh38dE10/yiQ5aAaaw892R+iYL
mIPYoirWFiiaAW5oIFCiYf4JKLi6a1QTdTeuznaz1cJzNo98y00VNa7kuyTuB803
i0pwm4TNJf6e9mezhTKvfg+U6S7BMIsw5RLDTK1uGjDfk8wQ8fD/6ReCSVPqb0W7
fhDfb6epmj7FPv9MfH9RxzScdHtza/js0OCsyp43iMl334nwgt5OACynLcC4FE2g
L2hx8cuTt/Wz2ZqB2j3JhfMqZ6nAdORKDQOO0vJy9kfxjzAclwPjKhzUOpfy10TB
6bxn8UUBTurHeewlBXgrsQxtO7f7VwynD1Ws2PCfPzu7+QfcA3ChMOU5t7DfcqMP
6UuMjQ67ZWSXTSUKLrkLeFiYsvzclQNqDKGCh2I99HuXHJJG2ytMmhCDp8GOiLqt
d4qWQ4D7AjcNhBkMGEtMIfjYeTzjUZmYhc1iP6WSZpebw7my+9v34BDk39lKmNvj
IKDTrvkBICQEU2ufgsF4ef76kzeCKo7xiVyfw4p7hdJJapn3aK7p3IPnAVVkf600
fPadXSjFSPZy9KvwYUc3ijGU7viGqeMQ2tXtesCSOHJqYbOMYUDjWyyDWcf0RfS8
YokE8/E=
=rIFO
-----END PGP SIGNATURE-----
Version: 2.2.27-3
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Dear Maintainer,
When importing public keys, gpg hangs for several minutes with
something like
gpg: waiting for lock (held by 1308345) (deadlock?) ...
Process 1308345, in this case, was
1308345 ? RL gpg --disable-dirmngr --batch --no-sk-comments --status-fd 21 --no-tty --charset utf8 --enable-progress-filter --exit-on-status-write-error --display :0.0 --logger-fd 25 --with-colons --with-secret --with-keygrip --list-keys --
... and the only other gpg process was
1307658 pts/2 SL+ 0:00 gpg --edit-key 5B80C5754298F0CB55D8ED6ABCEF7E294B092E28
I first noticed this problem almost a year ago, but didn't report
it at the time. I looks to me as if process 1308345 is waiting for an
input, but I don't see any prompts or dialog boxes.
Problem seems to time out eventually, so importing keys is still
(vaguely) possible, so I'm leaving this report marked as "normal".
Thanks,
.....Ron
- -- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.16.10.khufu (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gpg depends on:
ii gpgconf 2.2.27-3
ii libassuan0 2.5.5-1
ii libbz2-1.0 1.0.8-5
ii libc6 2.33-6
ii libgcrypt20 1.9.4-5
ii libgpg-error0 1.43-3
ii libreadline8 8.1.2-1
ii libsqlite3-0 3.37.2-2
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages gpg recommends:
ii gnupg 2.2.27-3
gpg suggests no packages.
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iQJCBAEBCgAsFiEETZlw4yMXM0sUHntjEvfoZbXi52EFAmIS9oYOHHJqbXhAcmpt
eC5uZXQACgkQEvfoZbXi52HiAg//eEasBs7zU9MefiCFcmgtg6Oi6hxPkYPlAgrH
b4BA3owGigPA/tEcAoDkY7IfKdslMrPGwV3JWCMh38dE10/yiQ5aAaaw892R+iYL
mIPYoirWFiiaAW5oIFCiYf4JKLi6a1QTdTeuznaz1cJzNo98y00VNa7kuyTuB803
i0pwm4TNJf6e9mezhTKvfg+U6S7BMIsw5RLDTK1uGjDfk8wQ8fD/6ReCSVPqb0W7
fhDfb6epmj7FPv9MfH9RxzScdHtza/js0OCsyp43iMl334nwgt5OACynLcC4FE2g
L2hx8cuTt/Wz2ZqB2j3JhfMqZ6nAdORKDQOO0vJy9kfxjzAclwPjKhzUOpfy10TB
6bxn8UUBTurHeewlBXgrsQxtO7f7VwynD1Ws2PCfPzu7+QfcA3ChMOU5t7DfcqMP
6UuMjQ67ZWSXTSUKLrkLeFiYsvzclQNqDKGCh2I99HuXHJJG2ytMmhCDp8GOiLqt
d4qWQ4D7AjcNhBkMGEtMIfjYeTzjUZmYhc1iP6WSZpebw7my+9v34BDk39lKmNvj
IKDTrvkBICQEU2ufgsF4ef76kzeCKo7xiVyfw4p7hdJJapn3aK7p3IPnAVVkf600
fPadXSjFSPZy9KvwYUc3ijGU7viGqeMQ2tXtesCSOHJqYbOMYUDjWyyDWcf0RfS8
YokE8/E=
=rIFO
-----END PGP SIGNATURE-----
Ron Murray
Feb 22, 2022, 8:10:03 PM2/22/22
to
After thinking about this a little more, I wondered whether the trust db may have been corrupted (even a "list-keys" took a long time, displaying messages about the trust db. Some Googling led me to the "--update-trustdb" for gpg. It took a while to run, but it seems to have fixed the problem.
You can probably close this bug.
Thanks,
.....Ron
--
Ron Murray <rj...@rjmx.net> PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761
0 new messages