Mailing List Archive: looking for assistance tracking down why i don't have the ability to run gpg from the command line

looking for assistance tracking down why i don't have the ability to run gpg from the command line

Aug 14, 2019, 8:30 AM

Post #1 of 3 (214 views)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I'm running debian 10 buster (upgraded recently from stretch if that
matters) and i use KDE. I haven't yet tried to logout of my desktop
environment completely (and just use a native console), but I thought
I would see if any of you had any ideas. Here's the problem:

ni@quark:~/.ssh$ gpg --list-keys
gpg: checking the trustdb
gpg: waiting for lock (held by 22009) ...
gpg: waiting for lock (held by 22009) ...
gpg: waiting for lock (held by 22009) ...
^C
gpg: signal Interrupt caught ... exiting

ni@quark:~/.ssh$ ps aux | grep 22009
ni 7740 0.0 0.0 6076 892 pts/6 S+ 11:21 0:00 grep
22009
ni 22009 2.0 0.2 89404 78536 ? RL 02:51 10:30 gpg
- --batch --no-sk-comments --status-fd 104 --no-tty --charset utf8
- --enable-progress-filter --exit-on-status-write-error --display :0
- --logger-fd 108 --with-colons --list-keys --
4E2247974AA5A23A5C92BB4DBB8B3D7331A9367F
ni@quark:~/.ssh$ kill 22009
ni@quark:~/.ssh$ gpg --list-keys
gpg: checking the trustdb
gpg: waiting for lock (held by 28999) ...
gpg: waiting for lock (held by 28999) ...
gpg: waiting for lock (held by 28999) ...

as you can see, killing the offending process doesn't work (as it
respawns immediately)

The reason this is important to me right now is because I have a new
laptop and I'm trying to transfer my keys to it. I have an email from
this list sent by Robert J. Hansen on 9/14/2016 that has excellent
instructions (which I've used in the past for this purpose) but the
1st command in those instructions:

gpg --armor --export

dumps a lot of output to the command line but never "finishes" (and my
guess is that it's the same lock that's preventing that command from
completing).

thanks so very much in advance for your time,
~c

- --
Charlie Derr Director, Instructional Technology 413-528-7344
https://www.simons-rock.edu Bard College at Simon's Rock
Encryption key: http://hope.simons-rock.edu/~cderr/
Personal writing: https://medium.com/@cderr Pronouns: he or they
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEETiJHl0qlojpckrtNu4s9czGpNn8FAl1UKR4ACgkQu4s9czGp
Nn93/w/+MX6xS0bMETgq/dWUaIt8vzubE1z9HypapZDyxqFyObsoWJS0AEwLMmwx
VqEAxFgbGrWT18CP04dLP1L6KPqAI5FsPm9ge0uXYVYF8M5xluIy8NALGWSbwhTm
NZlAuPwnzMmNaR4jD2iVF5PuIzzQF8Cx446vZTdR6vrCFWL+0hTn7Orp8l1Rk/ym
LLGPUU4iSkRpmYXcQyIwvrxpvROSFr521NFoyr8YcwX7w208FV3spqmfvBSO+Jqm
aQMXowggR9O61YPmrmDT6eXFLnULhTUzbaB3GYT55rh4bkqZZrw9I/Poi2j8DxaI
6wfTQasm4Hi2onyF1AgSpv7/uu4KnrR+FrYQfdkU0peCG1AYEcB8VUREfEOdHsUp
ncVZtZsaFk7NXWPYt0ibdBZbI4uJM4NRAPvQGY4mAgKszZpBJPO7lYvaJIpJJ87C
U9CQ4pIXC2ivgQ2jv5/Ti1vvBfbCwuD+9fUBy8yNZqi13E8El+Jo6WG5KhKCqhet
kkgHOBM8EKPKMpWQIBSv1/mc+HE6NAVz6YPiy41emKSmU8cKwimfF/Zsm8eMsgGx
aL7xEL4WRsgMGJaccRlCcTjk1ETROjMOgaGxBaacxq9QPIN0wKZvmti8HhsZdGsR
8FTQzY7fCmxB2m4S7tSdnIJ88W2glzJmWeHDGCgfcBDU80B1sbY=
=u8iV
-----END PGP SIGNATURE-----

_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: looking for assistance tracking down why i don't have the ability to run gpg from the command line [ In reply to ]

david at gbenet

Aug 14, 2019, 7:42 PM

Post #2 of 3 (214 views)

Permalink

On 14/08/2019 16:30, charlie derr wrote:
> I'm running debian 10 buster (upgraded recently from stretch if that
> matters) and i use KDE. I haven't yet tried to logout of my desktop
> environment completely (and just use a native console), but I thought
> I would see if any of you had any ideas. Here's the problem:
>
> ni@quark:~/.ssh$ gpg --list-keys
> gpg: checking the trustdb
> gpg: waiting for lock (held by 22009) ...
> gpg: waiting for lock (held by 22009) ...
> gpg: waiting for lock (held by 22009) ...
> ^C
> gpg: signal Interrupt caught ... exiting
>
> ni@quark:~/.ssh$ ps aux | grep 22009
> ni 7740 0.0 0.0 6076 892 pts/6 S+ 11:21 0:00 grep
> 22009
> ni 22009 2.0 0.2 89404 78536 ? RL 02:51 10:30 gpg
> --batch --no-sk-comments --status-fd 104 --no-tty --charset utf8
> --enable-progress-filter --exit-on-status-write-error --display :0
> --logger-fd 108 --with-colons --list-keys --
> 4E2247974AA5A23A5C92BB4DBB8B3D7331A9367F
> ni@quark:~/.ssh$ kill 22009
> ni@quark:~/.ssh$ gpg --list-keys
> gpg: checking the trustdb
> gpg: waiting for lock (held by 28999) ...
> gpg: waiting for lock (held by 28999) ...
> gpg: waiting for lock (held by 28999) ...
>
> as you can see, killing the offending process doesn't work (as it
> respawns immediately)
>
> The reason this is important to me right now is because I have a new
> laptop and I'm trying to transfer my keys to it. I have an email from
> this list sent by Robert J. Hansen on 9/14/2016 that has excellent
> instructions (which I've used in the past for this purpose) but the
> 1st command in those instructions:
>
> gpg --armor --export
>
> dumps a lot of output to the command line but never "finishes" (and my
> guess is that it's the same lock that's preventing that command from
> completing).
>
> thanks so very much in advance for your time,
> ~c
>
>
> _______________________________________________
> Gnupg-users mailing list
> Gnupg-users@gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-users
>

Hello Charlie,

On Debian 10 busty - which I have now - you have "root" I simply log
into root open the home folder go to user name folder list hidden files
- then select the .gpg folder and copy that to a USB. You can do a
weekly backup to USB.

Then you can add it to whatever you want - but be in root to change the
ownership to whatever the users called.

when I do a --list-users t lists all my 186 keys :)

David

--
People Should Not Be Afraid Of Their Government - Their Government
Should Be Afraid Of The People - When Injustice Becomes Law, REBELLION
Becomes A DUTY! Join the Rebellion Today! The "Captain's B(L)og"
https://gbenet.com

Re: looking for assistance tracking down why i don't have the ability to run gpg from the command line [ In reply to ]

peter at digitalbrains

Aug 15, 2019, 3:43 AM

Post #3 of 3 (212 views)

Permalink

Hello,

> ni@quark:~/.ssh$ ps aux | grep 22009
> ni 7740 0.0 0.0 6076 892 pts/6 S+ 11:21 0:00 grep
> 22009
> ni 22009 2.0 0.2 89404 78536 ? RL 02:51 10:30 gpg
> --batch --no-sk-comments --status-fd 104 --no-tty --charset utf8
> --enable-progress-filter --exit-on-status-write-error --display :0
> --logger-fd 108 --with-colons --list-keys --
> 4E2247974AA5A23A5C92BB4DBB8B3D7331A9367F

That doesn't show which process is starting that gpg. I would start by
doing

$ ps fax | less

and then from within less type for instance

/22009<Enter>

which will search for the line containing that PID. Then you can see its
ancestry (the f option makes a -f-orest of parent/child relations).

There are more ways to investigate, but this seems a good start.

HTH,

Peter.

--
I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
You can send me encrypted mail if you want some privacy.
My key is available at <http://digitalbrains.com/2012/openpgp-key-peter>

Mailing List Archive

Attached Files:

Attached Files: