Print preview takes a long time and then says "cannot connect to printer"
Reported by
jsm...@stillwaterschools.com,
Jul 1 2016
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36 Steps to reproduce the problem: 1. Click 'print' icon in gmail 2. Watch print preview spinner go for a long time 3. See dialog box complain about cannot connect to printer What is the expected behavior? Print preview should work. What went wrong? This is an enterprise environment. Two cases, one printing to a local usb-connected Dell 2335dn, one printing to a networked Dell 2155cdn. In both cases, they could print from other programs. Restarting Chrome solved the problem. We haven't been able to reproduce in-house yet. Did this work before? Yes Chrome version: 51.0.2704.103m Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 22.0 r0
,
Jul 1 2016
Correct. And no, the problem has not cropped up again since we asked JD to restart Chrome.
,
Jul 1 2016
It would be hard to solve issues like this one that cannot be easily reproduced. My guess is that the networked printer was the most recently used printer, so Chrome tried to query it the next time JD tried to print, but it was offline, and took forever to timeout and fail.
,
Aug 25 2016
Assuming the system default printer is always reachable, and Chrome changed its behavior to always select the system default printer instead of the (unreachable) most recently used printer, then that may mitigate this issue. That is, the user won't have a bad experience until they try to use the unreachable printer. I believe in the case of an unreachable network printer, other programs will similarly hang for a bit when the user tries to select the unreachable printer. So not much we can do there. Also, if the default printer is unreachable, then the user will have hit hangs in all programs when trying to print.
,
Aug 26 2016
We haven't had a repeat of this issue (but the school year is still young) so far, so it may be safe to close.
,
Aug 28 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||
►
Sign in to add a comment |
|||
Comment 1 by thestig@chromium.org
, Jul 1 2016