Need to restart chrome after restarting privet print server |
||||
Issue descriptionVersion 51.0.2704.79 (64-bit) OS: Linux What steps will reproduce the problem? (1) run gcp-cups-connector in local mode (2) print to a local (privet) printer (3) restart gcp-cups-connector (4) try to print again What is the expected output? Printing works just fine. What do you see instead? The first time I try to print, I get a message that printing failed. When I close the dialog and open it again, I get a blank print window (see screenshot). This is especially bad on Chrome OS since I have to log out and in again when this happens.
,
Jun 14 2016
I suspect this is a bug in cloud-print-connector. The connector definitely loses start if it restarts. I will leave this bug open for now but close it once I figure out what's going on with the connector.
,
Jun 14 2016
(loses state if it restarts)
,
Jun 15 2016
If you use a Windows machine as the cloud print proxy, do you hit the same problem? You can proxy the XPS document printer for testing.
,
Jun 15 2016
I will try this later, but cloud-print-connector does not support Privet. Does Chrome running in proxy mode?
,
Jun 15 2016
No sure. It's all "cloud print" to me.
,
Jun 15 2016
I will have to run tests to be sure, but it doesn't look like Chrome provides a Privet server. This involves running an HTTP server on many ports (one per printer) and serving up /privet resources. It also needs to register with the system-wide mdns provider (bonjour or avahi). For windows, it would need to bundle the Apple Bonjour SDK. I don't see code to do this in chromium. Regarding my last comments, I am still seeing these issues after fixing the known problems with the server's state.
,
Oct 8 2016
Also, Chrome running on Windows and Mac are not affected by this?
,
Oct 19 2016
I will have to verify this, but I think all platforms are affected.
,
Mar 9 2017
agoode: Hope you can figure out if this is a cloud-print-connector bug when you have time. Toss the bug back to me if it's a Chrome bug.
,
Mar 9 2017
I have not seen this recently. Keep it assigned to me and I will troubleshoot if I have the problem again.
,
Apr 12 2017
Yes, this is still an issue, my printer server restarted due to a power outage and I see the same symptoms on Chromium 57.0.2987.133.
,
Jul 20
,
Jul 21
Can we simulate the power outage by sending a SIGKILL to gcp-cups-connector?
,
Jul 21
You don't need to do anything fancy to reproduce it, just restarting the connector cleanly will do it. |
||||
►
Sign in to add a comment |
||||
Comment 1 by agoode@chromium.org
, Jun 10 2016