Hi there. I am using sway(fx), greetd and regret. Currently, when I log in, my keyring is not unlocking.
**NOTE - I solved it, but I am posting it here for others, as keyrings seem to come up all the time. **
CODE
Full file:
nixos/modules/desktops/sway/default.nix at main · bashfulrobot/nixos
Items of interest:
- default session
- services.gnome.gnome-keyring enabled
- security.pam.services.greetd.enableGnomeKeyring true
- security.pam.services.login.enableGnomeKeyring true
- adding export GNOME_KEYRING_CONTROL
- adding eval $(gnome-keyring-daemon --start
- (home-manager) services.gnome-keyring enable
I cannot figure out what I am missing. Usually, when searching, it seems mostly related to security.pam.services."name".enableGnomeKeyring
.
Now I was looking through the logs just now:
journalctl -b | egrep -i "keyring|pam"
### Seems critical
Jul 05 14:35:51 rembot greetd[5729]: gkr-pam: unable to locate daemon control file
Jul 05 14:35:51 rembot greetd[5729]: gkr-pam: stashed password to try later in open session
Jul 05 14:35:52 rembot greetd[4938]: pam_unix(greetd:session): session closed for user greeter
Jul 05 14:35:52 rembot greetd[5729]: pam_unix(greetd:session): session opened for user dustin(uid=1000) by (uid=0)
Jul 05 14:35:52 rembot (systemd)[5831]: pam_unix(systemd-user:session): session opened for user dustin(uid=1000) by (uid=0)
Jul 05 14:35:52 rembot greetd[5729]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
It looks like it is starting, but the unable to locate daemon control file
error stands out to me. But while searching around, I found that it does not seem to have much impact (according to other sources/threads).
But then there is:
Jul 05 14:36:08 rembot gcr-prompter[6698]: Gcr: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p0@:1.23
But I found a reference to this:
“So finally, after many tries, I was able to get the keyring to unlock itself after login. Had to delete all of the keyrings and let it automatically create one for itself and was able to replicate the change on another Arch install.”
Which I did. I can see in Seahorse that the keyring in unlocked. I can see my newly added added ssh keys.
So after all of that, why do I think something is still off? WHen I commit code to GitHub with either vccode, or git in my terminal, I am still prompted for my ssh key password.
Appreciate the help.