GNOME Bugzilla – Bug 567634
gnome-keyring-daemon prints out errors in auth.log regarding inability to lookup some components
Last modified: 2009-01-13 20:51:59 UTC
+++ This bug was initially created as a clone of Bug #550756 +++ Please describe the problem: Trying to log in through gdm there are some error messages printed in the auth.log file regarding the inability of gnome-keyring-daemon to lookup keyring, ssh and pkcs11 components. This bug is a clone of the Bug #550756 but I think not exactly the same problem, because while get the same errors in the auth.log files, I'm still able to log in and use all the standard gnome applications. Steps to reproduce: 1. log into gnome environment using gdm Actual results: The gnome session is launched but it shows errors in the auth.log file Expected results: No errors in the auth.log Does this happen every time? Yes. Other information: These the errors in the auth.log [code] Jan 13 18:25:41 gosk8 gdm-binary[3936]: pam_unix(gdm:session): session opened for user yaya by (uid=0) Jan 13 18:25:41 gosk8 gdm-binary[3936]: 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 13 18:25:41 gosk8 gdm-binary[3936]: Autolaunch error: X11 initialization failed. Jan 13 18:25:41 gosk8 gdm-binary[3936]: )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 13 18:25:41 gosk8 gdm-binary[3936]: Autolaunch error: X11 initialization failed. Jan 13 18:25:41 gosk8 gdm-binary[3936]: )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 13 18:25:41 gosk8 gdm-binary[3936]: Autolaunch error: X11 initialization failed. Jan 13 18:25:41 gosk8 gdm-binary[3936]: ) [/code]
Thanks for the bug report. This bug is fixed in the latest development versions of gnome-keyring. The startup process now initializes those components later. The process is described here: http://live.gnome.org/GnomeKeyring/RunningDaemon This has not been backported to 2.24.x because it involves changes in gnome-session as well.