-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
systemd-sysusers fails to create users needed for nm-openvpn #89
Comments
I wanted to clearly that the issue is not just seen for nm-openvpn user, but most users/groups being created by systemd-sysusers.service. Steps I'm taking and were I'm seen the issue.
Edit: Adding logs and more context. Logs from journalctl --unit systemd-sysusers You can see that from boot it tries a few times but always exits and fails to crate all the users and groups.
Running a cat /etc/group you can see that all groups that systemd-sysusers tried to crate where not created.
Running a cat /etc/passwd you can see that all users that systemd-sysusers treod to create where not created.
|
I forgot to add if I cat /etc/gshadow you can see there a ton so f groups and users that are not in /etc/{passwd}{group}.
|
@rehashedsalt I have confirmed the issue is cause by the groups:
Once I removed them with I'll provide logs in a bit. |
Interestingly my experience is a bit different. I've been using the wayblue hyprland nvidia-open image for a while. My systemd-sysusers logs, with no adjustments:
However, I too have been having problems with groups after wayblue upgraded to Fedora 41. Relevant error logs:
I did manually copy some groups over
as suggested in the FAQ when I first set up the system on F40. Not sure if that is what made the difference |
(For the record, I did confirm these groups do in fact exist) |
So if you overlay a package that provides users or groups to bone stock f41:
If you overlay a package onto Wayblue 41 (I did this with
If we instead add a package to the bluebuild recipe into Wayblue 41:
Thus, we have two problems:
We've got two ways forward:
For bluebuild I'm definitely gonna need help on this one -- it's not my forte and I have zero confidence determining if this is an issue on our end, something inherent to the way images are built and distributed, or something on bluebuild's end. Also: this issue supersedes a workaround mentioned in #46. |
I've got a fix that implements the workaround drafted up, testing is going on in Discord. Once I know that it works on machines other than mine and my VMs, I'll draft a PR with a unit file and a couple dropins for unit dependencies. |
I confirmed this is working posted in Discord: message on discord |
No description provided.
The text was updated successfully, but these errors were encountered: