I am seeing that today, its new. What does auth.log say?
Jan 23 14:59:48 k2 gdm[5733]: pam_unix(gdm:session): session opened for user slo by (uid=0) Jan 23 14:59:48 k2 gdm[5733]: pam_ck_connector(gdm:session): nox11 mode, ignoring PAM_TTY :0 Jan 23 14:59:48 k2 gdm[5733]: gnome-keyring-daemon: couldn't lookup keyring component setting: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: dbus-launch failed to autolaunch D-Bus session: No protocol specified Jan 23 14:59:48 k2 gdm[5733]: Autolaunch error: X11 initialization failed. Jan 23 14:59:48 k2 gdm[5733]: )gnome-keyring-daemon: couldn't lookup ssh component setting: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: dbus-launch failed to autolaunch D-Bus session: No protocol specified Jan 23 14:59:48 k2 gdm[5733]: Autolaunch error: X11 initialization failed. Jan 23 14:59:48 k2 gdm[5733]: )gnome-keyring-daemon: couldn't lookup pkcs11 component setting: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: dbus-launch failed to autolaunch D-Bus session: No protocol specified Jan 23 14:59:48 k2 gdm[5733]: Autolaunch error: X11 initialization failed. Jan 23 14:59:48 k2 gdm[5733]: ) Jan 23 14:59:48 k2 gnome-keyring-daemon[5963]: Couldn't unlock login keyring with provided password Jan 23 14:59:48 k2 gnome-keyring-daemon[5963]: Failed to unlock login on startup In this case the root cause appears to be the login didn't start everything, so now when I try and SSH to a remote box, whatever is meant to be doing its work in the background (letting me SSH to my laptop using a non-password-protected private key) isn't. -- ssh always asks to unlock private key with no password set https://bugs.launchpad.net/bugs/187127 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
