Description of problem:
I wanted to give homed a try, now that it is in Fedora 32. User creation and logging in fail due to SELinux, but that can be worked around with `setenforce 0`. Also, logging in fails due to bug 1806949, this needs to be adjusted in PAM.
Afterwards, logging in generally works, but there is no valid group for the user
Version-Release number of selected component (if applicable):
How reproducible: Always
Steps to Reproduce:
1. Disable SELinux (setenforce 0) and adjust PAM config as in bug 1806949
2. Create user:
sudo homectl create test --real-name="Test User"
3. Check that NSS knows about it:
(prints "uid=60444(test) gid=60444 groups=60444" for me)
4. Log in:
su - test
step 3) group of user test does not have a name
step 4) there is a warning message
/usr/bin/id: cannot find name for group ID 60444
Expected results: There should be a proper default group for created users, with the same name.
Note that specifying explicit group memberships works:
$ sudo homectl create rtest --real-name="Test Admin User" -G wheel
$ id rtest
uid=60471(rtest) gid=60471 groups=60471,10(wheel)
I can log in as rtest and run sudo.
Fixed in rawhide now.
FEDORA-2020-645de57f2e has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-645de57f2e
systemd-245.2-1.fc32 has been pushed to the Fedora 32 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-645de57f2e
FEDORA-2020-645de57f2e has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.
For some reason, bodhi didn't close this bug.