systemd-logind is not a valid systemd service [Solved]

zeroxoneafour · 2021-09-04 00:47:14

I'm not really new to Arch, but I don't know a more relevant place to ask this. So, I tried to reboot as a normal user (I have Polkit) and couldn't do it. I was asked to put my password into a prompt. Then I looked it up on the wiki and saw that loginctl didn't have an active session going. So I tried enabling it, and got -

The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.
 
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.

I'm quite sure I have never directly modified /usr/lib/systemd/system/systemd-logind.service, so I do not know where this error is coming from. On checking the file, it indeed does not have the tags asked for.

Yesterday I followed the instructions on the wiki for wiping all but essential packages to clear out my system. Rebooting without superuser was working fine before, and I didn't remove systemd, so nothing should have changed. Is something wrong with the systemd package, or is this just something wrong with my computer?

If this is something wrong with my computer, I would appreciate it if someone could upload an up-to-date systemd-logind service file.

Last edited by zeroxoneafour (2021-09-04 19:59:56)

jasonwryan · 2021-09-04 01:06:37

┌─[Shiv ~]
└─╼ systemctl list-unit-files --state=enabled | grep login                                                                                     
┌─[Shiv ~ 1]
└─╼

How do you start your session? If you have been running a graphical session as root, you have borked permissions on critical files in your $HOME.

Last edited by jasonwryan (2021-09-04 01:07:11)

zeroxoneafour · 2021-09-04 03:08:24

systemctl says systemd-logind is not enabled nor disabled, and is "static". I start my session using the ly DM, and alternately use sway and i3. I have the relevant permissions configured in Xorg, but possibly not Wayland. However, that doesn't matter because the problem is not with systemd-logind itself, but with the systemd service file it provides.

jasonwryan · 2021-09-04 03:21:42

Ly is breaking your session. Why do you think there is a problem with a service file that should not be managed by the user?

zeroxoneafour · 2021-09-04 20:00:39

I tried uninstalling ly and rebooting, and it works now. I think it's odd that the display manager changes the service file, but at least I know the problem.

Raynman · 2021-09-04 20:53:46

That would be odd, but jason is saying the problem is with the way Ly starts your session, not with the service file for logind, and you haven't given any reason for thinking that the service file has a problem.

You showed a informational message that you called an error. It says

Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/ or .requires/ directory.

and you found

zeroxoneafour wrote:

systemctl says systemd-logind is not enabled nor disabled, and is "static".

You can check:

$ systemctl show -p WantedBy,RequiredBy systemd-logind.service
RequiredBy=
WantedBy=multi-user.target

Arch Linux

#1 2021-09-04 00:47:14

systemd-logind is not a valid systemd service [Solved]

#2 2021-09-04 01:06:37

Re: systemd-logind is not a valid systemd service [Solved]

#3 2021-09-04 03:08:24

Re: systemd-logind is not a valid systemd service [Solved]

#4 2021-09-04 03:21:42

Re: systemd-logind is not a valid systemd service [Solved]

#5 2021-09-04 20:00:39

Re: systemd-logind is not a valid systemd service [Solved]

#6 2021-09-04 20:53:46

Re: systemd-logind is not a valid systemd service [Solved]

Board footer