User@962 service issue

smitropoulos · 2025-02-28 13:50:45

Hello there

I had to reinstall some time ago, and in a fresh system I am seeing this when running updates, as a post hook for pacman

:: Running post-transaction hooks...
(1/7) Reloading user manager configuration...
user@962.service is not active, cannot reload.
error: command failed to execute correctly

I have tried to find that “user” with UID 962, but there is nothing in the shadow file or anywhere else I have searched.

I am running out of ideas here, has anyone else encountered something similar?

seth · 2025-02-28 14:06:41

systemctl status user@962.service

smitropoulos · 2025-02-28 20:03:20

This is the output:

❯ systemctl status user@962.service
× user@962.service - User Manager for UID 962
     Loaded: loaded (/usr/lib/systemd/system/user@.service; static)
    Drop-In: /usr/lib/systemd/system/user@.service.d
             └─10-login-barrier.conf
     Active: failed (Result: exit-code) since Fri 2025-02-28 15:23:58 EET; 6h ago
 Invocation: 9151cbef5b0a46029580da725d578bef
       Docs: man:user@.service(5)
   Main PID: 1208 (code=exited, status=224/PAM)
   Mem peak: 3.5M
        CPU: 6ms

Feb 28 15:23:58 SMPC systemd[1]: Starting User Manager for UID 962...
Feb 28 15:23:58 SMPC (systemd)[1208]: pam_unix(systemd-user:account): account sddm has expired (account expired)
Feb 28 15:23:58 SMPC (systemd)[1208]: PAM failed: User account has expired
Feb 28 15:23:58 SMPC (systemd)[1208]: user@962.service: Failed to set up PAM session: Operation not permitted
Feb 28 15:23:58 SMPC (systemd)[1208]: user@962.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
Feb 28 15:23:58 SMPC systemd[1]: user@962.service: Main process exited, code=exited, status=224/PAM
Feb 28 15:23:58 SMPC systemd[1]: user@962.service: Failed with result 'exit-code'.
Feb 28 15:23:58 SMPC systemd[1]: Failed to start User Manager for UID 962.
Feb 28 15:46:35 SMPC systemd[1]: user@962.service: Unit cannot be reloaded because it is inactive.

seth · 2025-02-28 20:07:57

Do you (still) use SDDM?

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
grep -i sddm /etc/passwd

smitropoulos · 2025-02-28 20:10:47

Yes. I tried

 ❯ sudo usermod --expiredate= sddm

for now, as seen in https://bbs.archlinux.org/viewtopic.php … 2#p1866422.

seth · 2025-03-01 08:26:37

Seems the "error" is just noise because systemd creates deactivated users but also starts a service for it because sddm somehow "needs" (?) a session for its user?
Also see https://bbs.archlinux.org/viewtopic.php?id=249228 and https://bbs.archlinux.org/viewtopic.php?id=249037 and https://gitlab.archlinux.org/archlinux/ … -/issues/6
Supposed to be fixed, though?

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

smitropoulos · 2025-03-04 14:30:02

I think for now it should be done. Will post again if it's not

Arch Linux

#1 2025-02-28 13:50:45

User@962 service issue

#2 2025-02-28 14:06:41

Re: User@962 service issue

#3 2025-02-28 20:03:20

Re: User@962 service issue

#4 2025-02-28 20:07:57

Re: User@962 service issue

#5 2025-02-28 20:10:47

Re: User@962 service issue

#6 2025-03-01 08:26:37

Re: User@962 service issue

#7 2025-03-04 14:30:02

Re: User@962 service issue

Board footer