You are not logged in.
Hi!
I have recently installed Arch Linux on my desktop PC, and I have realized that when I list all systemd services with systemctl --type=service, I get a failed service called user@974.service.
$ systemctl status user@974.service
● user@974.service - User Manager for UID 974
Loaded: loaded (/usr/lib/systemd/system/user@.service; static; vendor preset: disabled)
Active: failed (Result: protocol) since Wed 2019-09-18 01:07:42 KST; 9min ago
Docs: man:user@.service(5)
Process: 5137 ExecStart=/usr/lib/systemd/systemd --user (code=exited, status=224/PAM)
Main PID: 5137 (code=exited, status=224/PAM)
szept 18 01:07:42 nicemicro-home-pc systemd[1]: Starting User Manager for UID 974...
szept 18 01:07:42 nicemicro-home-pc systemd[5137]: pam_unix(systemd-user:account): account lightdm has expired (account expired)
szept 18 01:07:42 nicemicro-home-pc systemd[5137]: PAM failed: User account has expired
szept 18 01:07:42 nicemicro-home-pc systemd[5137]: user@974.service: Failed to set up PAM session: Operation not permitted
szept 18 01:07:42 nicemicro-home-pc systemd[5137]: user@974.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
szept 18 01:07:42 nicemicro-home-pc systemd[1]: user@974.service: Failed with result 'protocol'.
szept 18 01:07:42 nicemicro-home-pc systemd[1]: Failed to start User Manager for UID 974.
and the journal for the last boot concerning this service:
$ journalctl -b -u user@974.service
-- Logs begin at Sat 2019-09-14 18:58:24 KST, end at Wed 2019-09-18 01:21:39 KST. --
szept 17 22:18:39 nicemicro-home-pc systemd[1]: Starting User Manager for UID 974...
szept 17 22:18:39 nicemicro-home-pc systemd[474]: pam_unix(systemd-user:account): account lightdm has expired (account expired)
szept 17 22:18:39 nicemicro-home-pc systemd[474]: PAM failed: User account has expired
szept 17 22:18:39 nicemicro-home-pc systemd[474]: user@974.service: Failed to set up PAM session: Operation not permitted
szept 17 22:18:39 nicemicro-home-pc systemd[474]: user@974.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
szept 17 22:18:39 nicemicro-home-pc systemd[1]: user@974.service: Failed with result 'protocol'.
szept 17 22:18:39 nicemicro-home-pc systemd[1]: Failed to start User Manager for UID 974.
szept 18 01:07:42 nicemicro-home-pc systemd[1]: Starting User Manager for UID 974...
szept 18 01:07:42 nicemicro-home-pc systemd[5137]: pam_unix(systemd-user:account): account lightdm has expired (account expired)
szept 18 01:07:42 nicemicro-home-pc systemd[5137]: PAM failed: User account has expired
szept 18 01:07:42 nicemicro-home-pc systemd[5137]: user@974.service: Failed to set up PAM session: Operation not permitted
szept 18 01:07:42 nicemicro-home-pc systemd[5137]: user@974.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
szept 18 01:07:42 nicemicro-home-pc systemd[1]: user@974.service: Failed with result 'protocol'.
szept 18 01:07:42 nicemicro-home-pc systemd[1]: Failed to start User Manager for UID 974.
I have an other Arch install on a bootable USB stick, that doesn't produce this error. Why on earth is the light-dm user expired?
It doesn't cause any problems in the user experience that I have noticed, but the system has only been installed last weekend. I am kind of stuck with my searching on google, most of the stuff I find is related to the lightdm.service, but in my case, that's up and running with no problem.
The only way... is all the way!
Offline
Offline
Thanks for the fast reply!
I have submitted the issue to the lightdm github page (https://github.com/canonical/lightdm/issues/90), should I open a bug report on Arch Linux bug tracker, too?
The only way... is all the way!
Offline
lightdm.pam and lightdm-autologin.pam are provided by arch not from upstream lightdm so I do not believe it is an upstream lightdm issue.
It could be considered a packaging issue (it should also affect sddm and lxdm).
On your system you can disable password expiry for the lightdm user with:
chage -E -1 ldm
Offline
Thanks!
This definitely solved the issue with the login manager for lightdm. I'm still wondering though, why does the lightdm account need a this, especially considering the fact that my system worked without any noticeable problem when it couldn't run.
The only way... is all the way!
Offline