I have x11-wm/ion3-2004110 installed. However, I was unable to find a way to gracefully start ssh-agent (It seems that it has to be started BEFORE the wm, because only that way its environment-variables are inherited to the WM and all programs started in the WM), I had a look at other WM on how they did it. Gnome seems to start ssh-agendt from /etx/X11/Sessions/Gnome, so I fixed /etx/X11/Sessions/ion3 to do it, too. I don't know if this is the suggested method to do it, or if there are better ways... it now looks like this: ===== /etc/X11/Sessions/ion3 ===== #!/bin/sh command="/usr/bin/ion3" sshagent=`which ssh-agent` if [ -n "$sshagent" ] && [ -x "$sshagent" ] && [ -z "$SSH_AUTH_SOCK" ]; then command="$sshagent -- $command" fi $command ==================================
Hmmm, I'm not sure that the session is the right location for this. You can create custom .xsession file in your home directory and then choose a "Custom session" when you log in. Perhaps this would be a better place from which to launch ssh-agent? There's nothing about ion3 that requires ssh-agent, but if other window manager session do launch ssh-agent then perhaps ion3 should do the same. Please close this bug with "INVALID" (not a bug) if you consider this a reasonable solution, otherwise comment and leave it open. I'll probably post a message to gentoo-desktop asking for advice.
This may be a possibility, but IMO it should be handled equally for all WMs.
Mail posted to gentoo-desktop for feedback.
Hmmm, no opinion on gentoo-desktop. For the moment I want to keep ion3 "pure": the user can create a custom .xsession if he wants to launch ssh-agent (or gpg-agent, or esd, or whatever...) at startup. If other WMs start doing this then I'll update ion3 too. WONTFIX for the moment...
