Comment 121 for bug 1642966

Revision history for this message
Eric Desrochers (slashd) wrote :

If I manually stop or stop/start cups.socket & cups.path, then cups.service is stopping successfully, and I can now proceed with the cups upgrade on a broken system.

With that being said, this could be a good workaround for Xenial users blocked by this situation.

systemctl stop cups.socket
systemctl stop cups.path

and then :
systemctl stop cups.service