You are not logged in.
I had gnome-keyring set up so that on login it unlocks the keyring and reads ssh keys (so that it acts as a ssh-agent), as described here: http://live.gnome.org/GnomeKeyring/Ssh and here http://live.gnome.org/GnomeKeyring/Pam
This was working great also outside gnome (for instance in xmonad and openbox), up to version 2.24.1. However, after update to 2.26.0-1 this stopped working. It is still OK in gnome, but in other environments (where the only gnome thing that is loaded is gnome-keyring-manager) it doesn't work correctly - it loads, but instead of creating both /tmp/keyring-<sth>/socket and /tmp/keyring-<sth>/socket.ssh it only created the first one, so no ssh support.
Can anyone help a bit with what has changed, or what could have gone wrong?
Thanks.
Offline
I'd also love to know a solution to this problem too. I've run into the same problem with gnome-keyring version 2.26.0-1 on my x86_64 box. I've tried to recompile the gnome-keyring package, but the problem still doesn't go away.
Offline
I've filed a bug report:
http://bugs.archlinux.org/task/13986
Offline
Actually now that the rest of gnome was updated, it sometimes doesn't work even in gnome - the login keyring is not unlocked.
Offline
I had the same problem with openbox. Using gdm fixed it.
Sic gorgiamus allos subjectatos nunc
Offline
I had the same problem with openbox. Using gdm fixed it.
Well if this is the only way to fix this then it sucks big time, since I don't want to run a huge login manager just to unlock the passwords
As far as ssh keys go, I switched to using pam_ssh.
EDIT: typos
Last edited by bender02 (2009-04-08 19:07:14)
Offline
I use NetworkManager in KDE4 and after upgrading gnome-keyring to 2.26 I had to enter my connection data every time. Probably is the same issue you're experiencing. I solved it by autostarting gnome-keyring. I'm not sure how to do it in openbox, but there should be some easy way.
Offline
Hi, I have the same problem with nm-applet under openbox.
With which command do you autostart gnome-keyring?
edit:
using GDM fix it, but I don't want to use a Login-Manager.
Last edited by SiD (2009-04-13 18:01:49)
Offline
abarilla wrote:I had the same problem with openbox. Using gdm fixed it.
Well if this is the only way to fix this then it sucks big time, since I don't want to run a huge login manager just to unlock the passwords
adding the content of /etc/X11/xinit/xinitrc.d/30-dbus to the ~/.xinitrc works for me.
# launches a session dbus instance
dbuslaunch="`which dbus-launch 2>/dev/null`"
if [ -n "$dbuslaunch" ] && [ -x "$dbuslaunch" ] && [ -z "$DBUS_SESSION_BUS_ADDRESS" ]; then
eval `$dbuslaunch --sh-syntax --exit-with-session`
fi
or sourcing the 30-dbus file in the ~/.xinitrc
source /etc/X11/xinit/xinitrc.d/30-dbus
or for all files in /etc/X11/xinit/xinitrc.d/
source /etc/X11/xinit/xinitrc.d/*
That's what GDM and KDM do.
Thanks to Jan de Groot for the hint.
Last edited by SiD (2009-04-14 09:58:46)
Offline
Thanks. It works!
Kamil
Offline
OK, so launching dbus from .xinitrc is not enough for me; /tmp/keyring-<whatever>/socket.ssh is still not created. How do you guys run the gnome-keyring-daemon? Using pam?
In gnome it works OK.
Offline
At least gnome-keyring 2.26 adds /etc/xdg/autostart/gnome-keyring-daemon.desktop file (which should make gnome-keyring autostart in xdg-compilant env) however this file also states:
OnlyShowIn=GNOME;
So no autostart outside GNOME.
As a workaround (I'm using kde + nm-applet) I've copied this file to ~/.config/autostart/gnome-keyring-daemon.desktop and removed that one line - now gnome-keyring autostarts even outside gnome.
Offline
At least gnome-keyring 2.26 adds /etc/xdg/autostart/gnome-keyring-daemon.desktop file (which should make gnome-keyring autostart in xdg-compilant env) however this file also states:
/etc/xdg/autostart/gnome-keyring-daemon.desktop wrote:OnlyShowIn=GNOME;
So no autostart outside GNOME.
As a workaround (I'm using kde + nm-applet) I've copied this file to ~/.config/autostart/gnome-keyring-daemon.desktop and removed that one line - now gnome-keyring autostarts even outside gnome.
Wow... adding that in makes the Gnome people look a little... Microsoft-ish. (I almost went with bitchy, but this works better since its a stronger epitaph.)
I keep getting distracted from my webserver project...
huh? oooh... shiny!
Offline
OK, so launching dbus from .xinitrc is not enough for me; /tmp/keyring-<whatever>/socket.ssh is still not created. How do you guys run the gnome-keyring-daemon? Using pam?
In gnome it works OK.
I only added starting dbus to .xinitrc, I didn't change or add anything else. I don't run gnome-keyring-deamon, nm-applet do this for me.
Offline
to have wifi key saved in a keyring file on fluxbox the solution is to launch nm-applet in ~/.fluxbox/startup as :
dbus_launch nm-applet --sm-disable &
the same if you like nautilus :
dbus_launch nautilus -n & (it gives you automount to sd card and usb key after a little change in policykit )
fluxbox needs to be executed with
exec ck-launch-session /usr/bin/fluxbox
Offline
-
Last edited by shrd (2009-04-19 22:15:20)
Offline
to have wifi key saved in a keyring file on fluxbox the solution is to launch nm-applet in ~/.fluxbox/startup as :
dbus_launch nm-applet --sm-disable &
the same if you like nautilus :
dbus_launch nautilus -n & (it gives you automount to sd card and usb key after a little change in policykit )
fluxbox needs to be executed with
exec ck-launch-session /usr/bin/fluxbox
hello,
thanks shrd, that solved my problems with fluxbox, nm-applet and wifi-keys in gnome-keyring, but:
i used
dbus-launch nm-applet --sm-disable &
exec ck-launch-session /usr/bin/fluxbox
so maybe it's just a typo, but might be helpful for non advanced users.
Offline
Why launch only nm-applet with a dbus session bus if you can have a shared dbus for all applications running on your desktop by sourcing the /etc/X11/xinitrc.d files?
Offline