Bug#928838: cups: Printing from local queue via remote queue not working any more, jobs just vanish

[Brian Potkin <claremont102@gmail.com>]

tags 928838 moreinfo
thanks


On Sun 12 May 2019 at 04:20:12 +0200, Robert Senger wrote:

> Package: cups
> Version: 2.2.10-6
> Severity: normal
> 
> Dear Maintainer,
> 
>    * What led up to the situation?
> 
> Setup:
> 
> Laptop (Client) running Debian 9/10 and CUPS 2.2.1/2.2.10
> Server/Router running Debian 10 and CUPS 2.2.10
> Printer Samsung Xpress C480W, LAN/WLAN
> 
> Laptop is connected to Server via SSID WLAN_1, Subnet 1
> Printer is connected to Server via SSID WLAN_2, Subnet 2
> Server should act as a print server running CUPS. Clients (laptop, printer) in
> different subnets should not communicate directly.
> 
> Printer is configured in CUPS on the server as ipp://printername:631/ipp/print,
> with Samsung C48x driver, queue name SAMSUNG, printing test pages from the
> server's web interface works fine
> Printer is configured in CUPS on the Laptop as
> ipps://servername:631/printers/SAMSUNG
> 
> With Debian 9 and CUPS 2.2.1 on the Server, this setup worked fine.
> 
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
> 
> Upgraded Server to Debian 10, CUPS 2.2.10
> 
>    * What was the outcome of this action?
> 
> Printing as describes above stopped working. Jobs sent from the laptop just go
> into Nirvana, they vanish and do not show up in the server's queue. The servers
> access_log reports success, but printing never happens. No errors are reported
> neither on the laptop nor on the server.
> 
>    * What outcome did you expect instead?
> 
> Printing as before.
> 
>    * Workaround(s)
> 
> - Downgrading CUPS from 2.2.10 to 2.2.1 (debs from Debian 9) on the Debian 10
> server fixes this problem, printing works fine again.
> - Using a client.conf file with "ServerName servername" makes printing
> possible, but without a local queue there's no queue dialog that can report
> failures (emtpy tray, paper jam) on the client
> - Printing directly to the printer from the laptop works, but is not desired
> 
> So, CUPS 2.2.10 is broken when used as a print server for clients running local
> queues.

Thank you for your report, Robert. Did you ever resolve this issue for
yourself? Perhaps by upgrading to bullseye on client and server?

Regards,

Brian.