Skip to content
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

fix: default user name isn't necessarily the same as user attr name #204

Merged

Conversation

KoviRobi
Copy link
Contributor

Me with my weird system again, sorry.

@nzbr
Copy link
Member

nzbr commented Jan 28, 2023

@KoviRobi I have opened a PR against yours that adds tests for this KoviRobi#2

Add tests for changing username and diverging user attr and name
@SuperSandro2000
Copy link
Member

SuperSandro2000 commented Jan 29, 2023

I am actually doing the same so I am surprised that it works for me and not for you.

@@ -153,7 +156,7 @@ with lib; {
})
(mkIf cfg.nativeSystemd {
wsl.wslConf = {
user.default = cfg.defaultUser;
user.default = config.users.users.${cfg.defaultUser}.name;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah, probably because my user.users attr matches name.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changing the username has always worked fine, but having different username and attr hasn't

@nzbr nzbr merged commit 0467c67 into nix-community:main Jan 30, 2023
@nzbr nzbr added the bug Something isn't working label Feb 1, 2023
@nzbr nzbr changed the title Default user name isn't necessarily the same as user attr name fix: default user name isn't necessarily the same as user attr name Jul 28, 2023
@KoviRobi KoviRobi deleted the user-name-different-from-user-attr-name branch November 13, 2023 10:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants