Hi all,
I'm running debian testing without a login manager, i3 as window manager. gnome-keyring & libpam-gnome-keyring packages are installed. There's Login keyring, set as default; password is the same as my user login password: https://i.imgur.com/IPSavEc.jpg
Keyring file is at ~/.local/share/keyrings/login.keyring, file header/start is:
Code: Select all
[keyring]
display-name=Login
ctime=0
mtime=1614101854
lock-on-idle=false
lock-after=false
Code: Select all
exec dbus-run-session i3
Code: Select all
dbus-update-activation-environment --systemd --all
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &
Code: Select all
auth optional pam_gnome_keyring.so
session optional pam_gnome_keyring.so auto_start
In my system it was started by systemd (/etc/systemd/user/graphical-session-pre.target.wants/gnome-keyring-daemon.service), so I disabled said service:
Code: Select all
systemctl --user mask gnome-keyring-daemon
Code: Select all
ps -ef | grep keyring
layr 3064 1 0 00:36 tty1 00:00:00 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets
How to debug this? Maybe someone running debian testing could share their approach?
/var/log/auth.log at the time of bootup & login, with those 2 lines commented out in pam.d/login. System boot was around minute 26, login around 28, and typed in keyring password around minute 29.
/var/log/auth.log at the time of bootup & login, with those 2 lines enabled in pam.d/login. System boot was around minute 58, login around 59, no prompt for keyring password. Note there's a line ("gkr-pam: gnome-keyring-daemon started properly and unlocked keyring") implying all's good, but no keyrings are listed by seahorse in this case: https://i.imgur.com/5DxQMSk.jpg
Just for transparency, here's my stackexchange tread, will keep both this thread and stackexchange updated.