Can't enable python3-validity.service with systemctl

[mexiquin]

trafficstars

Hi there! Just for some quick background, I'm using a Thinkpad T480 with a "06cb:009a Synaptics, Inc. Metallica MIS" Touch Fingerprint Reader. The operating system is Arch and have python-validity installed from the AUR.

The support for this fingerprint reader is pretty dang good. Although, I noticed that this driver doesn't enable on its own when the system is rebooted/powered down/etc. I followed the troubleshoot guide and found that the systemd service was dead, so I run the command:

sudo systemctl enable --now python3-validity.service

and I receive the following output:

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.

The service does start correctly, it goes from "dead" to "running". But since it can't be enabled, the setting is not preserved after shutdown.