I run my gnome session under ssh-agent. This seems to be fine: $ cat /home/ensonic/.xsession-errors /etc/X11/gdm/PreSession/Default: Registering your session with wtmp and utmp /etc/X11/gdm/PreSession/Default: running: /usr/X11R6/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/gdm/:0.Xservers" -h "" -l ":0" "ensonic" /etc/X11/gdm/Xsession: Beginning session setup... /etc/X11/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- gnome-session SESSION_MANAGER=local/fluffy:/tmp/.ICE-unix/7824 Initializing nautilus-open-terminal extension When the session comes up, it also presents the ssh-askpass (gtk2-ssh-askpass-0.3). After upgrading from gnome-2.12 to 2.14 the keys are not cached. That is doing ssh-add -l lists no keys. When I am doing ssh-add (and entering my pass-phrase) the key gets added. It seems that the upgrade broke the communication between the ssh-agent and the ssh-askpass frontend. Unfortunately I have no idea how to trace this down :(
Stefan, Can you still reproduce this bug? Thanks
I've checked where SSH_ASKPASS gets defined. It was under /etc/env.d/, so I re-run etc-update and that fixed it.
that was too quick :( Somehow the keys don't really get to the agent. Any idea what else I could check?
Hi, just tested gtk2-ssh-askpass here. With my pre-existing keychain setup (http://www.gentoo.org/doc/en/keychain-guide.xml), I just emerged the thing, env-update, relog into my gnome session and it works. I'm using gnome-2.18 but I don't see how environnement settings and ssh related stuff can be related to gnome. What does "env|egrep SSH" output ? is the SSH_AGENT_PID the same than the one launched by gnome-session ?
I close the bug, it seems to got fixed in the meantime.
