Le lundi, 20 juillet 2015, 11.04:21 MAG4 Piemonte a écrit : > Hi, we also confirm the bug after updating to 2.0.3-6 and the > temporary workaround manually running cupsd. We have some clients > running Testing and comparing the cups* running processes we found > that every client has > > /usr/sbin/cups-browsed > /usr/sbin/cupsd -l > /usr/lib/cups/notifier/dbus dbus://
The presence of "/usr/sbin/cupsd -l" indicates that it got started correctly by systemd. > but only the workarounded manually running cupsd has > > cupsd -C /etc/cups/cupsd.conf -s /etc/cups/cups-files.conf There should be no difference between letting systemd launch "cupsd -l" or launching the above command manually. This points to a weird behaviour when launched by systemd. What do the following commands output when the manual workaround has not been used (aka, cupsd launched by systemd, but apparently inactive) (please launch them as root): # grep -E 'WebInterface|Listen' /etc/cups/cupsd.conf # systemdctl status cups cups.socket cups.path # journalctl -u cups > /tmp/cups.journal Please attach cups.journal Cheers, OdyX -- OdyX -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org