Test in 50-ssh-agent for gnome-keyring ssh-agent via gconf, this works only for <=gnome-base/gnome-2.30.*
(see http://mail.gnome.org/archives/gnome-keyring-list/2010-November/msg00001.html )
-- /usr/portage/gnome-base/gdm/files/50-ssh-agent 2009-07-27 00:37:45.000000000 +0200
+++ /etc/X11/xinit/xinitrc.d/50-ssh-agent 2010-12-25 18:43:51.000000000 +0100
@@ -1,9 +1,14 @@
-# add ssh-agent if found
+# add ssh-agent if found and gnome-keyring ssh component is disabled
+gkr_ssh="`gconftool-2 --get /apps/gnome-keyring/daemon-components/ssh`"
-if [ -n "$sshagent" ] && [ -x "$sshagent" ] && [ -z "$SSH_AUTH_SOCK" ]; then
+if [ -n "$gkr" ] && [ -x "$gkr" ] && [ "$gkr_ssh" == "true" ]; then
+ echo "$0: using gnome-keyring, disable via gconf /apps/gnome-keyring/daemon-components/ssh "
+elif [ -n "$sshagent" ] && [ -x "$sshagent" ] && [ -z "$SSH_AUTH_SOCK" ]; then
command="$sshagent -- $command"
elif [ -z "$sshagent" ] ; then
echo "$0: ssh-agent not found!"
(Maybe look at ubuntus 90×11-common_ssh-agent file?)
Steps to Reproduce:
starting ssh-agent in ubuntu is controlled via the Xsession.options.
Maybe a einfo in gnome-base/gnome-keyring:
Disable /etc/X11/xinit/xinitrc.d/50-ssh-agent if you want gnome-keyring to take over ssh-agent function.
This is not how it is going to be done, but it is something I had on the back-burner as well.
(In reply to Gilles Dartiguelongue from comment #2)
> This is not how it is going to be done, but it is something I had on the
> back-burner as well.
Gilles, any news about this? (with much newer 3.8.x...) Thanks :)
In summary, that files don't belong to gnome-keyring neither gdm, they belong to ssh... I think there is another bug about this but I don't remember its summary or similar and I haven't found it :S