On 1 September 2010 07:31, Yves-Alexis Perez <cor...@debian.org> wrote
> I'm not using an older version, I'm using a more recent version :) > > ii gnome-keyring 2.30.3-1 GNOME keyring services (daemon and > tools) I'm using that too. Probably the version of Xfce you're using has the bug fixed > That's because of the OnlyShowIn line. I had changed that; it was becaus xfce doesn't check /usr/share/gnome/autostart. Copying the modified file in /etc/xdg/autostart made it appear and run at login, but gnome-keyring still doesn't work as a SSH agent. > Good point. So yes, either it's run as part of Xsession.d stuff (which > was not possible, aiui?) or xfce4-session runs it, and do it correctly, > for example using your patch. It used to be possible to start it in Xsession.d, but now it messes up the new DBus interface to gnome-keyring (it starts too early I seem to remember) > And I'm afraid it might break existing systems. For example, I have > gnome-keyring installed (and it manages password for stuff like > evolution) but I *dont* want to use it as ssh-agent. If I tune > xfce4-session to fix g-k-d start, will it force that behavior? I think the default is for gnome-keyring to be a ssh-agent; this can be changed via gconf (setting /apps/gnome-keyring/daemon-components/ssh to false). I realise that this is a bit inconvenient; but I'd say that if one uses many gnome applications will have to install gconf-editor anyway. (I don't like the fact that there isn't a simpler way to configure gnome-keyring if you're not using gnome, but this is what upstream has chosen and I don't think that relying on a bug in xfce4-session not to impose the ssh-agent to people would be a sensisble choice) Cheers, Luca -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org