On Thu 20 Apr 2017 at 14:50:55 +0100, Brian Potkin wrote: > > $ sudo cupsctl debuglevel=warn
The line "debuglevel=warn" will be in your cupsd.conf. You can edit the file to remove it. > > $ sudo systemctl status cups > > ● cups.service - CUPS Scheduler > > Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor > > preset: enabled) > > Active: failed (Result: exit-code) since Thu 2017-04-20 21:00:13 AEST; > > 1s ago > > Docs: man:cupsd(8) > > Process: 8587 ExecStart=/usr/sbin/cupsd -l (code=exited, status=1/FAILURE) > > Main PID: 8587 (code=exited, status=1/FAILURE) > > CPU: 324ms > > > > Apr 20 21:00:04 lantana systemd[1]: Started CUPS Scheduler. > > Apr 20 21:00:13 lantana systemd[1]: cups.service: Main process exited, > > code=exited, status=1/FAILURE > > Apr 20 21:00:13 lantana systemd[1]: cups.service: Unit entered failed state. > > Apr 20 21:00:13 lantana systemd[1]: cups.service: Failed with result > > 'exit-code'. > > We get the same outcome. This looks like a different issue from yours. #861470 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861470 -- Brian.
