FS#19540 - [gnupg2] gpg-agent dies with “can't connect my own socket: Invalid value passed to IPC”
Attached to Project:
Arch Linux
Opened by Olivier Mehani (shtrom) - Thursday, 20 May 2010, 04:20 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 03 August 2010, 07:34 GMT
Opened by Olivier Mehani (shtrom) - Thursday, 20 May 2010, 04:20 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 03 August 2010, 07:34 GMT
|
Details
Description:
Since the last update of extra/gnupg2 (the binary date is Apr 24), gpg-agent dies a few tens of seconds after having been started. In debug mode, it reports the following. $ gpg-agent --daemon --use-standard-socket --write-env-file --default-cache-ttl 43200 --debug-level guru gpg-agent[6737]: enabled debug flags: command mpi crypto memory cache memstat hashing assuan gpg-agent[6737]: listening on socket `/home/omehani/.gnupg/S.gpg-agent' gpg-agent[7591]: enabled debug flags: command mpi crypto memory cache memstat hashing assuan gpg-agent[7591]: listening on socket `/home/omehani/.gnupg/S.gpg-agent' GPG_AGENT_INFO=/home/omehani/.gnupg/S.gpg-agent:7592:1; export GPG_AGENT_INFO; gpg-agent[7592]: gpg-agent (GnuPG) 2.0.15 started gpg-agent[7592]: can't connect my own socket: Invalid value passed to IPC gpg-agent[7592]: this process is useless - shutting down gpg-agent[7592]: gpg-agent (GnuPG) 2.0.15 stopped It seems to be linked to libassuan [0] [0] https://bugs.g10code.com/gnupg/issue1205 Additional info: * local/gnupg2 2.0.15-1 * local/libassuan 2.0.0-1 Steps to reproduce: * Install gnupg2-2.0.15-1 and libassuan-2.0.0-1; * Start gpg-agent with 'gpg-agent --daemon --use-standard-socket --write-env-file --default-cache-ttl 43200 --debug-level guru'; * Wait (no more than a couple of minutes). * Message “can't connect my own socket: Invalid value passed to IPC” is displayed, and the gpg-agent exits. Rebuilding both packages from ABS doesn't change anything. |
This task depends upon
imho i had a similar issue some time ago and i think creating configs new solved the issue for me.
Unfortunately, the problem still exists.