Your message dated Tue, 25 Apr 2017 17:55:18 -0400
with message-id <[email protected]>
and subject line Re: [pkg-gnupg-maint] Bug#851462: #851462 gpg-agent: a
gpg-agent is already running - not starting a new one
has caused the Debian Bug report #851462,
regarding gpg-agent: a gpg-agent is already running - not starting a new one
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
851462: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851462
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnupg-agent
Version: 2.1.17-4
Severity: important
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
I can do nothing to restart a new gpg-agent.
gpg-connect-agent /bye does nothing.
gpgconf --kill gpg-agent kills the agent. I can also manually kill it.
But, no matter what I do, gpg-agent --daemon always says:
gpg-agent: a gpg-agent is already running - not starting a new one
Even if really nothing remotely resembling a gpg-agent is running.
- -- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/lksh
Init: systemd (via /run/systemd/system)
Versions of packages gnupg-agent depends on:
ii libassuan0 2.4.3-2
ii libc6 2.24-8
ii libgcrypt20 1.7.5-3
ii libgpg-error0 1.26-1
ii libnpth0 1.3-1
ii libreadline7 7.0-1
ii pinentry-qt [pinentry] 1.0.0-1
Versions of packages gnupg-agent recommends:
ii gnupg 2.1.17-4
ii gpgsm 2.1.17-4
Versions of packages gnupg-agent suggests:
ii scdaemon 2.1.17-4
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iQJ4BAEBCABiFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAlh7NqwxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYxIcbmlrQG5h
dHVyYWxuZXQuZGUACgkQt5o8FqDE8pb7+BAAlsH442tiWmm7Y2otP421dDkfuVQK
10qs6zA93eKAWSWVxr6RU1OXQXa+r0ZluCeDMhYRw8s2rD7PygMi8VpkGFPZdE+n
TX5nnNpf5dw8ZrxAVzNwInqR8gHyPQiRcme5M7/cXjIMH9q16fK4aHIdOFidBuDD
3kHVrgMdVMHfWIPlqG5CP0tkQ/0+WwCDiz7a+mDdvrbbx7/QT+DQYWEJTh4SbVvy
aAtpDgfPcn0uySCHjNwbzBinkwJIz3pFMzDNrujCQZ2ljpUvCESV+7cyeCnXw2J4
RFzAcJ3lJOh1bFttbn86a/0eIevAdsbnVoZegW2/BOSnX2wrXV0O7O72KVzNDbgv
hvpb/wTXyA+FBI/zw18A5FYdf3W142D3QQ02Lo2SQ5pPgx/lRBzJ9u2vt6/fOKi1
Cic1Vcb6F3JWWEi/G/Kf7lripNg3MgXdQMbM8j5HRcOxELr2LPX6zbfjXLxdmZPp
lUG44p1yDIksLRxunRDKgYlY0Ge3UoEnx0CxFUlioyGKxUGlwpHrBbFJfAZPXGH3
Liolp82eVOoAeo/sq1dv9VB/tvOOsSCZE8id6gpDYpmBRalQB5CFy/xn53r8+GzX
LdJLuwR+hF/zTr9clLDf+KltzwBMmPnVKC3U2xcIVakUYaMlYQNi2n+vNv8zsvc5
uB/wgfKKnZQ7fsc=
=GMWP
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Hi Thomas--
I'm sorry, but i don't understand what you're trying to do here. I'm
re-closing this bug report (#851462) because it doesn't seem to be
related to the original report anyway, other than the string "gpg-agent
is already running" appearing in both of them.
I've asked you some questions below about what you're trying to do --
feel free to open a new bug report when answering them with a clearer
description (or to reopen this one again if you're sure this is the same
issue).
On Sat 2017-02-11 19:51:29 -0500, Thomas Dickey wrote:
> It's broken, and recently. I noticed this about a week ago.
>
> On my machines, I mostly use ssh to connect, and have a script which
> ties together gpg/ssh, using gpg-agent. I do this to get the keys
> for both in - package signing and network connections.
"to get the keys for both in" what?
> Here's the script:
>
> #!/bin/sh
> # $Id: wrapssh,v 1.9 2015/12/21 09:47:59 tom Exp $
> # vi:ts=4 sw=4
> # Initialize a subshell which will run ssh-agent, sets a variable that we can
> # use in the initialization to force an ssh-add prompt.
>
> unset SSH_AGENT_PID
> unset SSH_AUTH_SOCK
> unset SSH2_AUTH_SOCK
> unset SSH2_AGENT_PID
>
> if test -f /usr/bin/ssh-agent
> then
> SSH_ADD="passphrase"
> export SSH_ADD
> if test -f /usr/bin/gpg-agent && test -f /usr/bin/pinentry-curses
> then
> killall gpg-agent 2>/dev/null
> ssh-agent presign
> else
> ssh-agent $SHELL
> fi
> fi
why are you doing "killall gpg-agent" ? what do you hope to gain from that?
what is "presign" ? is that the script below?
> ...and it calls back with a new shell (tcsh in my case) to activate this:
>
> if ( $?GPG_ADD ) then
> setenv GPG_TTY `tty`
> unsetenv GPG_ADD
> echo "GPG-signing on $GPG_TTY ..."
> if ( -e /usr/bin/gpg ) then
> echo | gpg -s >/dev/null
> else
> echo | gpg2 -s >/dev/null
> endif
> echo "...GPG-signing"
> endif
> if ( $?SSH_ADD ) then
> echo "prompt $SSH_ADD"
> unsetenv SSH_ADD
> ssh-add
> endif
the trace (below) doesn't seem to trace into this stuff, does it? I
don't speak tsch fluently, and i don't understand what the SSH_ADD and
GPG_ADD environment variables are trying to do here. can you explain?
> With the newly broken package, I don't get a gpg-prompt.
> Ditto for ssh-prompt. What I get is this (turning on the trace):
>
> ~ (101) sh -x wrapssh
> + unset SSH_AGENT_PID
> + unset SSH_AUTH_SOCK
> + unset SSH2_AUTH_SOCK
> + unset SSH2_AGENT_PID
> + test -f /usr/bin/ssh-agent
> + SSH_ADD=passphrase
> + export SSH_ADD
> + test -f /usr/bin/gpg-agent
> + test -f /usr/bin/pinentry-curses
> + killall gpg-agent
> + ssh-agent presign
> gpg-agent[1791]: reading options from '/users/tom/.gnupg/gpg-agent.conf'
> gpg-agent[1791]: WARNING: "--write-env-file" is an obsolete option - it has
> no effect
> gpg-agent[1791]: enabled debug flags: cache ipc
> gpg-agent: a gpg-agent is already running - not starting a new one
> gpg-agent: secmem usage: 0/65536 bytes in 0 blocks
>
> By the way, I don't have a gpg-agent.conf (so that's another error).
Are you saying that /users/tom/.gnupg/gpg-agent.conf doesn't exist, but
gpg-agent is somehow claiming that it does?
Regards,
--dkg
signature.asc
Description: PGP signature
--- End Message ---
