Comment 31 for bug 384920

Excerpt from log during time when gnome-keyring-pam was installed, and prior to changing to knetworkmanager:

    kdm: :0: PAM adding faulty module: /lib/security/pam_gnome_keyring.so: 1
Time(s)
    kdm: :0: PAM unable to dlopen(/lib/security/pam_gnome_keyring.so):
/lib/security/pam_gnome_keyring.so: cannot open shared object file: No such
file or directory: 1 Time(s)
    kdm: :0: 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: Not running within active session)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: Not
running within active session)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: Not running within active session): 5 Time(s)