Package: gnome-keyring
Version: 3.18.0-4
Followup-For: Bug #800617
It looks like the patch doesn't work either -- it's the exact same situation.
But there's another thing that can be helpful.
There's another bug (#796931) in debian concerning the gnupg-agent package.
When I first installed the sid version of that package, I was unable to access
my ssh keys at all. After switching to the testing version of the following
packages: gnupg-agent gnupg2 gpgsm scdaemon , the issue disappeared, so I was
using the testing version of the packages all the time.
When I noticed the problems with gnome-keyring, I didn't even realize that the
two things could be connected in some way. But it looks like they are.
First of all, I upgraded the packages in question. Then I did the trick
described in the aforementioned bug, which was to add some code to the
..bashrc/.zshrc file:
if [ "$PS1" ]; then
unset GPG_AGENT_INFO
unset SSH_AGENT_PID
if [ "${gnupg_SSH_AUTH_SOCK_by:-0}" -ne $$ ]; then
export SSH_AUTH_SOCK="${HOME}/.gnupg/S.gpg-agent.ssh"
fi
fi
export GPG_TTY=`tty`
After reboot, the message "The Secret Service was already initialized" in the
log disappeared. Running gajim and ssh command in the same session no longer
gives the lag when executing the second application. There's no error/messages
in the log, and my ssh keys work just fine.
