Bug#908147: restarting cups-browsed deleted print jobs
On Sat 01 Dec 2018 at 18:04:15 +0100, gregor herrmann wrote:
> On Thu, 06 Sep 2018 13:31:51 -0400, Anthony DeRobertis wrote:
>
> > After doing so, the queue in the browser refreshed and showed empty. But
> > I checked — the PDFs were not created. Showing completed jobs shows
> > nothing. Looking in /var/spool/cups (on both the local machine and the
> > remote machine) shows no sign of the two jobs.
>
> I can't reproduce this bug but maybe I did something wrong. What I
> did was:
>
> - print to a printer which is not available
> - check in the cups web ui and in /var/spool/cups that the print job
> is there
> - service cups-browsed restart
> - and the job is still in the spool and the web ui still shows the job
> and the problem (printer not responding; well, it's a few hundred
> kilometers away)
>
> (In the spirit of full disclosure: this is with sysv-init and not
> systemd, in case this makes a difference.)
I would doubt the init system is a factor. Additionally, your print
queue/printer is not on the local network so discovery via Bonjour
broadcasting is not involved, as it would seem to be with Anthony
DeRobertis. So, I am unsure how pertinent your observation is.
> Cheers,
> gregor, from the Bern BSP
Thanks for your participation in the BSP. All work and no beer I
imagine. Or did Odyx buy you a few? :)
Regards,
Brian.
Reply to: