You are not logged in.

#1 2023-12-10 00:39:44

Salt7299
Member
Registered: 2023-09-28
Posts: 5

Systemd-sysusers.service not working after upgrade to systemd 255

I got this error, and systemd --user units were not diplaying correctly, couple of programs depending on systemd broke down iirc.

23:17:46.944 UTC systemd-sysusers.service Failed to copy permissions from /etc/group to /etc/.#groupb4a019b6cf9fae97: Invalid argument
23:18:00.874 UTC user@1000.service user@1000.service: Failed to adjust control group access: Invalid argument

Nothing was wrong with grpck. Downgrade to 254 fixed the problem.

As for suspected causes
1. some bug in systemd
2. Incompatibility with kernel. I have custom kernel and don't upgrade it very often bcs of compile time. Currently I have slimmed down arch zen 6.5.5 with some patches to fix support for my sound amplifiers (CS35L41 bug on Asus Zenbook UX3402VA)
3. Some very specific changes in systemd-sysusers made my config incompatible with systemd

Last edited by Salt7299 (2023-12-10 00:40:10)

Offline

#2 2023-12-12 03:32:17

horza
Member
Registered: 2023-12-12
Posts: 1

Re: Systemd-sysusers.service not working after upgrade to systemd 255

I've got this issue too, but only with linux-cachyos-tt-lto kernel. "Resolved" by using linux-cachyos-lto for now.

Offline

#3 2023-12-17 14:16:06

Salt7299
Member
Registered: 2023-09-28
Posts: 5

Re: Systemd-sysusers.service not working after upgrade to systemd 255

Can confirm, update to satanic linux-zen 6.6.6, fixed the problem. Idk what caused systemd 255 to chimpout like that. I used kernel config based on broken 6.5.5 for 6.6.6 kernel, just added new features. It leaves me just more confused, but I think I will leave it at that, I don't have time to debug this mess

Offline

#4 2024-01-05 21:41:50

dumblob
Member
Registered: 2013-08-08
Posts: 4
Website

Re: Systemd-sysusers.service not working after upgrade to systemd 255

Just chiming in that I had the exact same issue and it took me quite some time to figure out that the it is not a bug in systemd (yeah, I am still sceptical a bit about it due to its history etc.) nor agetty, PAM, or any other part of my system.

[ALPM] upgraded linux-cachyos (6.4.11-1 -> 6.6.9-1)

Now it all works again without touching anything in the system.

Quotes, strings, tags, and keywords to make this easier to find or discover by others
  1. Sound stopped working - that is how I noticed. Media players could not connect to pipewire as it could not be started due to systemd --user not running in the background due to some segfault in the background

  2. Manifested through errors & logs like:

Jan 03 18:59:14 mypc dbus-daemon[921]: [session uid=1000 pid=919] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=923 comm="systemctl --user import-environment DISPLAY XAUTHO")
Jan 03 18:59:14 mypc systemd-journald[334]: /var/log/journal/0b4c704d6ffb4fc09a7fafc5f705519f/user-1000.journal: Journal file uses a different sequence number ID, rotating.
Jan 03 18:59:14 mypc dbus-daemon[921]: [session uid=1000 pid=919] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1

Jan 03 18:59:14 mypc dbus-daemon[496]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.10' (uid=0 pid=950 comm="/usr/bin/sudo sh -s")
Jan 03 18:59:14 mypc dbus-daemon[496]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.

Offline

Board footer

Powered by FluxBB