Hi Marga,
thanks for taking care of this bug. Unfortunately I have not much idea
about how all this session thingy works, but I try to give you
all the infos I have.
So I have
.gnupg/gpg-agent.conf
enable-ssh-support
processes:
2257 ? Ss 0:00 ssh-agent
2328 ? Ss 0:00 /usr/bin/gpg-agent --daemon
2540 ? Sl 0:00
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
.xsession-errors:
...
# the following is the output of the gpg-agent being started
SSH_AUTH_SOCK=/home/norbert/.gnupg/S.gpg-agent.ssh; export SSH_AUTH_SOCK;
...
# many dbus-update-activation-environment lines
...
# mind that the PID here is the ssh-agent, not the gpg agent
dbus-update-activation-environment: setting SSH_AGENT_PID=2257
...
dbus-update-activation-environment: setting
SSH_AUTH_SOCK=/home/norbert/.gnupg/S.gpg-agent.ssh
...
dbus-update-activation-environment: setting
GPG_AGENT_INFO=/home/norbert/.gnupg/S.gpg-agent:0:1
...
** (polkit-gnome-authentication-agent-1:2550): WARNING **: Unable to register
authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An
authentication agent already exists for the given subject
Cannot register authentication agent:
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent
already exists for the given subject
So it seems to me that he ssh-agent gots started too early (at all)
and overrides the gpg-agent ...but I really don't know.
Anything else I can provide?
All the best
Norbert
--
PREINING Norbert + TeX Live & Debian Developer + http://www.preining.info
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
