Description of problem: pesign.service fails to start with the following error: 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. Version-Release number of selected component (if applicable): 0.112.30.fc32 How reproducible: test starting or enabling pesign.service...happens every time. Steps to Reproduce: 1. install pesign 2. try to start or enable service 3. note unit file error message Actual results: 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. Expected results: service enabled and started when passing the relevant commands to the unit file Additional info: fwupd tries to restart this service during update. by default pesign is not installed, if installed it's going to throw this error when the restart action is tried. There is a bug against fwupd already about trying to restart pesign.service during the update process.
This has been resolved by later updates to the components in question (fwupd and pesign)