On Wed, Oct 25, 2017 at 08:08:04PM +0100, Brian Potkin wrote: > Hello Julian; thank you for your report.
Hello Brian, Thanks for getting back to me! > On Sun 22 Oct 2017 at 09:20:28 +0100, Julian Gilbey wrote: > > > Package: cups > > Version: 2.2.5-2 > > Severity: important > > > > (I'm labelling this as "important" because it's wasting large amounts > > of paper.) > > > > This is a weird bug, and I have little idea how to track down the > > cause. > > > > About a week or so ago, on my Debian testing system, printing commands > > started producing three copies of every page on my local printer (so a > > 2-page document would come out at 3 copies of page 1 followed by 3 > > copies of page 2). This is the case in at least all of the following > > circumstances: > > Can this changed be pinned down to any particular version of cups or > cups-filters? Or something you altered in cupsd.conf (for example) at > that time? The upgrades I've done in October were as follows: Oct 8: [UPGRADE] cups-browsed:amd64 1.16.4-1+b2 -> 1.17.8-1 [UPGRADE] cups-filters:amd64 1.16.4-1+b2 -> 1.17.8-1 [UPGRADE] cups-filters-core-drivers:amd64 1.16.4-1+b2 -> 1.17.8-1 [UPGRADE] libcupsfilters-dev:amd64 1.16.4-1+b2 -> 1.17.8-1 [UPGRADE] libcupsfilters1:amd64 1.16.4-1+b2 -> 1.17.8-1 [UPGRADE] libfontembed1:amd64 1.16.4-1+b2 -> 1.17.8-1 Oct 11: [UPGRADE] cups-browsed:amd64 1.17.8-1 -> 1.17.9-1 [UPGRADE] cups-filters:amd64 1.17.8-1 -> 1.17.9-1 etc. (same packages as above) Oct 22: [UPGRADE] cups:amd64 2.2.4-7 -> 2.2.5-2 [UPGRADE] cups-bsd:amd64 2.2.4-7 -> 2.2.5-2 etc., but the problem was already present before this date. So perhaps it was the Oct 8 or Oct 11 upgrade of cups-filters? I downgraded back to 1.16.4-1+b2, and then it worked fine. I upgraded to 1.17.9-1 (dist-upgrade through aptitude) and immediately downgraded to 1.17.8-1, and it still worked, and then I upgraded back to 1.17.9-1, and it still works. So now everything is working again, and I have no obvious way now of reproducing the problem. How weird. > > SELF Test Page only produces a single page of output! > > A self-test page is actually produced by the printer itself; it is often > done from a button on the printer. The filtering system is not involved. Ah, OK. > Did you really use port 603 to bring up the CUPS web interface? Duh, no, 631, sorry. > You also mention Windows and Mac machines. I am not familiar with > printing from either of these, but my understanding is that Windows does > all the processing and sends the completed job to a CUPS server, which > does no processing. That is, the filtering system is bypassed. I wonder > whether your Mac is doing this too. Yes, I should have been more precise: they print directly to the printer over ethernet, not via CUPS. This showed me that the problem lay in the CUPS system, not in the printer itself. > > [...] > > Any suggestions? > > We'll need the printer model, the PPD used and an error_log. So in the meantime, for the sake of information, it's a Brother DCP-9020CDW. But there's no point in sending logs, etc., because it's now working again.... So I guess either close this bug report or mark it as unreproducible? Best wishes, Julian
