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
A mutable user described in 'configuration.nix' gets locked out if an older generation is booted once #38132
Comments
configuration.nix
gets locked out if an older generation is booted once
An additional detail: if, after rebooting into the previous generation, i recreate the user with the same password, then, after rebooting back into the latest generation, the user password is preserved. |
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly:
|
I marked this as stale due to inactivity. → More info |
still important to me |
I marked this as stale due to inactivity. → More info |
still important to me |
Issue description
I noticed that if i add an existing imperatively created user to
users.users
, and then boot once into an old generation, the user gets permanently locked out of its account, and i need to log in as a root to set again a password for that user. This is withmutableUsers = true
.Steps to reproduce
And rebuild:
nixos-rebuild boot
.Reboot and test that the new
test
user can log in.Reboot into the previous generation and observe that the user
test
has disappeared from the login menu (in LightDM, for example).Reboot back into the last generation and observe that the password for
test
user is not accepted anymore.Technical details
The text was updated successfully, but these errors were encountered: