Am Donnerstag, den 20.03.2008, 17:35 -0300 schrieb Gustavo Noronha Silva: > Hey, > > On Thu, 2008-03-20 at 00:39 +0100, Sebastian Dröge wrote: > > Ok, upstream said that gnome-keyring should be started by PAM or > > gnome-session to get ssh key, etc support. > > > > Could you check if gnome-keyring is started by gnome-session (or PAM via > > the gdm PAM config) for you? > > I see a gnome-keyring-daemon process, started with no arguments. I'm not > sure who started it. And, indeed, the SSH_AUTH_SOCK variable is defined > to the ssh-agent file, not the keyring file, in my session: > > $ ps aux | grep gnome-keyring-daemon > kov 3894 0.0 0.0 7076 1048 ? S 17:00 0:00 > /usr/bin/gnome-keyring-daemon > kov 4380 0.0 0.1 15372 2584 ? SL 17:03 0:00 > /usr/bin/gnome-keyring-daemon --foreground --components=keyring,ssh > > $ env | grep SSH > SSH_AGENT_PID=3883 > SSH_AUTH_SOCK=/tmp/ssh-dMJNye3835/agent.3835 > > My gdm config does seem to include stuff to start the keyring: > > # rgrep keyring /etc/pam.d/* > /etc/pam.d/gdm:auth optional pam_gnome_keyring.so > /etc/pam.d/gdm:session optional pam_gnome_keyring.so auto_start > > I'm not sure why it is not being able to set the variable in the > session, though. I guess seahorse might be stepping on its feet.
Hm, which version of gnome-session do you have? In general this doesn't make much sense at all... the pam module will start it with --login, so this one is missing here. Then gnome-session will start it if it's not started already, if it's started already it will care for the environment variables. And then it will be started by the service file only if it's not running at all yet but something tries to use it.
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
