On mer., 2011-11-02 at 15:55 +0100, Thomas Pierson wrote: > Thanks for your response. > > > You've just hit an hard problem. xfce4-session will start the various > > gnome-keyring components correctly, but right now there's no way to pass > > their environment to something else. If you check a pstree you'll see > > the various desktop components are *not* children of those processes, so > > they can't inherit their environment. And yes, xfce4-session doesn't > > support environment passing, but I'm not even sure there's a common > > ground for that. > > Ok, so you say xfce4-session simply can't works with > gnome-kering-manager
It works just fine, depending on what you need. But yes, components needing to export environment variables can't be started by xfce4-session. > but why is there options about "gnome keyring" and > "ssh-agent" in the defaut list of "xfce session manager"? Because they ship a .desktop file for autostarting: dpkg -L gnome-keyring |grep autostart /etc/xdg/autostart /etc/xdg/autostart/gnome-keyring-pkcs11.desktop /etc/xdg/autostart/gnome-keyring-ssh.desktop /etc/xdg/autostart/gnome-keyring-secrets.desktop /etc/xdg/autostart/gnome-keyring-gpg.desktop > Is it a regression due to gnome3 upgrade? Not sure if it's GNOME3, but yes, at one point they were started using /etc/X11/Xsession.d stuff (and thus were started *before* xfce4-session which inherited they environment). > Should we forward the bug upstream to xfce or gnome? I don't think gnome people want to revert that change. There's already a bug in Xfce bugzilla about that: https://bugzilla.xfce.org/show_bug.cgi?id=8014 which indicates that enabling GNOME compatibility mode might help. Regards, -- Yves-Alexis
signature.asc
Description: This is a digitally signed message part