I need the help of a Desktop session genius (is there a gnome-session mailing list?).
- gvfs has an SSH module which uses OpenSSH. - OpenSSH checks for the presence of the SSH_AUTH_SOCK environment variable in order to integrate with SSH agents. - gnome-keyring-daemon is started from by /etc/xdg/autostart - gnome-keyring-daemon sets the SSH_AUTH_SOCK environment variable. - gvfsd is auto started by DBus. The end result of the above is that the SSH_AUTH_SOCK environment variable is not set in gvfsd. This has regressed [1] in GNOME 2.26.0 however this may be a race condition or heisenbug. I've received a suggestion to use 'UpdateActivationEnvironment'. Where is this mythical creature implemented and/or documented? Any interesting [2] ideas or suggestions on how to fix this? Are strange hacks inevitable because gnome-keyring deals with stuff like OpenSSH and GnuPG? Cheers, Stef [1] http://bugzilla.gnome.org/show_bug.cgi?id=577614 [2] Suggesting that OpenSSH should use DBus is not interesting, unless it comes with a plan of how to accomplish it. _______________________________________________ desktop-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/desktop-devel-list
