-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow unlocking of keyring from greetd #246197
Comments
@luc65r, you are mentioned as the maintainer so I tought I ping you on this :) |
You can use |
I have had success with |
EDIT: Made a quick PR to fix this as it is literally just one line |
The PAM service `greetd` creates now autostarts GNOME Keyring when it is enabled via `services.gnome.gnome-keyring.enable`. Should cause a lot fewer headaches for people like me who didn't know why GNOME Keyring was complaining that it was never supplied with login details. Fixes NixOS#246197
The PAM service `greetd` creates now autostarts GNOME Keyring when it is enabled via `services.gnome.gnome-keyring.enable`. Should cause a lot fewer headaches for people like me who didn't know why GNOME Keyring was complaining that it was never supplied with login details. Fixes #246197
The PAM service `greetd` creates now autostarts GNOME Keyring when it is enabled via `services.gnome.gnome-keyring.enable`. Should cause a lot fewer headaches for people like me who didn't know why GNOME Keyring was complaining that it was never supplied with login details. Fixes NixOS#246197
Still cannot get this to work for the live of me. I'm using Hyprland with greetd but my default keyring remains locked on boot. My config hyprland.nix |
Both LightDM and GDM include the login module where a keyring can be unlocked, for example by setting
security.pam.services.login.enableGnomeKeyring = true;
.I suggest adding the following:
to
nixpkgs/nixos/modules/services/display-managers/greetd.nix
Line 59 in d3a6adc
and maybe hide them behind a boolean?
Maybe someone with more knowledge of the PAM system could give some feedback on this, as I am not sure if there could be negative or unforeseen consequences lurking.
The text was updated successfully, but these errors were encountered: