GNOME Bugzilla – Bug 550756
gnome-keyring-daemon blocks session startup on exported home directories
Last modified: 2009-03-11 13:34:16 UTC
Please describe the problem: When I try to login from GDM with a user from an LDAP directory with home directory on a mounted NFS export, the Gnome session is launched but it shows only the wallpaper, no panels, nothing else... Steps to reproduce: 1. mount NFS exported home directory (autofs via LDAP) 2. enter username and password on GDM login Actual results: The Gnome session is launched but it shows only the wallpaper, no panels, nothing else... Expected results: A normal start of a Gnome session, panels appear and the desktop become usable. Does this happen every time? Yes. Other information: The only error messages I found are in /var/log/auth.log. [code] $ lsb_release -rd Description: Ubuntu intrepid (development branch) Release: 8.10 $ apt-cache policy gnome-keyring gnome-keyring: Installed: 2.23.90-0ubuntu1 Candidate: 2.23.90-0ubuntu1 Version table: *** 2.23.90-0ubuntu1 0 500 http://packages.aldu.net intrepid/main Packages 100 /var/lib/dpkg/status $ tail /var/log/auth.log Aug 28 19:13:19 pc-1 gdm[6944]: pam_unix(gdm:session): session opened for user heruan by (uid=0) Aug 28 19:13:20 pc-1 gdm[6944]: 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 Aug 28 19:13:20 pc-1 gdm[6944]: Autolaunch error: X11 initialization failed. Aug 28 19:13:20 pc-1 gdm[6944]: )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 Aug 28 19:13:20 pc-1 gdm[6944]: Autolaunch error: X11 initialization failed. Aug 28 19:13:20 pc-1 gdm[6944]: )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 Aug 28 19:13:20 pc-1 gdm[6944]: Autolaunch error: X11 initialization failed. Aug 28 19:13:20 pc-1 gdm[6944]: ) [/code]
This bug persists on Ubuntu Jaunty Jackalope alpha 4.
I recently fixed a problem with the session hanging on startup. The fix is included in 2.25.92 or gnome-keyring from SVN. Does this fix the problem for you?
gnome-keyring-2.25.92 fixes the problem for me. Thanks.