Chrome printing does not detect paused printers
Reported by
kylemacf...@gmail.com,
Jun 12 2016
|
|||||
Issue descriptionChrome Version : 51.0.2704.84 As requested at https://github.com/google/cups-connector/issues/224 The basic problem is that if you pause a printer in CUPS the GCP control panel will detect this but Chrome will still say that the printer is working. The attached image shows what happens at google.com/cloudprint if you pause a printer in CUPS. However Chrome will still detect this printer as working fine and allow you to send print jobs to it.
,
Jun 15 2016
agoode: Is there some GCP protocol that I should be aware of here?
,
Oct 6 2016
,
Mar 9 2017
agoode: Is this an issue with ConnectionStatus or something? If you happen to know what bit of data Chromium should be looking for, that would be really helpful.
,
Mar 9 2017
I am looking at CUPS and cloud-print-connector. So, when a printer is paused (with cupsdisable), the state of the printer goes to "stopped". This should come across to GCP as CloudDeviceState.printer.state == STOPPED. https://developers.google.com/cloud-print/docs/cdd#cds The "Paused" text in the screenshot above comes from literal text in CUPS (not an enum), so it's conveyed as a vendor message.
,
Mar 9 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by agoode@chromium.org
, Jun 13 2016Status: Untriaged (was: Unconfirmed)