Setup fails with "no account named <user>" for directory (non-/etc/passwd) users
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- linux, rust
- Domain
- backend, operating-systems
Research direction
Start by tracing the first-run wizard's “Start engine” action and the “onboarding fix” path that reports the account lookup error. Check how that path resolves the current user and how the RPM build links the binary; the issue names no source files or tests. Done means setup starts for directory accounts that resolve through NSS, while the static RPM build remains supported.
Written by the indexing model from the issue text.
Description
Kiri version and system
Kiri 0.2.1 (RPM), Fedora 45, KDE Plasma (Wayland), x86_64. User account from Microsoft Entra ID via Himmelblau (NSS module), not listed in /etc/passwd.
What you did
- Installed Kiri 0.2.1 from the RPM.
- Opened the first-run setup wizard.
- Clicked "Start engine".
My user account is a directory account (Entra ID via Himmelblau), resolved through NSS rather than /etc/passwd.
What happened
The wizard shows "no account named <user>" and the engine never starts.
`kiri diag logs --errors`:
WARN ui action failed action="onboarding fix" error="no account named <user>" target=running
The account resolves fine through the system's NSS:
$ getent passwd <user>
<user>:x:<uid>:<gid>:<full name>:/home/<user>:/bin/bash
But the binary is fully static:
$ file /usr/bin/kiri
ELF 64-bit LSB pie executable, x86-64, static-pie linked, ...
A static binary can't load NSS modules, so its user lookup only sees /etc/passwd. Accounts from SSSD/LDAP/AD, winbind, Himmelblau (Entra ID) or systemd-homed won't be found.
What you expected instead
The engine starts and setup continues for users that resolve via NSS (getent passwd works).
Anything else
Adding the user to /etc/passwd by hand isn't a viable workaround: without a matching /etc/shadow entry, PAM's account checks fail and sudo breaks for that user.
Suggested fix, either:
- resolve users through NSS (e.g. dynamically link glibc for the lookup, or shell out to
getent passwd), or - use the numeric UID (getuid() / $SUDO_UID / $PKEXEC_UID) rather than looking the user up by name.
- Dominant language
- Rust
- Stars
- 7.5k
- Forks
- 329
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 105
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from libracoder/kiri
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
libracoder/kiri#364 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
libracoder/kiri#289 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 47/100
libracoder/kiri#365 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
libracoder/kiri#362 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 47/100
libracoder/kiri#359 ·
Maintainers usually reply within 1 day
Similar issues
-
benchmark-review
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
area:filesystem bug need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Captions panel does not offer to show an existing transcriptPossibly taken @thedavidweng claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
CapSoftware/Cap#4276 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
matrix-org/matrix-rust-sdk#7495 ·
Maintainers usually reply within 1 day