[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#969784: marked as done (cups: Cups fails to bind to a network ip address after system reboot)



Your message dated Sun, 30 May 2021 00:56:40 +0300
with message-id <20210529215640.GA18187@localhost>
and subject line Re: Bug#969784: cups: Cups fails to bind to a network ip address after system reboot
has caused the Debian Bug report #969784,
regarding cups: Cups fails to bind to a network ip address after system reboot
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.)


-- 
969784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969784
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: cups
Version: 2.2.10-6+deb10u3
Severity: important

Dear Maintainer,

Cups fails to bind to a network ip address after system reboot with
error "Unable to open listen socket for address XXX.XXX.XXX.XXX:631 -
Cannot assign requested address." If the services restarted manually
after reboot is works as usual. Similar issues was reported to redhat
while ago https://bugzilla.redhat.com/show_bug.cgi?id=970809 . To
workaround the issues I added "After=network.target" to cups.service.
With the dependency set it works with no problem. I suggest to add this
dependency by default.

-- System Information:
Debian Release: 10.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-10-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cups depends on:
ii  cups-client            2.2.10-6+deb10u3
ii  cups-common            2.2.10-6+deb10u3
ii  cups-core-drivers      2.2.10-6+deb10u3
ii  cups-daemon            2.2.10-6+deb10u3
ii  cups-filters           1.21.6-5
ii  cups-ppdc              2.2.10-6+deb10u3
ii  cups-server-common     2.2.10-6+deb10u3
ii  debconf [debconf-2.0]  1.5.71
ii  ghostscript            9.27~dfsg-2+deb10u4
ii  libavahi-client3       0.7-4+b1
ii  libavahi-common3       0.7-4+b1
ii  libc6                  2.28-10
ii  libcups2               2.2.10-6+deb10u3
ii  libcupsimage2          2.2.10-6+deb10u3
ii  libgcc1                1:8.3.0-6
ii  libstdc++6             8.3.0-6
ii  libusb-1.0-0           2:1.0.22-2
ii  poppler-utils          0.71.0-5
ii  procps                 2:3.3.15-2

Versions of packages cups recommends:
ii  avahi-daemon                     0.7-4+b1
ii  colord                           1.4.3-4
ii  cups-filters [ghostscript-cups]  1.21.6-5
ii  printer-driver-gutenprint        5.3.1-7

Versions of packages cups suggests:
ii  cups-bsd                                   2.2.10-6+deb10u3
pn  cups-pdf                                   <none>
ii  foomatic-db-compressed-ppds [foomatic-db]  20181217-2
ii  hplip                                      3.18.12+dfsg0-2
ii  printer-driver-hpcups                      3.18.12+dfsg0-2
pn  smbclient                                  <none>
ii  udev                                       241-7~deb10u4

-- debconf information:
  cupsys/backend: lpd, socket, usb, snmp, dnssd
  cupsys/raw-print: true

--- End Message ---
--- Begin Message ---
Version: 2.3.3op2-3

On Mon, Sep 07, 2020 at 10:28:19PM -0500, Pavel Shamis wrote:
>...
> Cups fails to bind to a network ip address after system reboot with
> error "Unable to open listen socket for address XXX.XXX.XXX.XXX:631 -
> Cannot assign requested address." If the services restarted manually
> after reboot is works as usual. Similar issues was reported to redhat
> while ago https://bugzilla.redhat.com/show_bug.cgi?id=970809 . To
> workaround the issues I added "After=network.target" to cups.service.
> With the dependency set it works with no problem. I suggest to add this
> dependency by default.

Thanks for the report.

This has been fixed upstream, and bullseye now has:
  After=network.target sssd.service ypbind.service nslcd.service

Unfortunately it is unlikely that this fix will be backported to buster.

cu
Adrian

--- End Message ---

Reply to: