Processing commands for cont...@bugs.debian.org:
> reopen 814340
Bug #814340 {Done: Brian Potkin } [cups-daemon] CUPS
won't start at boot (systemd)
Bug reopened
Ignoring request to alter fixed versions of bug #814340 to the same values
previously set
> thanks
Stopping processing here.
Please co
reopen 814340
thanks
On Sat 13 Feb 2016 at 09:55:20 +0100, Cédric Dufour - Idiap Research Institute
wrote:
> Hello Brian,
>
> Thank you for your follow up.
>
> There something I don't understand and maybe you can clarifiy it for me (see
> below)
>
> On 13/02/16 00:19, Brian Potkin wrote:
Hello Brian,
Thank you for your follow up.
There something I don't understand and maybe you can clarifiy it for me (see
below)
On 13/02/16 00:19, Brian Potkin wrote:
> On Wed 10 Feb 2016 at 15:50:53 +0100, Cédric Dufour - Idiap Research
> Institute wrote:
>
>
>> I have found that CUPS will not
Hello again,
The issue at hand does not occur on hosts where 'cups-browsed' is also
installed (I guess the cups.service somehow gets "pulled in" by
/etc/systemd/system/multi-user.target.wants/cups-browsed.service; I
don't understand, however, how
/etc/systemd/system/paths.target.wants/cups.path co
Package: cups-daemon
Version: 1.7.5-11+deb8u1
Hello,
I have found that CUPS will not start at boot if the /var/spool/cups
directory contains no d* files (job files).
This is the case for a brand new CUPS installation or if
"PreserveJobFiles" is set to "No" in /etc/cups/cupsd.conf (eg. for large
c
