Bug#976361: marked as done (cups: Cups*-2.3.3op1-2 can not start)
Your message dated Sun, 9 Jan 2022 22:34:10 +0000
with message-id <09012022223238.da276c1d5823@desktop.copernicus.org.uk>
and subject line Re: Bug#976361: cups: Cups*-2.3.3op1-2 can not start
has caused the Debian Bug report #976361,
regarding cups: Cups*-2.3.3op1-2 can not start
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
976361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976361
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: cups: Cups*-2.3.3op1-2 can not start
- From: Tomoo Nomura <nomura@tmo.co.jp>
- Date: Fri, 04 Dec 2020 10:00:43 +0900
- Message-id: <160704364374.24506.13047524123274908701.reportbug@localhost>
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.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (101, 'testing'), (99, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.9.0-4-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages cups depends on:
hi cups-client 2.3.3op1-2
hi cups-common 2.3.3op1-2
hi cups-core-drivers 2.3.3op1-2
hi cups-daemon 2.3.3op1-2
ii cups-filters 1.28.5-1
hi cups-ppdc 2.3.3op1-2
hi cups-server-common 2.3.3op1-2
ii debconf [debconf-2.0] 1.5.74
ii ghostscript 9.52.1~dfsg-1
ii libavahi-client3 0.8-3
ii libavahi-common3 0.8-3
ii libc6 2.31-4
hi libcups2 2.3.3op1-2
ii libgcc-s1 10.2.0-19
ii libstdc++6 10.2.0-19
ii libusb-1.0-0 2:1.0.23-2
ii poppler-utils 20.09.0-3
ii procps 2:3.3.16-5
Versions of packages cups recommends:
ii avahi-daemon 0.8-3
ii colord 1.4.4-2
Versions of packages cups suggests:
hi cups-bsd 2.3.3op1-2
pn cups-pdf <none>
ii foomatic-db-compressed-ppds [foomatic-db] 20200820-1
ii smbclient 2:4.12.5+dfsg-3
ii udev 246.6-4
-- debconf information excluded
--- End Message ---
--- Begin Message ---
- To: 976361-done@bugs.debian.org
- Subject: Re: Bug#976361: cups: Cups*-2.3.3op1-2 can not start
- From: Brian Potkin <claremont102@gmail.com>
- Date: Sun, 9 Jan 2022 22:34:10 +0000
- Message-id: <09012022223238.da276c1d5823@desktop.copernicus.org.uk>
- In-reply-to: <160704364374.24506.13047524123274908701.reportbug@localhost>
- References: <160704364374.24506.13047524123274908701.reportbug@localhost>
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.
Dear Debian User,
Further information on your issue was requested some time ago but there hasn't been any response from you. Use of our limited, volunteer
supported resources is best served by not keeping open inactive bugs any
longer than desirable, especially in cases where the package concerned
is older than the current stable Debian version. Consequently, the
report is now being closed.
Regards,
Brian.
--- End Message ---
Reply to: