Your message dated Sat, 19 Apr 2025 12:20:22 +0200
with message-id <[email protected]>
and subject line Re: Bug#847206: gpg-agent: can't connect to the agent: File
name too long
has caused the Debian Bug report #847206,
regarding gpg-agent: can't connect to the agent: File name too long
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.)
--
847206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847206
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnupg-agent
Version: 2.1.16-3
Severity: normal
Hey,
when i started to run the tests for messagelib within debian build dir
gpg-agent fails to start silently. Here the relevant part
GNUPGHOME=/build/kf5-messagelib-1co6xC/kf5-messagelib-16.04.3/obj-x86_64-linux-gnu/messagecore/autotests/gnupg_home
gpg-agent --daemon test
_pid=`echo GETINFO pid |
GNUPGHOME=/build/kf5-messagelib-1co6xC/kf5-messagelib-16.04.3/obj-x86_64-linux-gnu/messagecore/autotests/gnupg_home
gpg-connect-agent | grep 'D' | cut -d' ' -f2`
the output is:
gpg-agent[26537]: enabled debug flags: ipc
gpg-connect-agent: no running gpg-agent - starting '/usr/bin/gpg-agent'
gpg-connect-agent: waiting for the agent to come up ... (5s)
gpg-connect-agent: waiting for the agent to come up ... (4s)
gpg-connect-agent: waiting for the agent to come up ... (3s)
gpg-connect-agent: waiting for the agent to come up ... (2s)
gpg-connect-agent: waiting for the agent to come up ... (1s)
gpg-connect-agent: can't connect to the agent: File name too long
gpg-connect-agent: error sending standard options: No agent running
The test isn't started at all and no error message is logged, that
gpg-agent do not start, this is not nice. I only get the error, what is
wrong, when i use gpg-connect-agent.
Best Regards,
sandro
-- System Information:
Debian Release: stretch/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'),
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.8.0-2-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 /bin/dash
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.3-2
ii libgpg-error0 1.25-2
ii libnpth0 1.3-1
ii libreadline7 7.0-1
ii pinentry-qt [pinentry] 0.9.7-10~
Versions of packages gnupg-agent recommends:
ii gnupg 2.1.16-3
ii gpgsm 2.1.16-3
Versions of packages gnupg-agent suggests:
ii scdaemon 2.1.16-3
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.2.13-1
On 2016-12-06 Sandro Knauß <[email protected]> wrote:
> Package: gnupg-agent
> Version: 2.1.16-3
> Severity: normal
> Hey,
> when i started to run the tests for messagelib within debian build dir
> gpg-agent fails to start silently. Here the relevant part
> GNUPGHOME=/build/kf5-messagelib-1co6xC/kf5-messagelib-16.04.3/obj-x86_64-linux-gnu/messagecore/autotests/gnupg_home
> gpg-agent --daemon test
> _pid=`echo GETINFO pid |
> GNUPGHOME=/build/kf5-messagelib-1co6xC/kf5-messagelib-16.04.3/obj-x86_64-linux-gnu/messagecore/autotests/gnupg_home
> gpg-connect-agent | grep 'D' | cut -d' ' -f2`
> the output is:
> gpg-agent[26537]: enabled debug flags: ipc
> gpg-connect-agent: no running gpg-agent - starting '/usr/bin/gpg-agent'
> gpg-connect-agent: waiting for the agent to come up ... (5s)
> gpg-connect-agent: waiting for the agent to come up ... (4s)
> gpg-connect-agent: waiting for the agent to come up ... (3s)
> gpg-connect-agent: waiting for the agent to come up ... (2s)
> gpg-connect-agent: waiting for the agent to come up ... (1s)
> gpg-connect-agent: can't connect to the agent: File name too long
> gpg-connect-agent: error sending standard options: No agent running
> The test isn't started at all and no error message is logged, that
> gpg-agent do not start, this is not nice. I only get the error, what is
> wrong, when i use gpg-connect-agent.
Hello,
Newer versions of gpg do not use sockets in $GNUPGHOME anymore, quoting
Werner in <https://dev.gnupg.org/T4931>:
Since 2.2.13 we use
If a /run/user/$UID directory exists, that directory is now used
for IPC sockets instead of the GNUPGHOME directory. This fixes
problems with NFS and too long socket names and thus avoids the
need for redirection files.
gpgconf: New commands --create-socketdir and --remove-socketdir,
new option --homedir.
This works by using a hash of the directory name below
/run/user/$UID/gnupg as directory for the sockets.
With 2.1.20 we also added:
A socket directory for a non standard GNUGHOME is now created on
the fly under /run/user. Thus "gpgconf --create-socketdir" is now
optional. The use of "gpgconf --remove-socketdir" to clean up
obsolete socket directories is however recommended to avoid
cluttering /run/user with useless directories.
cu Andreas
--- End Message ---
