Debian Bug report logs - #747073

[systemd] ListenStream=[::1]:631 makes socket fail if ipv6 module is not loaded

Reported by: BogDan Vatra <bogdan.vatra@kdab.com> Date: Mon, 5 May 2014 11:33:01 UTC Severity: normal Tags: jessie, moreinfo, sid Found in version cups/1.7.1-7 Fixed in version cups/1.7.5-7 Done: Didier Raboud <odyx@debian.org> Bug is archived. No further changes may be made.

Toggle useless messages

Report forwarded to debian-bugs-dist@lists.debian.org, Debian Printing Team <debian-printing@lists.debian.org> :

Bug#747073 ; Package cups-daemon . (Mon, 05 May 2014 11:33:06 GMT) (full text, mbox, link).

Acknowledgement sent to BogDan Vatra <bogdan.vatra@kdab.com> :

New Bug report received and forwarded. Copy sent to Debian Printing Team <debian-printing@lists.debian.org> . (Mon, 05 May 2014 11:33:06 GMT) (full text, mbox, link).

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: BogDan Vatra <bogdan.vatra@kdab.com> To: submit@bugs.debian.org Subject: [cups-daemon] Doesn't work with systemd Date: Mon, 05 May 2014 14:23:32 +0300

Package: cups-daemon Version: 1.7.2-3 Severity: grave Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up cups-daemon (1.7.2-3) ... A dependency job for cups.service failed. See 'journalctl -xn' for details. invoke-rc.d: initscript cups, action "start" failed. dpkg: error processing package cups-daemon (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of cups-core-drivers: cups-core-drivers depends on cups-daemon (>= 1.7.2-3); however: Package cups-daemon is not configured yet. dpkg: error processing package cups-core-drivers (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of cups: cups depends on cups-core-drivers (>= 1.7.2-3); however: Package cups-core-drivers is not configured yet. cups depends on cups-daemon (>= 1.7.2-3); however: Package cups-daemon is not configured yet. dpkg: error processing package cups (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of printer-driver-hpcups: printer-driver-hpcups depends on cups (>= 1.4.0) | cupsddk; however: Package cups is not configured yet. Package cupsddk is not installed. printer-driver-hpcups depends on cups; however: Package cups is not configured yet. dpkg: error processing package printer-driver-hpcups (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of hplip: hplip depends on printer-driver-hpcups (= 3.14.1-1); however: Package printer-driver-hpcups is not configured yet. hplip depends on cups (>= 1.1.20); however: Package cups is not configured yet. dpkg: error processing package hplip (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of printer-driver-postscript- hp: printer-driver-postscript-hp depends on hplip (>= 3.14.1-1); however: Package hplip is not configured yet. dpkg: error processing package printer-driver-postscript-hp (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of printer-driver-gutenprint: printer-driver-gutenprint depends on cups (>= 1.3.0); however: Package cups is not configured yet. dpkg: error processing package printer-driver-gutenprint (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: cups-daemon cups-core-drivers cups printer-driver-hpcups hplip printer-driver-postscript-hp printer-driver-gutenprint E: Sub-process /usr/bin/dpkg returned an error code (1) --- System information. --- Architecture: amd64 Kernel: Linux 3.14-1-amd64 Debian Release: jessie/sid 500 unstable www.deb-multimedia.org 500 unstable ftp.ro.debian.org 500 stable dl.google.com --- Package information. --- Depends (Version) | Installed =======================================-+-================ libavahi-client3 (>= 0.6.16) | libavahi-common3 (>= 0.6.16) | libc6 (>= 2.15) | libcups2 (= 1.7.2-3) | libcupsmime1 (>= 1.5.0) | libdbus-1-3 (>= 1.0.2) | libgnutls28 (>= 3.2.10-0) | libgssapi-krb5-2 (>= 1.10+dfsg~) | libpam0g (>= 0.99.7.1) | libpaper1 | libsystemd-daemon0 (>= 31) | init-system-helpers (>= 1.18~) | procps | lsb-base (>= 3) | ssl-cert (>= 1.0.11) | adduser | bc | Recommends (Version) | Installed ===============================-+-=============== colord | 1.0.6-1 cups-browsed | 1.0.53-1 avahi-daemon (>= 0.6.31-3~) | 0.6.31-4 Suggests (Version) | Installed ============================================-+-============= cups | 1.7.2-3 cups-bsd | cups-common (>= 1.7.2-3) | 1.7.2-3 cups-server-common (>= 1.7.2-3) | 1.7.2-3 cups-client (>= 1.7.2-3) | 1.7.2-3 cups-ppdc | 1.7.2-3 cups-filters | 1.0.53-1 poppler-utils (>= 0.12) | 0.24.5-3 ghostscript (>= 9.02~) | 9.05~dfsg-8.1 cups-filters (>= 1.0.42) | 1.0.53-1 OR foomatic-filters (>= 4.0) | foomatic-db-compressed-ppds | OR foomatic-db | printer-driver-gutenprint | 5.2.9-2 printer-driver-hpcups | 3.14.1-1 hplip | 3.14.1-1 cups-pdf | udev | 204-10 smbclient | 2:4.1.7+dfsg-2

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Printing Team <debian-printing@lists.debian.org> :

Bug#747073 ; Package cups-daemon . (Mon, 05 May 2014 12:03:11 GMT) (full text, mbox, link).

Acknowledgement sent to 747073@bugs.debian.org :

Extra info received and forwarded to list. Copy sent to Debian Printing Team <debian-printing@lists.debian.org> . (Mon, 05 May 2014 12:03:11 GMT) (full text, mbox, link).

Message #10 received at 747073@bugs.debian.org (full text, mbox, reply):

From: Simon McVittie <smcv@debian.org> To: BogDan Vatra <bogdan.vatra@kdab.com>, 747073@bugs.debian.org Subject: Re: Bug#747073: [cups-daemon] Doesn't work with systemd Date: Mon, 5 May 2014 13:00:53 +0100

retitle 747073 cups-daemon+systemd: A dependency job for cups.service failed tags 747073 + moreinfo thanks On Mon, 05 May 2014 at 14:23:32 +0300, BogDan Vatra wrote: > Setting up cups-daemon (1.7.2-3) ... > A dependency job for cups.service failed. See 'journalctl -xn' for details. > invoke-rc.d: initscript cups, action "start" failed. I expect the cups maintainers are going to need more information here. Please look in the journal (or syslog) to see what went wrong, and quote it on the bug. Useful commands might include "journalctl", "less /var/log/syslog", "journalctl -xn", "systemctl -a status cups.service", "systemctl list-units". cups works fine on my systemd laptop, so there must be some local state/configuration involved here, rather than a simple "doesn't work on systemd". The rest of the failures you quoted look like a cascade of failed dependencies from cups-daemon failing to configure. (I am not a cups maintainer, I just saw this bug on apt-listbugs and thought I'd get start the process of getting enough information that the cups maintainers can do something about it.) S

Changed Bug title to 'cups-daemon+systemd: A dependency job for cups.service failed' from '[cups-daemon] Doesn't work with systemd' Request was from Simon McVittie <smcv@debian.org> to control@bugs.debian.org . (Mon, 05 May 2014 12:03:18 GMT) (full text, mbox, link).

Added tag(s) moreinfo. Request was from Simon McVittie <smcv@debian.org> to control@bugs.debian.org . (Mon, 05 May 2014 12:03:19 GMT) (full text, mbox, link).

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Printing Team <debian-printing@lists.debian.org> :

Bug#747073 ; Package cups-daemon . (Mon, 05 May 2014 12:30:09 GMT) (full text, mbox, link).

Acknowledgement sent to BogDan Vatra <bogdan.vatra@kdab.com> :

Extra info received and forwarded to list. Copy sent to Debian Printing Team <debian-printing@lists.debian.org> . (Mon, 05 May 2014 12:30:09 GMT) (full text, mbox, link).

Message #19 received at 747073@bugs.debian.org (full text, mbox, reply):

From: BogDan Vatra <bogdan.vatra@kdab.com> To: 747073@bugs.debian.org Subject: Re: Bug#747073: [cups-daemon] Doesn't work with systemd Date: Mon, 05 May 2014 15:19:30 +0300

[..] > > I expect the cups maintainers are going to need more information here. > Please look in the journal (or syslog) to see what went wrong, and quote > it on the bug. > > Useful commands might include "journalctl", "less /var/log/syslog", > "journalctl -xn", "systemctl -a status cups.service", "systemctl > list-units". Here we go: journalctl: .... mai 05 15:07:25 zmeu sudo[2830]: bogdan : TTY=pts/3 ; PWD=/home/bogdan ; USER=root ; COMMAND=/bin/bash mai 05 15:07:25 zmeu sudo[2830]: pam_unix(sudo:session): session opened for user root by bogdan(uid=0) mai 05 15:07:37 zmeu systemd[1]: Reloading. mai 05 15:07:37 zmeu systemd[1]: Starting CUPS Printing Service Sockets. mai 05 15:07:37 zmeu systemd[1]: cups.socket failed to listen on sockets: Cannot assign requested address mai 05 15:07:37 zmeu systemd[1]: Failed to listen on CUPS Printing Service Sockets. mai 05 15:07:37 zmeu systemd[1]: Dependency failed for CUPS Printing Service. ============================================ less /var/log/syslog: ...... May 5 15:07:37 zmeu systemd[1]: Reloading. May 5 15:07:37 zmeu systemd[1]: Starting CUPS Printing Service Sockets. May 5 15:07:37 zmeu systemd[1]: cups.socket failed to listen on sockets: Cannot assign requested address May 5 15:07:37 zmeu systemd[1]: Failed to listen on CUPS Printing Service Sockets. May 5 15:07:37 zmeu systemd[1]: Dependency failed for CUPS Printing Service. ============================================ journalctl -xn: ..... May 05 15:07:25 zmeu sudo[2830]: bogdan : TTY=pts/3 ; PWD=/home/bogdan ; USER=root ; COMMAND=/bin/bash May 05 15:07:25 zmeu sudo[2830]: pam_unix(sudo:session): session opened for user root by bogdan(uid=0) May 05 15:07:37 zmeu systemd[1]: Reloading. May 05 15:07:37 zmeu systemd[1]: Starting CUPS Printing Service Sockets. -- Subject: Unit cups.socket has begun with start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit cups.socket has begun starting up. May 05 15:07:37 zmeu systemd[1]: cups.socket failed to listen on sockets: Cannot assign requested address May 05 15:07:37 zmeu systemd[1]: Failed to listen on CUPS Printing Service Sockets. -- Subject: Unit cups.socket has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d -- -- Unit cups.socket has failed. -- -- The result is failed. May 05 15:07:37 zmeu systemd[1]: Dependency failed for CUPS Printing Service. -- Subject: Unit cups.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d -- -- Unit cups.service has failed. -- -- The result is dependency. ============================================ systemctl -a status cups.service: cups.service - CUPS Printing Service Loaded: loaded (/lib/systemd/system/cups.service; enabled) Active: inactive (dead) Docs: man:cupsd(8) man:cupsd.conf(5) May 05 14:41:19 zmeu systemd[1]: Dependency failed for CUPS Printing Service. May 05 14:41:39 zmeu systemd[1]: Dependency failed for CUPS Printing Service. May 05 14:42:27 zmeu systemd[1]: Dependency failed for CUPS Printing Service. May 05 14:45:33 zmeu systemd[1]: Dependency failed for CUPS Printing Service. May 05 15:07:37 zmeu systemd[1]: Dependency failed for CUPS Printing Service. ============================================ systemctl list-units: UNIT LOAD ACTIVE SUB DESCRIPTION proc-sys-fs-binfmt_misc.automount loaded active running Arbitrary Executable File Formats File System Automount Poi sys-devices-pci0000:00-0000:00:16.3-tty-ttyS1.device loaded active plugged Lynx Point KT Controller sys-devices-pci0000:00-0000:00:19.0-net-eth0.device loaded active plugged Ethernet Connection I217-LM sys-devices-pci0000:00-0000:00:1b.0-sound-card0.device loaded active plugged Lynx Point High Definition Audio Controller sys-devices-pci0000...0:1c.1-0000:02:00.0-net-wlan0.device loaded active plugged Centrino Advanced-N 6235 AGN sys-devices-pci0000...1c.4-0000:05:00.1-sound-card1.device loaded active plugged GK107 HDMI Audio Controller sys-devices-pci0000...t0:0:0-0:0:0:0-block-sda-sda1.device loaded active plugged WDC_WD20EZRX-00D8PB0 sys-devices-pci0000...t0:0:0-0:0:0:0-block-sda-sda2.device loaded active plugged WDC_WD20EZRX-00D8PB0 sys-devices-pci0000...target0:0:0-0:0:0:0-block-sda.device loaded active plugged WDC_WD20EZRX-00D8PB0 sys-devices-pci0000...t1:0:0-1:0:0:0-block-sdb-sdb1.device loaded active plugged ST1000DM003-1CH162 sys-devices-pci0000...t1:0:0-1:0:0:0-block-sdb-sdb2.device loaded active plugged ST1000DM003-1CH162 sys-devices-pci0000...t1:0:0-1:0:0:0-block-sdb-sdb3.device loaded active plugged ST1000DM003-1CH162 sys-devices-pci0000...t1:0:0-1:0:0:0-block-sdb-sdb4.device loaded active plugged ST1000DM003-1CH162 sys-devices-pci0000...t1:0:0-1:0:0:0-block-sdb-sdb5.device loaded active plugged ST1000DM003-1CH162 sys-devices-pci0000...t1:0:0-1:0:0:0-block-sdb-sdb6.device loaded active plugged ST1000DM003-1CH162 sys-devices-pci0000...t1:0:0-1:0:0:0-block-sdb-sdb7.device loaded active plugged ST1000DM003-1CH162 sys-devices-pci0000...target1:0:0-1:0:0:0-block-sdb.device loaded active plugged ST1000DM003-1CH162 sys-devices-pci0000...target3:0:0-3:0:0:0-block-sr0.device loaded active plugged PLDS_DVD-RW_DH16ACSH sys-devices-platform-serial8250-tty-ttyS2.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS2 sys-devices-platform-serial8250-tty-ttyS3.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS3 sys-devices-pnp0-00:0a-tty-ttyS0.device loaded active plugged /sys/devices/pnp0/00:0a/tty/ttyS0 sys-devices-virtual-net-vmnet1.device loaded active plugged /sys/devices/virtual/net/vmnet1 sys-devices-virtual-net-vmnet8.device loaded active plugged /sys/devices/virtual/net/vmnet8 sys-module-fuse.device loaded active plugged /sys/module/fuse sys-subsystem-net-devices-eth0.device loaded active plugged Ethernet Connection I217-LM sys-subsystem-net-devices-vmnet1.device loaded active plugged /sys/subsystem/net/devices/vmnet1 sys-subsystem-net-devices-vmnet8.device loaded active plugged /sys/subsystem/net/devices/vmnet8 sys-subsystem-net-devices-wlan0.device loaded active plugged Centrino Advanced-N 6235 AGN -.mount loaded active mounted / dev-hugepages.mount loaded active mounted Huge Pages File System dev-mqueue.mount loaded active mounted POSIX Message Queue File System home.mount loaded active mounted /home mnt-sda1.mount loaded active mounted /mnt/sda1 proc-sys-fs-binfmt_misc.mount loaded active mounted Arbitrary Executable File Formats File System run-lock.mount loaded active mounted Lock Directory run-user.mount loaded active mounted User Runtime Directory run-vmblock\x2dfuse.mount loaded active mounted /run/vmblock-fuse sys-fs-fuse-connections.mount loaded active mounted FUSE Control File System sys-kernel-debug.mount loaded active mounted Debug File System systemd-ask-password-console.path loaded active waiting Dispatch Password Requests to Console Directory Watch systemd-ask-password-wall.path loaded active waiting Forward Password Requests to Wall Directory Watch acpid.service loaded active running ACPI event daemon atd.service loaded active running Deferred execution scheduler avahi-daemon.service loaded active running Avahi mDNS/DNS-SD Stack binfmt-support.service loaded active exited Enable support for additional executable binary formats bitlbee.service loaded active running LSB: Start and stop BitlBee IRC to other chat networks gate bootlogs.service loaded active exited LSB: Log file handling to be done during bootup. console-kit-daemon.service loaded active running Console Manager console-kit-log-system-start.service loaded active exited Console System Startup Logging console-setup.service loaded active exited LSB: Set console font and keymap cron.service loaded active running LSB: Regular background program processing daemon dbus.service loaded active running D-Bus System Message Bus getty@tty1.service loaded active running Getty on tty1 hdparm.service loaded active exited LSB: Tune IDE hard disks ifup@eth0.service loaded active exited ifup for eth0 ifup@vmnet1.service loaded active exited ifup for vmnet1 ifup@vmnet8.service loaded active exited ifup for vmnet8 ifup@wlan0.service loaded active exited ifup for wlan0 kbd.service loaded active exited LSB: Prepare console kdm.service loaded active running LSB: X display manager for KDE keyboard-setup.service loaded active exited LSB: Set preliminary keymap minissdpd.service loaded active running LSB: keep memory of all UPnP devices that announced themsel ModemManager.service loaded active running Modem Manager motd.service loaded active exited LSB: Create dynamic part of /etc/motd networking.service loaded active exited LSB: Raise network interfaces. NetworkManager.service loaded active running Network Manager nvidia-kernel.service loaded active exited LSB: create NVIDIA device nodes openvpn.service loaded active exited LSB: Openvpn VPN service qemu-system-x86.service loaded active exited LSB: QEMU KVM module loading script rc-local.service loaded active exited /etc/rc.local Compatibility rsyslog.service loaded active running System Logging Service saned.service loaded active exited LSB: SANE network scanner server ssh.service loaded active running OpenBSD Secure Shell server systemd-journald.service loaded active running Journal Service systemd-logind.service loaded active running Login Service systemd-modules-load.service loaded active exited Load Kernel Modules systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems systemd-sysctl.service loaded active exited Apply Kernel Variables systemd-tmpfiles-setup-dev.service loaded active exited Create static device nodes in /dev systemd-tmpfiles-setup.service loaded active exited Recreate Volatile Files and Directories systemd-udev-trigger.service loaded active exited udev Coldplug all Devices systemd-udevd.service loaded active running udev Kernel Device Manager systemd-user-sessions.service loaded active exited Permit User Sessions transmission-daemon.service loaded failed failed Transmission BitTorrent Daemon udev-finish.service loaded active exited Copy rules generated while the root was ro udisks2.service loaded active running Disk Manager upower.service loaded active running Daemon for power management vmamqpd.service loaded failed failed LSB: This service starts and stops vmamqpd vmware-USBArbitrator.service loaded active running LSB: This services starts and stops the USB Arbitrator. vmware.service loaded active running LSB: This service starts and stops VMware services acpid.socket loaded active running ACPID Listen Socket avahi-daemon.socket loaded active listening Avahi mDNS/DNS-SD Stack Activation Socket cups.socket loaded failed failed CUPS Printing Service Sockets dbus.socket loaded active running D-Bus System Message Bus Socket syslog.socket loaded active running Syslog Socket systemd-initctl.socket loaded active listening /dev/initctl Compatibility Named Pipe systemd-journald.socket loaded active running Journal Socket systemd-shutdownd.socket loaded active listening Delayed Shutdown Socket systemd-udevd-control.socket loaded active running udev Control Socket systemd-udevd-kernel.socket loaded active running udev Kernel Socket dev-sdb6.swap loaded active active /dev/sdb6 basic.target loaded active active Basic System cryptsetup.target loaded active active Encrypted Volumes getty.target loaded active active Login Prompts graphical.target loaded active active Graphical Interface local-fs-pre.target loaded active active Local File Systems (Pre) local-fs.target loaded active active Local File Systems multi-user.target loaded active active Multi-User System network.target loaded active active Network nss-lookup.target loaded active active Host and Network Name Lookups paths.target loaded active active Paths remote-fs-pre.target loaded active active Remote File Systems (Pre) remote-fs.target loaded active active Remote File Systems sockets.target loaded active active Sockets sound.target loaded active active Sound Card swap.target loaded active active Swap sysinit.target loaded active active System Initialization syslog.target loaded active active Syslog timers.target loaded active active Timers x-display-manager.target loaded active active X11 Display Manager systemd-tmpfiles-clean.timer loaded active waiting Daily Cleanup of Temporary Directories LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 121 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. >cups works fine on my systemd laptop, so there must be some > local > state/configuration involved here, rather than a simple "doesn't work on > systemd". > Well, cups worked perfectly for me before I SID replaced sysvinit with systemd. Because I was sure that some people will say "it works for me", I removed them, and I tried to install them again. The result is the same, so for me is just a simple "doesn't work on systemd". :) [...] > > (I am not a cups maintainer, I just saw this bug on apt-listbugs and > thought I'd get start the process of getting enough information that the > cups maintainers can do something about it.) > Thanks! BogDan.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Printing Team <debian-printing@lists.debian.org> :

Bug#747073 ; Package cups-daemon . (Mon, 05 May 2014 15:45:09 GMT) (full text, mbox, link).

Acknowledgement sent to "Didier 'OdyX' Raboud" <odyx@debian.org> :

Extra info received and forwarded to list. Copy sent to Debian Printing Team <debian-printing@lists.debian.org> . (Mon, 05 May 2014 15:45:09 GMT) (full text, mbox, link).

Message #24 received at 747073@bugs.debian.org (full text, mbox, reply):

From: "Didier 'OdyX' Raboud" <odyx@debian.org> To: BogDan Vatra <bogdan.vatra@kdab.com>, 747073@bugs.debian.org Subject: Re: Bug#747073: [cups-daemon] Doesn't work with systemd Date: Mon, 05 May 2014 17:43:45 +0200

Le lundi, 5 mai 2014, 15.19:30 BogDan Vatra a écrit : > > I expect the cups maintainers are going to need more information > > here. Please look in the journal (or syslog) to see what went > > wrong, and quote it on the bug. Yay, thanks for the initial response. > > Useful commands might include "journalctl", "less /var/log/syslog", > > "journalctl -xn", "systemctl -a status cups.service", "systemctl > > list-units". > > Here we go: > > journalctl: > .... > mai 05 15:07:25 zmeu sudo[2830]: bogdan : TTY=pts/3 ; PWD=/home/bogdan > ; USER=root ; COMMAND=/bin/bash > mai 05 15:07:25 zmeu sudo[2830]: pam_unix(sudo:session): session > opened for user root by bogdan(uid=0) > mai 05 15:07:37 zmeu systemd[1]: Reloading. > mai 05 15:07:37 zmeu systemd[1]: Starting CUPS Printing Service > Sockets. mai 05 15:07:37 zmeu systemd[1]: cups.socket failed to > listen on sockets: Cannot assign requested address Hmm. Can you attach the content of all files and symlinks in /etc/systemd/system/cups.socket.d ? Could you also attach the output of `systemctl show cups.socket` ? Do you happen to have a specific IPv6 setup on this machine? Kernel module unloaded or not built? > Well, cups worked perfectly for me before I SID replaced sysvinit with > systemd. Because I was sure that some people will say "it works for > me", I removed them, and I tried to install them again. The result is > the same, so for me is just a simple "doesn't work on systemd". :) Did you upgrade all your system to sid? What is the install status of cups-browsed? Thanks in advance, cheers, OdyX

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Printing Team <debian-printing@lists.debian.org> :

Bug#747073 ; Package cups-daemon . (Mon, 05 May 2014 15:51:04 GMT) (full text, mbox, link).

Acknowledgement sent to "Didier 'OdyX' Raboud" <odyx@debian.org> :

Extra info received and forwarded to list. Copy sent to Debian Printing Team <debian-printing@lists.debian.org> . (Mon, 05 May 2014 15:51:04 GMT) (full text, mbox, link).

Message #29 received at 747073@bugs.debian.org (full text, mbox, reply):

From: "Didier 'OdyX' Raboud" <odyx@debian.org> To: BogDan Vatra <bogdan.vatra@kdab.com> Cc: 747073@bugs.debian.org Subject: Re: Bug#747073: [cups-daemon] Doesn't work with systemd Date: Mon, 05 May 2014 17:46:58 +0200

Le lundi, 5 mai 2014, 17.43:45 Didier 'OdyX' Raboud a écrit : > Hmm. Can you attach the content of all files and symlinks in > /etc/systemd/system/cups.socket.d ? Please also attach the output of the following command: sudo netstat -lnptu | grep 631 Cheers, OdyX

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Printing Team <debian-printing@lists.debian.org> :

Bug#747073 ; Package cups-daemon . (Tue, 06 May 2014 07:12:04 GMT) (full text, mbox, link).

Acknowledgement sent to BogDan Vatra <bogdan.vatra@kdab.com> :

Extra info received and forwarded to list. Copy sent to Debian Printing Team <debian-printing@lists.debian.org> . (Tue, 06 May 2014 07:12:04 GMT) (full text, mbox, link).

Message #34 received at 747073@bugs.debian.org (full text, mbox, reply):

From: BogDan Vatra <bogdan.vatra@kdab.com> To: Didier 'OdyX' Raboud <odyx@debian.org> Cc: 747073@bugs.debian.org Subject: Re: Bug#747073: [cups-daemon] Doesn't work with systemd Date: Tue, 06 May 2014 10:09:04 +0300

On Monday 05 May 2014 17:43:45 Didier 'OdyX' Raboud wrote: > Le lundi, 5 mai 2014, 15.19:30 BogDan Vatra a écrit : > > > I expect the cups maintainers are going to need more information > > > here. Please look in the journal (or syslog) to see what went > > > wrong, and quote it on the bug. > > Yay, thanks for the initial response. > > > > Useful commands might include "journalctl", "less /var/log/syslog", > > > "journalctl -xn", "systemctl -a status cups.service", "systemctl > > > list-units". > > > > Here we go: > > > > journalctl: > > .... > > mai 05 15:07:25 zmeu sudo[2830]: bogdan : TTY=pts/3 ; PWD=/home/bogdan > > ; USER=root ; COMMAND=/bin/bash > > mai 05 15:07:25 zmeu sudo[2830]: pam_unix(sudo:session): session > > opened for user root by bogdan(uid=0) > > mai 05 15:07:37 zmeu systemd[1]: Reloading. > > mai 05 15:07:37 zmeu systemd[1]: Starting CUPS Printing Service > > Sockets. mai 05 15:07:37 zmeu systemd[1]: cups.socket failed to > > listen on sockets: Cannot assign requested address > > Hmm. Can you attach the content of all files and symlinks in > /etc/systemd/system/cups.socket.d ? > Check cups.socket.d.output.txt > Could you also attach the output of `systemctl show cups.socket` ? > Check systemctl_show_cups.socket_output.txt > Do you happen to have a specific IPv6 setup on this machine? Kernel > module unloaded or not built? > Yes, I disabled IPv6. # cat /etc/sysctl.d/disableipv6.conf net.ipv6.conf.all.disable_ipv6=1 It seems this is the reason why it doesn't work, I comment "ListenStream=[::1]:631" and it works fine. > > Well, cups worked perfectly for me before I SID replaced sysvinit with > > systemd. Because I was sure that some people will say "it works for > > me", I removed them, and I tried to install them again. The result is > > the same, so for me is just a simple "doesn't work on systemd". :) > > Did you upgrade all your system to sid? No, I didn't upgrade to sid, I upgrade my existing sid installation. > What is the install status of > cups-browsed? > Is working. Thanks.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Printing Team <debian-printing@lists.debian.org> :

Bug#747073 ; Package cups-daemon . (Tue, 06 May 2014 07:12:07 GMT) (full text, mbox, link).

Acknowledgement sent to BogDan Vatra <bogdan.vatra@kdab.com> :

Extra info received and forwarded to list. Copy sent to Debian Printing Team <debian-printing@lists.debian.org> . (Tue, 06 May 2014 07:12:08 GMT) (full text, mbox, link).

Message #39 received at 747073@bugs.debian.org (full text, mbox, reply):

From: BogDan Vatra <bogdan.vatra@kdab.com> To: Didier 'OdyX' Raboud <odyx@debian.org> Cc: 747073@bugs.debian.org Subject: Re: Bug#747073: [cups-daemon] Doesn't work with systemd Date: Tue, 06 May 2014 10:10:15 +0300

On Monday 05 May 2014 17:46:58 Didier 'OdyX' Raboud wrote: > Le lundi, 5 mai 2014, 17.43:45 Didier 'OdyX' Raboud a écrit : > > Hmm. Can you attach the content of all files and symlinks in > > /etc/systemd/system/cups.socket.d ? > > Please also attach the output of the following command: > > sudo netstat -lnptu | grep 631 > # netstat -lnptu | grep 631 tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 1/init udp 0 0 0.0.0.0:631 0.0.0.0:* 843/cups-browsed BogDan.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Printing Team <debian-printing@lists.debian.org> :

Bug#747073 ; Package cups-daemon . (Tue, 06 May 2014 07:24:05 GMT) (full text, mbox, link).

Acknowledgement sent to "Didier 'OdyX' Raboud" <odyx@debian.org> :

Extra info received and forwarded to list. Copy sent to Debian Printing Team <debian-printing@lists.debian.org> . (Tue, 06 May 2014 07:24:05 GMT) (full text, mbox, link).

Message #44 received at 747073@bugs.debian.org (full text, mbox, reply):

From: "Didier 'OdyX' Raboud" <odyx@debian.org> To: BogDan Vatra <bogdan.vatra@kdab.com> Cc: 747073@bugs.debian.org, systemd@packages.qa.debian.org Subject: Re: Bug#747073: [cups-daemon] Doesn't work with systemd Date: Tue, 06 May 2014 09:21:41 +0200

Control: reassign -1 systemd Control: retitle -1 [systemd] ListenStream=[::1]:631 makes socket fail if ipv6 module is not loaded Hi again BogDan, Le mardi, 6 mai 2014, 10.09:04 BogDan Vatra a écrit : > On Monday 05 May 2014 17:43:45 Didier 'OdyX' Raboud wrote: > > Do you happen to have a specific IPv6 setup on this machine? Kernel > > module unloaded or not built? > > Yes, I disabled IPv6. > # cat /etc/sysctl.d/disableipv6.conf > net.ipv6.conf.all.disable_ipv6=1 > > It seems this is the reason why it doesn't work, I comment > "ListenStream=[::1]:631" and it works fine. Given that I don't think it's CUPS's responsibility to check for ipv6 availability, I'm hereby reassigning this bug to systemd. systemd maintainers: I think Listen*=[::1]:$port stanzas shouldn't make the .socket-file loading fail if the ipv6 module is not loaded. It should certainly spit out a warning though. Cheers, OdyX

Bug reassigned from package 'cups-daemon' to 'systemd'. Request was from "Didier 'OdyX' Raboud" <odyx@debian.org> to 747073-submit@bugs.debian.org . (Tue, 06 May 2014 07:24:05 GMT) (full text, mbox, link).

No longer marked as found in versions cups/1.7.2-3. Request was from "Didier 'OdyX' Raboud" <odyx@debian.org> to 747073-submit@bugs.debian.org . (Tue, 06 May 2014 07:24:06 GMT) (full text, mbox, link).

Changed Bug title to '[systemd] ListenStream=[::1]:631 makes socket fail if ipv6 module is not loaded' from 'cups-daemon+systemd: A dependency job for cups.service failed' Request was from "Didier 'OdyX' Raboud" <odyx@debian.org> to 747073-submit@bugs.debian.org . (Tue, 06 May 2014 07:24:07 GMT) (full text, mbox, link).

Added tag(s) sid and jessie. Request was from Holger Levsen <holger@layer-acht.org> to control@bugs.debian.org . (Tue, 06 May 2014 22:03:10 GMT) (full text, mbox, link).

Severity set to 'normal' from 'grave' Request was from Michael Biebl <biebl@debian.org> to control@bugs.debian.org . (Wed, 07 May 2014 11:27:04 GMT) (full text, mbox, link).

Added indication that 747073 affects cups-daemon Request was from Didier Raboud <odyx@debian.org> to control@bugs.debian.org . (Sun, 03 Aug 2014 09:57:08 GMT) (full text, mbox, link).

Information forwarded to debian-bugs-dist@lists.debian.org, Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org> :

Bug#747073 ; Package systemd . (Sun, 03 Aug 2014 10:15:04 GMT) (full text, mbox, link).

Acknowledgement sent to md@Linux.IT (Marco d'Itri) :

Extra info received and forwarded to list. Copy sent to Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org> . (Sun, 03 Aug 2014 10:15:04 GMT) (full text, mbox, link).

Message #61 received at 747073@bugs.debian.org (full text, mbox, reply):

From: md@Linux.IT (Marco d'Itri) To: Didier 'OdyX' Raboud <odyx@debian.org>, 747073@bugs.debian.org Cc: BogDan Vatra <bogdan.vatra@kdab.com>, control@bugs.debian.org Subject: Re: Bug#747073: [cups-daemon] Doesn't work with systemd Date: Sun, 3 Aug 2014 12:11:58 +0200

reassign 747073 cups-daemon thanks On May 06, Didier 'OdyX' Raboud <odyx@debian.org> wrote: > Given that I don't think it's CUPS's responsibility to check for ipv6 > availability, I'm hereby reassigning this bug to systemd. Sure it is: the CUPS maintainer script is explicitly instructing systemd to open an IPv6 socket and systemd tries to do it. > systemd maintainers: I think Listen*=[::1]:$port stanzas shouldn't make > the .socket-file loading fail if the ipv6 module is not loaded. It should > certainly spit out a warning though. There is no magic "we do not care if it does not work" address family: if a unit is configured to open a socket but this fails then the unit must fail. -- ciao, Marco

Bug reassigned from package 'systemd' to 'cups-daemon'. Request was from md@Linux.IT (Marco d'Itri) to control@bugs.debian.org . (Sun, 03 Aug 2014 10:15:14 GMT) (full text, mbox, link).

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Printing Team <debian-printing@lists.debian.org> :

Bug#747073 ; Package cups-daemon . (Sun, 03 Aug 2014 12:09:11 GMT) (full text, mbox, link).

Acknowledgement sent to "Didier 'OdyX' Raboud" <odyx@debian.org> :

Extra info received and forwarded to list. Copy sent to Debian Printing Team <debian-printing@lists.debian.org> . (Sun, 03 Aug 2014 12:09:11 GMT) (full text, mbox, link).

Message #68 received at 747073@bugs.debian.org (full text, mbox, reply):

From: "Didier 'OdyX' Raboud" <odyx@debian.org> To: "Marco d'Itri" <md@linux.it>, Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org> Cc: 747073@bugs.debian.org Subject: Re: Bug#747073: [cups-daemon] Doesn't work with systemd Date: Sun, 03 Aug 2014 14:06:10 +0200

Hi Marco, hi all, Le dimanche, 3 août 2014, 12.11:58 Marco d'Itri a écrit : > > systemd maintainers: I think Listen*=[::1]:$port stanzas shouldn't > > make the .socket-file loading fail if the ipv6 module is not > > loaded. It should certainly spit out a warning though. > > There is no magic "we do not care if it does not work" address family: > if a unit is configured to open a socket but this fails then the unit > must fail. Fair enough. Assuming there's no good way to make this work within systemd, I see three ways forward to fix this in cups: a) declare that ipv6 is mandatory these days, document this in README.Debian, let users cope with it. Pros: it works for most, ipv6 is coming anyway Cons: changes done through cups would break the user override every time. b) Detect whether there's a local ipv6 address both in the cups-daemon.preinst and in the cups code through cupsd-write-systemd-Port.patch. Pros: would work for everyone Cons: wouldn't make cups work over ipv6 if the latter is enabled after cups is installed; more fault-potential os-specific code. c) Replace address-based ListenStream stanzas with a combination of BindIPv6Only and FreeBind to configure systemd to bind only local or all available interfaces. The problem with that is that CUPS does address-based checking to verify that its bound addresses are really local. That could be patched out or corrected though. Pros: Probably the cleanest solution Cons: Needs good C-fu which I'm not sure to have Will imply extensive testing to fix a setup that currently works for most cases. No idea if this works as I think it should. The current setup took quite some intensive iterations to work as it currently does; it's only drawback is that it fails to give proper feedback to users who have disabled ipv6 for some reason. I'm currently leaning towards either leaving this bug as a documentation trace (+wontfix) or tackling the c)-idea above but would welcome feedback from systemd maintainers on whether this has a chance to actually work. Cheers, OdyX

Marked as found in versions cups/1.7.1-7. Request was from Didier Raboud <odyx@debian.org> to control@bugs.debian.org . (Sun, 03 Aug 2014 12:15:04 GMT) (full text, mbox, link).

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Printing Team <debian-printing@lists.debian.org> :

Bug#747073 ; Package cups-daemon . (Sun, 03 Aug 2014 13:12:09 GMT) (full text, mbox, link).

Acknowledgement sent to Marco d'Itri <md@linux.it> :

Extra info received and forwarded to list. Copy sent to Debian Printing Team <debian-printing@lists.debian.org> . (Sun, 03 Aug 2014 13:12:09 GMT) (full text, mbox, link).

Message #75 received at 747073@bugs.debian.org (full text, mbox, reply):

From: Marco d'Itri <md@linux.it> To: Didier 'OdyX' Raboud <odyx@debian.org> Cc: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>, 747073@bugs.debian.org Subject: Re: Bug#747073: [cups-daemon] Doesn't work with systemd Date: Sun, 3 Aug 2014 14:31:52 +0200

On Aug 03, Didier 'OdyX' Raboud <odyx@debian.org> wrote: > a) declare that ipv6 is mandatory these days, document this in > README.Debian, let users cope with it. I really see no point in supporting systemd with no ipv6 nowadays. -- ciao, Marco

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Printing Team <debian-printing@lists.debian.org> :

Bug#747073 ; Package cups-daemon . (Sun, 03 Aug 2014 23:33:05 GMT) (full text, mbox, link).

Acknowledgement sent to Brian Potkin <claremont102@gmail.com> :

Extra info received and forwarded to list. Copy sent to Debian Printing Team <debian-printing@lists.debian.org> . (Sun, 03 Aug 2014 23:33:05 GMT) (full text, mbox, link).

Message #80 received at 747073@bugs.debian.org (full text, mbox, reply):

From: Brian Potkin <claremont102@gmail.com> To: Didier 'OdyX' Raboud <odyx@debian.org>, 747073@bugs.debian.org Cc: Marco d'Itri <md@linux.it>, Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>, BogDan Vatra <bogdan.vatra@kdab.com> Subject: Re: Bug#747073: [cups-daemon] Doesn't work with systemd Date: Mon, 4 Aug 2014 00:24:22 +0100

On Sun 03 Aug 2014 at 14:06:10 +0200, Didier 'OdyX' Raboud wrote: > Le dimanche, 3 août 2014, 12.11:58 Marco d'Itri a écrit : > > > systemd maintainers: I think Listen*=[::1]:$port stanzas shouldn't > > > make the .socket-file loading fail if the ipv6 module is not > > > loaded. It should certainly spit out a warning though. > > > > There is no magic "we do not care if it does not work" address family: > > if a unit is configured to open a socket but this fails then the unit > > must fail. > > Fair enough. > > Assuming there's no good way to make this work within systemd, I see > three ways forward to fix this in cups: > > a) declare that ipv6 is mandatory these days, document this in > README.Debian, let users cope with it. > Pros: it works for most, ipv6 is coming anyway > Cons: changes done through cups would break the user override every > time. [Snip] > The current setup took quite some intensive iterations to work as it > currently does; it's only drawback is that it fails to give proper > feedback to users who have disabled ipv6 for some reason. > > I'm currently leaning towards either leaving this bug as a documentation > trace (+wontfix) or tackling the c)-idea above but would welcome > feedback from systemd maintainers on whether this has a chance to > actually work. Debian set the goal of supporting IPv6 across the distribution and I believe it is now mainly complete, so it seems to me that regarding it as an integral part or default for the distribution is fair and not out of place. Users who for whatever reason turn it off should not have an expectation of significant work being done to meet their situation. I would suggest your documentation idea is the path to take. Proof-reading is available on request. :) Regards, Brian.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Printing Team <debian-printing@lists.debian.org> :

Bug#747073 ; Package cups-daemon . (Thu, 25 Sep 2014 20:27:14 GMT) (full text, mbox, link).

Acknowledgement sent to Didier 'OdyX' Raboud <odyx@debian.org> :

Extra info received and forwarded to list. Copy sent to Debian Printing Team <debian-printing@lists.debian.org> . (Thu, 25 Sep 2014 20:27:14 GMT) (full text, mbox, link).

Message #85 received at 747073@bugs.debian.org (full text, mbox, reply):

From: Didier 'OdyX' Raboud <odyx@debian.org> To: 747073@bugs.debian.org, Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org> Subject: Re: Bug#747073: [cups-daemon] Doesn't work with systemd Date: Thu, 25 Sep 2014 22:24:49 +0200

Hi all again, I've spent some braincells on this problem and I thought it'd probably be wise to report my thought process to this bug. OdyXLe dimanche, 3 août 2014, 14.06:10 Didier '' Raboud a écrit : > Le dimanche, 3 août 2014, 12.11:58 Marco d'Itri a écrit : > > > systemd maintainers: I think Listen*=[::1]:$port stanzas shouldn't > > > make the .socket-file loading fail if the ipv6 module is not > > > loaded. It should certainly spit out a warning though. > > > > There is no magic "we do not care if it does not work" address > > family: if a unit is configured to open a socket but this fails > > then the unit must fail. This causes more headaches, see below. > Assuming there's no good way to make this work within systemd, I see > three ways forward to fix this in cups: > > a) declare that ipv6 is mandatory these days, document this in > README.Debian, let users cope with it. > Pros: it works for most, ipv6 is coming anyway > Cons: changes done through cups would break the user override every > time. This has been reported privately to me as a serious problem as some institutions apparently continue to forbid ipv6. > b) Detect whether there's a local ipv6 address both in the > cups-daemon.preinst and in the cups code through > cupsd-write-systemd-Port.patch. > Pros: would work for everyone > Cons: wouldn't make cups work over ipv6 if the latter is enabled > after cups is installed; more fault-potential os-specific > code. The more I think about it, the more I become convinced that this would be a nightmare to manage on top of being really ugly. > c) Replace address-based ListenStream stanzas with a combination of > BindIPv6Only and FreeBind to configure systemd to bind only local > or all available interfaces. The problem with that is that CUPS does > address-based checking to verify that its bound addresses are really > local. That could be patched out or corrected though. I've tried to tackle this again, but here are the problems I'm having: i) ListenStream with explicit IPs This means I need to know before writing the file whether the corresponding IP is available; this is the current situation, and it fails when ipv6 is not available. ii) ListenStream with only the port number. This works for the localhost ipv6 [::1] but it doesn't listen on 127.0.0.1:631 but on :::631 . This implies that accessing http://localhost:631/ doesn't spawn CUPS (of course, if you try accessing http://[::1]:631/ first, then CUPS is spawned and the IPv4 access works duing the 30 seconds, as cups has taken the port. iii) Any combination of FreeBind or BindIPv6Only doesn't seem to help. So, dear systemd maintainers; what am I missing? CUPS offers two alternative settings, which I can't reproduce in systemd.socket stanzas: a) 'Listen localhost:631' for which systemd would need to bind against: 127.0.0.1:631 if 127.0.0.1 exists locally (we take is as granted) [::1]:631 if [::1] exists locally (purpose of this very bug) b) 'Port 631' for which systemd would need to bind against: 127.0.0.1:631 if 127.0.0.1 exists locally (we take is as granted) [::1]:631 if [::1] exists locally (purpose of this very bug) + port 631 on every local IP. Reading systemd.socket, I would have set: ListenStream=631 BindIPv6Only=both … and toggled FreeBind to switch from a) to b) as above, but that's not how it works. What am I doing wrong? Let's state it clearly: the core of the problem is that I think that "http://localhost:631/" is a standard CUPS user interface and I'm not ready to make sure users (starting with me) change their muscle memory to use "http://ip6-localhost:631/" or "http://[::1]:631/" instead. How can we make this happen? TIA, cheers, OdyX

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Printing Team <debian-printing@lists.debian.org> :

Bug#747073 ; Package cups-daemon . (Thu, 02 Oct 2014 16:33:18 GMT) (full text, mbox, link).

Acknowledgement sent to Didier 'OdyX' Raboud <odyx@debian.org> :

Extra info received and forwarded to list. Copy sent to Debian Printing Team <debian-printing@lists.debian.org> . (Thu, 02 Oct 2014 16:33:18 GMT) (full text, mbox, link).

Message #90 received at 747073@bugs.debian.org (full text, mbox, reply):

From: Didier 'OdyX' Raboud <odyx@debian.org> To: 747073@bugs.debian.org Cc: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org> Subject: Re: Bug#747073: [cups-daemon] ListenStream=[::1]:631 makes socket fail if ipv6 module is not loaded Date: Thu, 02 Oct 2014 18:31:20 +0200

Hi again, I've gone further in my investigations and therefore filed these two bugs: https://bugs.freedesktop.org/show_bug.cgi?id=84604 https://www.cups.org/str.php?L4491 I think I'm getting a clearer picture of the problem and a potential (wrong ?) workaround patch, stay tuned. Cheers, OdyX

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Printing Team <debian-printing@lists.debian.org> :

Bug#747073 ; Package cups-daemon . (Tue, 21 Oct 2014 20:54:04 GMT) (full text, mbox, link).

Acknowledgement sent to Didier 'OdyX' Raboud <odyx@debian.org> :

Extra info received and forwarded to list. Copy sent to Debian Printing Team <debian-printing@lists.debian.org> . (Tue, 21 Oct 2014 20:54:04 GMT) (full text, mbox, link).

Message #95 received at 747073@bugs.debian.org (full text, mbox, reply):

From: Didier 'OdyX' Raboud <odyx@debian.org> To: debian-printing@lists.debian.org, 747073@bugs.debian.org Cc: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org> Subject: Re: Bug#747073: [cups-daemon] ListenStream=[::1]:631 makes socket fail if ipv6 module is not loaded Date: Tue, 21 Oct 2014 22:50:37 +0200

Hi again all, Le jeudi, 2 octobre 2014, 18.31:20 Didier 'OdyX' Raboud a écrit : > I've gone further in my investigations and therefore filed these two > bugs: I've got answers on these two bugs: https://bugs.freedesktop.org/show_bug.cgi?id=84604 Lennart Poettering saying: > So, systemd currently doesn't support this scheme nicely. We should > however. > (…) > Now, there's one problem with this: the latter line will cause the > .socket unit to fail on kernels where ipv6 is not compiled in. The > question now is what to do about this. https://www.cups.org/str.php?L4491 Mike Sweet saying: > OK, systemd's IPv4 over v6 address is NOT OK. v4-over-v6 is widely > seen as a major security problem, which is why CUPS doesn't support it > transparently. > (…) > The latest changes for STR #4497 no longer use systemd to make the > localhost listeners, so this won't be an issue anymore... The answers combined on both bugs lead me to the conclusion that the socket-activation of CUPS on its INET ports is too premature in absence of the hypothetical new "failure to listen on a port is non-fatal" systemd feature, which is unlikely in Jessie. I will proceed with dropping the "systemd socket activation by-default" feature in Debian's CUPS in the next days, depending on the actual testing migration. I'm not overly happy with this, but I think this is the best way for a rock-solid CUPS in Jessie. Cheers, OdyX

Reply sent to Didier Raboud <odyx@debian.org> :

You have taken responsibility. (Fri, 24 Oct 2014 06:21:09 GMT) (full text, mbox, link).

Notification sent to BogDan Vatra <bogdan.vatra@kdab.com> :

Bug acknowledged by developer. (Fri, 24 Oct 2014 06:21:09 GMT) (full text, mbox, link).

Message #100 received at 747073-close@bugs.debian.org (full text, mbox, reply):

From: Didier Raboud <odyx@debian.org> To: 747073-close@bugs.debian.org Subject: Bug#747073: fixed in cups 1.7.5-7 Date: Fri, 24 Oct 2014 06:18:52 +0000

Source: cups Source-Version: 1.7.5-7 We believe that the bug you reported is fixed in the latest version of cups, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 747073@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Didier Raboud <odyx@debian.org> (supplier of updated cups package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Thu, 23 Oct 2014 22:06:18 +0200 Source: cups Binary: libcups2 libcupsimage2 libcupscgi1 libcupsmime1 libcupsppdc1 cups cups-core-drivers cups-daemon cups-client libcups2-dev libcupsimage2-dev libcupscgi1-dev libcupsmime1-dev libcupsppdc1-dev cups-bsd cups-common cups-server-common cups-ppdc cups-dbg Architecture: source all Version: 1.7.5-7 Distribution: unstable Urgency: medium Maintainer: Debian Printing Team <debian-printing@lists.debian.org> Changed-By: Didier Raboud <odyx@debian.org> Description: cups - Common UNIX Printing System(tm) - PPD/driver support, web interfa cups-bsd - Common UNIX Printing System(tm) - BSD commands cups-client - Common UNIX Printing System(tm) - client programs (SysV) cups-common - Common UNIX Printing System(tm) - common files cups-core-drivers - Common UNIX Printing System(tm) - PPD-less printing cups-daemon - Common UNIX Printing System(tm) - daemon cups-dbg - Common UNIX Printing System(tm) - debugging symbols cups-ppdc - Common UNIX Printing System(tm) - PPD manipulation utilities cups-server-common - Common UNIX Printing System(tm) - server common files libcups2 - Common UNIX Printing System(tm) - Core library libcups2-dev - Common UNIX Printing System(tm) - Development files CUPS library libcupscgi1 - Common UNIX Printing System(tm) - CGI library libcupscgi1-dev - Common UNIX Printing System(tm) - Development files for CGI libra libcupsimage2 - Common UNIX Printing System(tm) - Raster image library libcupsimage2-dev - Common UNIX Printing System(tm) - Development files CUPS image li libcupsmime1 - Common UNIX Printing System(tm) - MIME library libcupsmime1-dev - Common UNIX Printing System(tm) - Development files MIME library libcupsppdc1 - Common UNIX Printing System(tm) - PPD manipulation library libcupsppdc1-dev - Common UNIX Printing System(tm) - Development files PPD library Closes: 747073 Changes: cups (1.7.5-7) unstable; urgency=medium . * Revert to not socket-activating CUPS (Closes: #747073) - Drop patch to let CUPS write the systemd.socket configuration files - Replace preinst generation of the same configuration file, delete them on upgrade - Drop the symlink enforcing the automatic configuration - Update NEWS and README.Debian to reflect that change - Create two cups socket configuration examples, document their existence in README.Debian - Update the systemd socket activation patch to include PassCredentials=true in the socket configuration, following upstream's feedback - Disable automatic idle exit timeout under systemd, as this will get activated without socket activation Checksums-Sha1: 50ccf37f14cd2026904ca865ccb755436359ab02 3418 cups_1.7.5-7.dsc 3f5068aa2df4b9f55d31a7105b2d08dac18c86cb 302736 cups_1.7.5-7.debian.tar.xz 088c4e522d24e393b5723220547abb261019405c 273192 cups-common_1.7.5-7_all.deb ed500f7867a94466ef2446127171a4ceaaa20c83 620422 cups-server-common_1.7.5-7_all.deb Checksums-Sha256: 5f85034b3e56b0a4593cdf6e5ae4f0fc2215aef05ce7f007c89daf28b7c71a53 3418 cups_1.7.5-7.dsc 041e9e385963a8716508c7a58ab5df5f80e2c7940a241bdec09b1ad1eeb27a49 302736 cups_1.7.5-7.debian.tar.xz 5e781bb254b5543817532adae71b1be2bf05ab1189f0c8c0b732beab7eac14c7 273192 cups-common_1.7.5-7_all.deb a073c6fe990eaf56329a9cf4deaff349b4686da8e63a943cd42cab8f07b6992a 620422 cups-server-common_1.7.5-7_all.deb Files: ee36e7fa8d143f6b1ec3cca6a9f0efff 3418 net optional cups_1.7.5-7.dsc 40637eadbdda81b8b775f030373fa80e 302736 net optional cups_1.7.5-7.debian.tar.xz 56b01acfeaf907d4cda88806b3f004a8 273192 net optional cups-common_1.7.5-7_all.deb 60da758cd0aabe5c31698973c6c82c15 620422 net optional cups-server-common_1.7.5-7_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQGcBAEBCAAGBQJUSe33AAoJEIvPpx7KFjRVSfwL/0PBXfW3xAXQukQpSllhZtp3 YGdpwZ+eruj6UTJ01+RBPmS/TpLQjF7wRgf9vbBb5nidlShVrd3WlbTL/kU4n8HL rzttkTgcBUl1JUAoFNaCPnEAKzxYQf1AYyFRS9wuard02szqwYuwXv1z2B3xIIqD OB/fhnzQnr2t/wp19vQpDA4ifKWIaKebYmrV+WJe2sel8dfWVfEKhSE6Xv/Laio9 55T7pEhoxOV9wfp0r9BHUJ17d5EB5BBM0pof1Kz4dpXsp9YXR0hxtynFVHKKyiTg 4LEQ6Fujmil0DOLKNxpnUayZLPfKjvh4xgEWHdQkxYltgrYHuIip1HB/ayy2Y5ZE 9RJO403bSGTADuqgbWq3lwrv0IDp3wmzcT9IOg+NKD66cl2wsWj0/25AJwM6K4uB gjnUNdSg/4rn+jWtBay/TiLl9gmOMyggCIM+hZ+fHFS1XgQBXqwIZKntJAyVE8CC 7Opq2IgVpO7HF3GinkptdDJLT5BNO8H+4lru/3oTuA== =hyy7 -----END PGP SIGNATURE-----

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Printing Team <debian-printing@lists.debian.org> :

Bug#747073 ; Package cups-daemon . (Fri, 24 Oct 2014 17:15:05 GMT) (full text, mbox, link).

Acknowledgement sent to Josh Triplett <josh@joshtriplett.org> :

Extra info received and forwarded to list. Copy sent to Debian Printing Team <debian-printing@lists.debian.org> . (Fri, 24 Oct 2014 17:15:05 GMT) (full text, mbox, link).

Message #105 received at 747073@bugs.debian.org (full text, mbox, reply):

From: Josh Triplett <josh@joshtriplett.org> To: 747073@bugs.debian.org Cc: Didier 'OdyX' Raboud <odyx@debian.org> Subject: Re: Bug#747073: [cups-daemon] Doesn't work with systemd Date: Fri, 24 Oct 2014 10:13:00 -0700

On Thu, 25 Sep 2014 22:24:49 +0200 Didier 'OdyX' Raboud <odyx@debian.org> wrote: > ii) ListenStream with only the port number. > This works for the localhost ipv6 [::1] but it doesn't listen on > 127.0.0.1:631 but on :::631 . This implies that accessing > http://localhost:631/ doesn't spawn CUPS (of course, if you try > accessing http://[::1]:631/ first, then CUPS is spawned and the > IPv4 access works duing the 30 seconds, as cups has taken the port. This seems like the fundamental bug here. Listening on [::1]:631 with BindIPv6Only=both *should* work equivalently to listening on 127.0.0.1:631 or localhost:631, and accessing http://localhost:631/ should then spawn CUPS rather than giving an error. Regarding the "v4-over-v6 is widely seen as a major security problem" in the CUPS bug report: per https://tools.ietf.org/html/draft-itojun-v6ops-v4mapped-harmful-02 , the problem is using v4mapped addresses *on the wire*, not using such addresses within a system to listen on a single socket. The recommendations from that draft say to avoid generating or receiving IPv6 packets on the wire that contain v4mapped addresses, and that same draft says "IPv4-mapped addresses are exclusively for uses local to a node as specified in the basic API". That said, I'd still like to see systemd capable of producing both a v4 and v6 listening socket, for whichever stacks the local system has, omitting any that cannot exist because the stack doesn't exist. (Ideally, systemd should only allow a ListenStream to fail because of a missing stack, while still erroring on failures such as port conflicts.) > Let's state it clearly: the core of the problem is that I think that > "http://localhost:631/" is a standard CUPS user interface and I'm not > ready to make sure users (starting with me) change their muscle memory > to use "http://ip6-localhost:631/" or "http://[::1]:631/" instead. How > can we make this happen? On a closely related note, I think we should fix hostname resolution so that "localhost" resolves to both 127.0.0.1 and ::1, and vice versa, with ip6-localhost remaining only as a compatibility fallback, if at all. http://localhost:631/ should work just fine over IPv6, just as any other http or https URL does; if it doesn't, let's fix that. - Josh Triplett

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Printing Team <debian-printing@lists.debian.org> :

Bug#747073 ; Package cups-daemon . (Fri, 24 Oct 2014 19:06:05 GMT) (full text, mbox, link).

Acknowledgement sent to Didier 'OdyX' Raboud <odyx@debian.org> :

Extra info received and forwarded to list. Copy sent to Debian Printing Team <debian-printing@lists.debian.org> . (Fri, 24 Oct 2014 19:06:05 GMT) (full text, mbox, link).

Message #110 received at 747073@bugs.debian.org (full text, mbox, reply):

From: Didier 'OdyX' Raboud <odyx@debian.org> To: Josh Triplett <josh@joshtriplett.org> Cc: 747073@bugs.debian.org Subject: Re: Bug#747073: [cups-daemon] Doesn't work with systemd Date: Fri, 24 Oct 2014 21:03:44 +0200

Le vendredi, 24 octobre 2014, 10.13:00 Josh Triplett a écrit : > On Thu, 25 Sep 2014 22:24:49 +0200 Didier 'OdyX' Raboud <odyx@debian.org> wrote: > > ii) ListenStream with only the port number. > > > > This works for the localhost ipv6 [::1] but it doesn't listen > > on > > 127.0.0.1:631 but on :::631 . This implies that accessing > > http://localhost:631/ doesn't spawn CUPS (of course, if you try > > accessing http://[::1]:631/ first, then CUPS is spawned and the > > IPv4 access works duing the 30 seconds, as cups has taken the > > port. > > This seems like the fundamental bug here. Listening on [::1]:631 with > BindIPv6Only=both *should* work equivalently to listening on > 127.0.0.1:631 or localhost:631, and accessing http://localhost:631/ > should then spawn CUPS rather than giving an error. Did you see Lennart's analysis on https://bugs.freedesktop.org/show_bug.cgi?id=84604 ? > That said, I'd still like to see systemd capable of producing both a > v4 and v6 listening socket, for whichever stacks the local system > has, omitting any that cannot exist because the stack doesn't exist. > (Ideally, systemd should only allow a ListenStream to fail because of > a missing stack, while still erroring on failures such as port > conflicts.) Yes, I concur. In fact, conducting this analysis and involving both the Apple and systemd upstream authors has convinced me that getting this right will be possible, but the pieces are not yet available. Cheers, OdyX

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Printing Team <debian-printing@lists.debian.org> :

Bug#747073 ; Package cups-daemon . (Fri, 24 Oct 2014 20:27:04 GMT) (full text, mbox, link).

Acknowledgement sent to josh@joshtriplett.org :

Extra info received and forwarded to list. Copy sent to Debian Printing Team <debian-printing@lists.debian.org> . (Fri, 24 Oct 2014 20:27:04 GMT) (full text, mbox, link).

Message #115 received at 747073@bugs.debian.org (full text, mbox, reply):

From: josh@joshtriplett.org To: Didier 'OdyX' Raboud <odyx@debian.org> Cc: 747073@bugs.debian.org Subject: Re: Bug#747073: [cups-daemon] Doesn't work with systemd Date: Fri, 24 Oct 2014 13:25:45 -0700

On Fri, Oct 24, 2014 at 09:03:44PM +0200, Didier 'OdyX' Raboud wrote: > Le vendredi, 24 octobre 2014, 10.13:00 Josh Triplett a écrit : > > On Thu, 25 Sep 2014 22:24:49 +0200 Didier 'OdyX' Raboud > <odyx@debian.org> wrote: > > > ii) ListenStream with only the port number. > > > > > > This works for the localhost ipv6 [::1] but it doesn't listen > > > on > > > 127.0.0.1:631 but on :::631 . This implies that accessing > > > http://localhost:631/ doesn't spawn CUPS (of course, if you try > > > accessing http://[::1]:631/ first, then CUPS is spawned and the > > > IPv4 access works duing the 30 seconds, as cups has taken the > > > port. > > > > This seems like the fundamental bug here. Listening on [::1]:631 with > > BindIPv6Only=both *should* work equivalently to listening on > > 127.0.0.1:631 or localhost:631, and accessing http://localhost:631/ > > should then spawn CUPS rather than giving an error. > > Did you see Lennart's analysis on > https://bugs.freedesktop.org/show_bug.cgi?id=84604 ? Yes, I read that before responding. Between the two bugs, I think the fundamental problem is that CUPS refuses to support v4mapped IPv6 sockets, which are the only way to handle everything through one socket, and systemd can't currently work around that by configuring a socket per *available* address family without failing on unavailable address families. > > That said, I'd still like to see systemd capable of producing both a > > v4 and v6 listening socket, for whichever stacks the local system > > has, omitting any that cannot exist because the stack doesn't exist. > > (Ideally, systemd should only allow a ListenStream to fail because of > > a missing stack, while still erroring on failures such as port > > conflicts.) > > Yes, I concur. > > In fact, conducting this analysis and involving both the Apple and > systemd upstream authors has convinced me that getting this right will > be possible, but the pieces are not yet available. Agreed. - Josh Triplett

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Printing Team <debian-printing@lists.debian.org> :

Bug#747073 ; Package cups-daemon . (Sat, 25 Oct 2014 07:15:10 GMT) (full text, mbox, link).

Acknowledgement sent to Didier 'OdyX' Raboud <odyx@debian.org> :

Extra info received and forwarded to list. Copy sent to Debian Printing Team <debian-printing@lists.debian.org> . (Sat, 25 Oct 2014 07:15:11 GMT) (full text, mbox, link).

Message #120 received at 747073@bugs.debian.org (full text, mbox, reply):

From: Didier 'OdyX' Raboud <odyx@debian.org> To: josh@joshtriplett.org, 747073@bugs.debian.org Subject: Re: Bug#747073: [cups-daemon] Doesn't work with systemd Date: Sat, 25 Oct 2014 09:11:38 +0200

Le vendredi, 24 octobre 2014, 13.25:45 josh@joshtriplett.org a écrit : > On Fri, Oct 24, 2014 at 09:03:44PM +0200, Didier 'OdyX' Raboud wrote: > > Did you see Lennart's analysis on > > https://bugs.freedesktop.org/show_bug.cgi?id=84604 ? > > Yes, I read that before responding. Between the two bugs, I think the > fundamental problem is that CUPS refuses to support v4mapped IPv6 > sockets, which are the only way to handle everything through one > socket, and systemd can't currently work around that by configuring a > socket per *available* address family without failing on unavailable > address families. For the record; given my (current) understanding of the problem, I agree with CUPS upstream choices here: refusing to support v4mapped IPv6 sockets while supporting IPv4 sockets is a sane choice, which systemd ought to support. Cheers, OdyX

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Printing Team <debian-printing@lists.debian.org> :

Bug#747073 ; Package cups-daemon . (Sat, 25 Oct 2014 07:51:05 GMT) (full text, mbox, link).

Acknowledgement sent to Josh Triplett <josh@joshtriplett.org> :

Extra info received and forwarded to list. Copy sent to Debian Printing Team <debian-printing@lists.debian.org> . (Sat, 25 Oct 2014 07:51:05 GMT) (full text, mbox, link).

Message #125 received at 747073@bugs.debian.org (full text, mbox, reply):

From: Josh Triplett <josh@joshtriplett.org> To: Didier 'OdyX' Raboud <odyx@debian.org> Cc: 747073@bugs.debian.org Subject: Re: Bug#747073: [cups-daemon] Doesn't work with systemd Date: Sat, 25 Oct 2014 00:46:15 -0700

On Sat, Oct 25, 2014 at 09:11:38AM +0200, Didier 'OdyX' Raboud wrote: > Le vendredi, 24 octobre 2014, 13.25:45 josh@joshtriplett.org a écrit : > > On Fri, Oct 24, 2014 at 09:03:44PM +0200, Didier 'OdyX' Raboud wrote: > > > Did you see Lennart's analysis on > > > https://bugs.freedesktop.org/show_bug.cgi?id=84604 ? > > > > Yes, I read that before responding. Between the two bugs, I think the > > fundamental problem is that CUPS refuses to support v4mapped IPv6 > > sockets, which are the only way to handle everything through one > > socket, and systemd can't currently work around that by configuring a > > socket per *available* address family without failing on unavailable > > address families. > > For the record; given my (current) understanding of the problem, I agree > with CUPS upstream choices here: refusing to support v4mapped IPv6 > sockets while supporting IPv4 sockets is a sane choice, which systemd > ought to support. While I agree that systemd needs to cover this case, why do you think CUPS shouldn't support v4mapped? Did you read the document I previously linked to about not using v4mapped *on the wire* but using it *within a system*? - Josh Triplett

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Printing Team <debian-printing@lists.debian.org> :

Bug#747073 ; Package cups-daemon . (Sun, 26 Oct 2014 14:09:04 GMT) (full text, mbox, link).

Acknowledgement sent to dondavis@reglue.org :

Extra info received and forwarded to list. Copy sent to Debian Printing Team <debian-printing@lists.debian.org> . (Sun, 26 Oct 2014 14:09:04 GMT) (full text, mbox, link).

Message #130 received at 747073@bugs.debian.org (full text, mbox, reply):

From: Don Davis <dondavis@reglue.org> To: 747073@bugs.debian.org Subject: And the fix is? Date: Sun, 26 Oct 2014 09:06:08 -0500

I appreciate the insight - but how might a regular user now use CUPS without enabling ipv6?

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Printing Team <debian-printing@lists.debian.org> :

Bug#747073 ; Package cups-daemon . (Sun, 26 Oct 2014 15:21:10 GMT) (full text, mbox, link).

Acknowledgement sent to Didier 'OdyX' Raboud <odyx@debian.org> :

Extra info received and forwarded to list. Copy sent to Debian Printing Team <debian-printing@lists.debian.org> . (Sun, 26 Oct 2014 15:21:10 GMT) (full text, mbox, link).

Message #135 received at 747073@bugs.debian.org (full text, mbox, reply):

From: Didier 'OdyX' Raboud <odyx@debian.org> To: dondavis@reglue.org, 747073@bugs.debian.org Subject: Re: Bug#747073: And the fix is? Date: Sun, 26 Oct 2014 16:12:45 +0100

Le dimanche, 26 octobre 2014, 09.06:08 Don Davis a écrit : > I appreciate the insight - but how might a regular user now use CUPS > without enabling ipv6? Just install the packages and "use it"; CUPS will be launched permanently as system service, and be kept running, exactly as it was in Wheezy. Cheers, OdyX

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Printing Team <debian-printing@lists.debian.org> :

Bug#747073 ; Package cups-daemon . (Sun, 26 Oct 2014 15:21:14 GMT) (full text, mbox, link).

Acknowledgement sent to Didier 'OdyX' Raboud <odyx@debian.org> :

Extra info received and forwarded to list. Copy sent to Debian Printing Team <debian-printing@lists.debian.org> . (Sun, 26 Oct 2014 15:21:14 GMT) (full text, mbox, link).

Message #140 received at 747073@bugs.debian.org (full text, mbox, reply):

From: Didier 'OdyX' Raboud <odyx@debian.org> To: Josh Triplett <josh@joshtriplett.org>, 747073@bugs.debian.org Subject: Re: Bug#747073: [cups-daemon] Doesn't work with systemd Date: Sun, 26 Oct 2014 16:17:03 +0100

Le samedi, 25 octobre 2014, 00.46:15 Josh Triplett a écrit : > On Sat, Oct 25, 2014 at 09:11:38AM +0200, Didier 'OdyX' Raboud wrote: > > For the record; given my (current) understanding of the problem, I > > agree with CUPS upstream choices here: refusing to support v4mapped > > IPv6 sockets while supporting IPv4 sockets is a sane choice, which > > systemd ought to support. > > While I agree that systemd needs to cover this case, why do you think > CUPS shouldn't support v4mapped? > > Did you read the document I previously linked to about not using > v4mapped *on the wire* but using it *within a system*? Let's rephrase then: my current position is that I will follow upstream's choices in socket management; I don't have enough resources myself to change how CUPS works in this regard. That said, part of the problem is that CUPS does "localhost" matching to verify that the incoming connections are allowed by its own configuration. In a large scheme of things, CUPS-when-run-on-a-systemd- system could probably "blindly" trust systemd sockets and not second- judge whether they are legit or not; the responsibility to decide on which addresses CUPS should be triggered would be entirely deferred to systemd. But that's not how CUPS works currently. :-) Cheers, OdyX

Bug archived. Request was from Debbugs Internal Request <owner@bugs.debian.org> to internal_control@bugs.debian.org . (Mon, 01 Dec 2014 08:10:11 GMT) (full text, mbox, link).

Send a report that this bug log contains spam.