GNOME stores your SSH key passphrases in GNOME Keyring, which
(the login
keyring) is unlocked
with your login password by
pam_gnome_keyring
:
#%PAM-1.0
auth ...
auth ...
auth optional pam_gnome_keyring.so
session ...
session ...
session optional pam_gnome_keyring.so auto_start
However, your current setup will not work with this, as you are
starting a ssh-agent
at the last step,
overwriting any environment variables that
gnome-keyring may have set. Remove
ssh-agent
, and try adding this after all keyring
daemon processes:
eval $(gnome-keyring-daemon --start)
Keep in mind also that gnome-keyring-daemon
publishes a few environment variables over DBus which are then
read by gnome-shell
, which Awesome doesn't
do. That, and you are starting the DBus
session bus after all daemons have started, so
they may be unable to connect to your session at all.
One more thing: Many of the daemons must be started
inside a ConsoleKit session – the PolicyKit
authentication agent, for example. You'll have more luck if you
replace your entire ~/.xinitrc
script with:
exec ck-launch-session dbus-launch --exit-with-session ~/.xinitrc-session
then use ~/.xinitrc-session
to launch the rest of
GNOME.
You can go an easier way. Use the standard
ck-launch-session dbus-launch --exit-with-session
gnome-session
, and just tell GNOME session manager
to launch Awesome as the window manager.
Follow the official instructions.
Abridged form for GNOME 2:
mkdir -p ~/.local/share/applications/
cp /usr/share/applications/awesome.desktop ~/.local/share/applications/
cat >> ~/.local/share/applications/awesome.desktop
X-GNOME-WMName=Awesome
X-GNOME-WMSettingsModule=awesome
X-GNOME-Autostart-Phase=WindowManager;Panel
X-GNOME-Provides=windowmanager;panel
X-GNOME-Autostart-Notify=true
[Ctrl-D]
gconftool-2 --set /desktop/gnome/session/required_components/windowmanager --type string awesome