Skip to content

systemd-daemon-reload-user.hook fails to restart "job for user@0.service"

Description:

During regular upgrade with pacman -Syu on the TTY, pacman printed the following message:

[2025-02-09T16:42:02+0100] [ALPM] running '30-systemd-daemon-reload-user.hook'...
[2025-02-09T16:43:32+0100] [ALPM-SCRIPTLET] Job for user@0.service failed because the control process exited with error code.
[2025-02-09T16:43:32+0100] [ALPM-SCRIPTLET] See "systemctl status user@0.service" and "journalctl -xeu user@0.service" for details.

During the upgrade, systemd was update from 257.1-1 to 257.2-2. The upgrade process kept running and finished. The system rebooted fine and seems to work.

I'm aware that failed hooks can brick a system, so I'm going to be careful and report that.

Additional info:

  • package version(s): pacman 7.0.0.r6.gc685ae6-1, systemd 257.1-1 and systemd 257.2-2
  • config and/or log files: journalctl status user@0.service + journalctl -xu user@0.service

Steps to reproduce:

  1. Boot
  2. Switch to a TTY e.g. Ctrl+F4 # GDM Login Manager idles on TTY001, no user logged it
  3. Login as superuser
  4. # screen
  5. # pacman -Syu

Thanks

journalctl_xu_user_at_0_dot_service.txt

journalctl_status_user_at_0_dot_service.txt

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information