tags 976361 moreinfo thanks
On Fri 04 Dec 2020 at 10:00:43 +0900, Tomoo Nomura wrote: > Package: cups > Version: 2.3.3op1-2 > Severity: important > > Dear Maintainer, > > When upgrading to 2.3.3op1-2, cups can not start with an error "Dependency > failed for CUPS Scheduler". > > here is a log; > > tom-lin@root:/etc/cups# journalctl -xe > ░░ Defined-By: systemd > ░░ Support: https://www.debian.org/support > ░░ > ░░ The unit cups.socket has entered the 'failed' state with result > 'start-limit-hit'. > Dec 02 19:32:29 tom-lin systemd[1]: Failed to listen on CUPS Scheduler. > ░░ Subject: A start job for unit cups.socket has failed > ░░ Defined-By: systemd > ░░ Support: https://www.debian.org/support > ░░ > ░░ A start job for unit cups.socket has finished with a failure. > ░░ > ░░ The job identifier is 4029 and the job result is failed. > Dec 02 19:32:29 tom-lin systemd[1]: Dependency failed for CUPS Scheduler. > ░░ Subject: A start job for unit cups.service has failed > ░░ Defined-By: systemd > ░░ Support: https://www.debian.org/support > ░░ > ░░ A start job for unit cups.service has finished with a failure. > ░░ > ░░ The job identifier is 3927 and the job result is dependency. > > After downgrading to 2.3.3-1, it works well. Thank you for your report, Tomoo. What is the behaviour of 2.3.3op2-7, the present unstable version? Regards, Brian.
