On a broken VirtualBox system, if I perform ;
systemctl stop cups.service
I got the following message : "Job for cups.service canceled."
Obviously, cups remain started with same PID, so no effect on the stop action requested.
Exactly as during the package upgrade.
On the other side, syslog shows : Stopping CUPS Scheduler.... Started CUPS Scheduler.
followed by a colord message.
I purge colord as a debug exercise but problem remain the same.
Note that if I do :
systemctl restart cups.service
that works.
So seems like the culprit of the upgrade failure is around the fact that the VirtualBox guess can't properly stop cups.service.
but why ?
- Eric
On a broken VirtualBox system, if I perform ;
systemctl stop cups.service
I got the following message : "Job for cups.service canceled."
Obviously, cups remain started with same PID, so no effect on the stop action requested.
Exactly as during the package upgrade.
On the other side, syslog shows :
Stopping CUPS Scheduler....
Started CUPS Scheduler.
followed by a colord message.
I purge colord as a debug exercise but problem remain the same.
Note that if I do :
systemctl restart cups.service
that works.
So seems like the culprit of the upgrade failure is around the fact that the VirtualBox guess can't properly stop cups.service.
but why ?
- Eric