systemctl enable gdm3 failes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
docker-systemctl-replacement (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
root@mu-
Synchronizing state of gdm3.service with SysV service script with /lib/systemd/
Executing: /lib/systemd/
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.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: systemctl (not installed)
ProcVersionSign
Uname: Linux 5.15.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: X-Cinnamon
Date: Sun Jun 12 21:03:54 2022
InstallationDate: Installed on 2022-06-01 (11 days ago)
InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LD_PRELOAD=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: docker-
UpgradeStatus: No upgrade log present (probably fresh install)