Your message dated Mon, 23 Jan 2017 21:43:02 -0500
with message-id <[email protected]>
and subject line Re: [pkg-gnupg-maint] Bug#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 ---
On Wed 2017-01-18 05:13:19 -0500, Dominik George wrote:
> Well, when I reported this bug, I wasn't aware that gpg-agent is now
> handled by systemd.
>
> In fact, it wasn't me who configured that, but it was your package.
>
> One day I could use gpg-agent for SSH and I could kill and start it, the
> next day it behaved oddly for no obvious reason.
>
> I might have missed the relevant NEWS, but even after reading up on it,
> I still find the behaviour a bit odd.
>
> But it probably isn't a bug.
Ok, closing this bug report. in the next upload to unstable (hopefully
today) i'll make sure that the NEWS in the gnupg-agent package explains
this change.
Regards,
--dkg
signature.asc
Description: PGP signature
--- End Message ---
