I'm testing SDDM and I've seen gnome-keyring is not unlocked when starting a session. It works fine with KDM Is only me, or someone else has experienced this problem? I remember to have touch the pam configuration of kdm in the past, but sddm has its stock config. I have this in /etc/pam.d/sddm auth [success=done ignore=ignore default=bad] pam_selinux_permit.so auth substack password-auth -auth optional pam_gnome_keyring.so -auth optional pam_mate_keyring.so auth include postlogin account required pam_nologin.so account include password-auth password include password-auth session required pam_selinux.so close session required pam_loginuid.so session optional pam_console.so -session optional pam_ck_connector.so session required pam_selinux.so open session optional pam_keyinit.so force revoke session required pam_namespace.so session include password-auth -session optional pam_gnome_keyring.so auto_start -session optional pam_mate_keyring.so auto_start session include postlogin And this in /etc/pam.d/kdm #%PAM-1.0 auth [success=done ignore=ignore default=bad] pam_selinux_permit.so auth required pam_env.so auth substack system-auth -auth optional pam_gnome_keyring.so auth include postlogin account required pam_nologin.so account include system-auth password include system-auth session required pam_selinux.so close session required pam_loginuid.so session optional pam_console.so -session optional pam_ck_connector.so session required pam_selinux.so open session optional pam_keyinit.so force revoke session required pam_namespace.so -session optional pam_gnome_keyring.so auto_start session include system-auth session include postlogin