Issue metadata
Sign in to add a comment
|
Cloud print fails to print, print ticket failed to parse
Reported by
hen...@gildecollege.nl,
Nov 8 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 8953.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2905.0 Safari/537.36 Platform: 8953.0.0 (Official Build) dev-channel cyan Steps to reproduce the problem: I just tried to print something through google docs, it says that it failed to print and cannot parse the print ticket. Last friday it did work the right way. Also when manually uploading a document it will print the right way. What is the expected behavior? That the document is send to the printer directly, without the user needing to upload it first. Print directly from google docs. What went wrong? I dont know? It gives me an error i attached a screenshot. Did this work before? Yes I dont know. Chrome version: 56.0.2905.0 Channel: dev OS Version: 8953.0.0 Flash Version: 23.0.0.205-r1 Hope its get fixed soon because we need this as we use about 200 chromebooks in our environment.
,
Nov 9 2016
Sorry, typo: should be: CBC-RS/TC-watchlist
,
Nov 10 2016
How do i get to CBC-RS/TC-watchlist ?
,
Nov 10 2016
Toshiba Chromebook 2 running Chrome OS Version 56.0.2905.0 dev (64-bit) Platform 8953.0.0 (Official Build) dev-channel swanky Firmware Google_Swanky.5216.238.5 The same printer works fine with a Google Cloud print from a Windows 10 PC running Chrome browser.
,
Nov 11 2016
,
Nov 11 2016
This may be the same as http://crbug.com/660817 . If it is the issue should be resolved on the next Dev channel update; it's been fixed but the fix didn't make it into 2905.0.
,
Nov 11 2016
Workaround #1: -- download file to local drive -- go to https://www.google.com/cloudprint#jobs -- use red PRINT button -- select Upload file to print -- navigate to downloaded file>>select -- print Looking in CBC for other posts with possibly more workarounds. Note that Powerwash has not yet been done, nor a USB/SD restoration -- I do not like these possible solutions as they are very poor UX.
,
Nov 11 2016
in re #6 -- then should the two be merged?
,
Nov 11 2016
We need to see if this actually resolves itself in the next update. If it does, it's a duplicate, if not, this is being caused by a separate issue that we need to address. I don't think we should merge the two until we know for certain that it is the same problem.
,
Nov 16 2016
FIXED in latest Dev Release: Version 56.0.2920.0 dev (64-bit)
,
Nov 16 2016
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by frankt3...@gmail.com
, Nov 8 2016