http://bugzilla.xfce.org/show_bug.cgi?id=6073
--- Comment #5 from Yves-Alexis Perez <[email protected]> 2010-09-16 07:39:12 UTC --- (In reply to comment #4) > (In reply to comment #3) > > (In reply to comment #2) > > > (In reply to comment #1) > > > > Hmm, the problem is that there isn't a good way to check that the auth > > > > sock is > > > > actually valid and isn't a stale env var left over from something else. > > > > > > Why is ssh-agent called from there in the first place? Shouldn't it be > > > another > > > service in /etc/xdg/autostart? > > > > autostart is too late in the startup process. It has to be a parent of > > xfce4-session so every child inherits the SSH_AUTH_SOCK and SSH_AGEN_PID > > envvar. > > Nope, GNOME starts the keyring through autostart, but of course you would have > to register Xfce as a session manager in dbus, and listen for when environment > variables are requested to be updated. > > http://live.gnome.org/SessionManagement/GnomeSession Yes, as you know xfce4-session doesn't support this. So my point still stands, autostart is too late in the process. > > The only other sane option is to make it a configuration directly in the > preferences, so that the user can choose between gnome compat's keyring, or > ssh-agent. That's already the case. If you select “Start gnome services at startup”, then gnome-keyring is run. In 4.6 it uses the old api though, so I doesn't work correctly. But there are patches to make it start correctly and replace ssh-agent. See http://bugzilla.xfce.org/show_bug.cgi?id=5912 -- Configure bugmail: http://bugzilla.xfce.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Xfce-bugs mailing list [email protected] http://foo-projects.org/mailman/listinfo/xfce-bugs
