Specifiying a bit more, I had already this issue with Debian 9 and I have it with Debian 11, always with XFCE as desktop manager and lightdm as display manager and I always introduce my password when start the session (tell me if I can give any other relevant detail to this issue).
As specified in the second of the links above, I have included the lines
Code: Select all
auth optional pam_gnome_keyring.so
session optional pam_gnome_keyring.so auto_start
Code: Select all
#%PAM-1.0
# Block login if they are globally disabled
auth requisite pam_nologin.so
# Load environment from /etc/environment and ~/.pam_environment
session required pam_env.so readenv=1
session required pam_env.so readenv=1 envfile=/etc/default/locale
@include common-auth
auth optional pam_gnome_keyring.so
@include common-account
# SELinux needs to be the first session rule. This ensures that any
# lingering context has been cleared. Without out this it is possible
# that a module could execute code in the wrong domain.
# When the module is present, "required" would be sufficient (When SELinux
# is disabled, this returns success.)
session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close
session required pam_limits.so
session required pam_loginuid.so
@include common-session
# SELinux needs to intervene at login time to ensure that the process
# starts in the proper default security context. Only sessions which are
# intended to run in the user's context should be run after this.
session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open
# When the module is present, "required" would be sufficient (When SELinux
# is disabled, this returns success.)
session optional pam_gnome_keyring.so auto_start
@include common-password
I didn't add the lines at the bottom, since there are no more "auth" lines in this file. I do not know if may have influence other "auth" lines in the files /etc/pam.d/lightdm-autologin and /etc/pam.d/lightdm-greeter.Note that the required added lines are at the bottom. If you put them above, after the other "auth" lines, say, then you'll be required to enter your password twice at login, which doesn't give the installation a smooth feel.
I have never seen the check box "do you want to automatically open the keyring on login?" mentioned in the link with that solution. The current behaviour is:
- If I press the Cancel button a number of times (not always the same, it may depend on the app), finally it closes, but next time I open the app I get the popup again
- If I write my session password and Unlock, then the popup does not appear any more the next times I open any of the apps with this behaviour at least for some hours. This is the case even if I shut down the computer and start again, for example as I did yesterday various times. However, today I got again this popup.