Thanks. Actually I came to the same conclusion and my final solution is to wrap awesome in an awesome-after-gnome-keyring script. (Coming up with a single sh command was too much for me :-) ). I placed in Xsession.d a script just after the the startup command is determined (around 56) to do the substitution. I suppose .xsession would work too, I will try it later.
Just for the closure of it, the script 90x11-common_ssh-agent contains a check to see if $SSH2_AUTH_SOCK is set. I assume this is an oversight, because gnome-keyring-daemon sets this variable, but is started after 90x11. Thanks, and sorry for your trouble, Panayiotis On 07/12/2012 06:02 PM, Simon McVittie wrote: > On 11/07/12 17:42, Panayiotis Karabassis wrote: >> I wanted to have access to the gnome-keyring in my awesome-wm session. Hence >> I >> added "gnome-keyring-daemon --start" to my .xsessionrc. This however did not >> work (for example subversion would hang while accessing its key) because >> -apparently- gnome-keyring needs DBus to be running when the "--start" >> command >> is executed. > .xsessionrc isn't the right place to do this. I don't know where is, but > you're likely to run into problems with activated session services: > > * activated session services are child processes of the session > dbus-daemon > * so, activated session services inherit environment variables from > the session dbus-daemon > * most scripts in /etc/X11/Xsession.d set environment variables > * ... so if you start dbus-daemon too early, it will miss out on > environment variables that are set after it starts (see Launchpad > bugs 807614 and 809900) > >> Adding gnome-keyring --start to the $STARTUP variable also does not work, >> because certain application such as ssh-agent mistakenly think that this is a >> non-gnome-keyring session, and start themselves. > I would suggest doing whatever gnome-session does to get a > gnome-keyring. I think the equivalent is starting gnome-keyring just > before awesome, from your ~/.xsession (not .xsessionrc). > > Regards, > S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org