Details
-
Bug
-
Resolution: Fixed
-
P2: Important
-
None
-
dev
-
None
-
7523cd195 (dev)
Description
It seems that running systemctl stop once is not enough, the unit is activated by other means immediately.
And running systemctl disable is a noop according to what the command prints.
+ sudo systemctl stop packagekit + sudo systemctl disable packagekit 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 or disabled 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. + sudo fuser /usr/libexec/packagekitd + echo 'Waiting for PackageKit to finish...' Waiting for PackageKit to finish... + sleep 1 + sudo fuser /usr/libexec/packagekitd + echo 'Waiting for PackageKit to finish...' Waiting for PackageKit to finish... + sleep 1 + sudo fuser /usr/libexec/packagekitd + echo 'Waiting for PackageKit to finish...' Waiting for PackageKit to finish... + sleep 1