New issue
Advanced search Search tips

Issue 647060 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Printing from Drive resulted in invalidfont printout

Project Member Reported by tsobczak@google.com, Sep 14 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36

Steps to reproduce the problem:
1. Click print from within Drive
2. Print to printer

What is the expected behavior?
The document prints

What went wrong?
The printer printed a page that read 

ERROR: invalidfont
OFFENDING COMMAND: show

STACK:

(5)

Did this work before? Yes September 9, 2016

Chrome version: 52.0.2743.116  Channel: n/a
OS Version: OS X 10.11.6
Flash Version: Shockwave Flash 22.0 r0

This happened both from the Chrome print dialog and when I chose to print from the system dialog.
 
Labels: Needs-Feedback Hotlist-Google
What happens when you print from Safari -- does the same thing happen?

If this is particular to Chrome, then we'll want to bisect across builds to find where this broke.

Comment 2 by tsobczak@google.com, Sep 16 2016

Printing from Safari was successful.

Comment 3 by shrike@chromium.org, Sep 21 2016

What did the print preview screen look like? And is this still happening?
Project Member

Comment 4 by sheriffbot@chromium.org, Sep 29 2016

Labels: -Needs-Feedback Needs-Review
Owner: ccameron@chromium.org
Thank you for providing more feedback. Adding requester "ccameron@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Components: Internals>Printing
Labels: -Needs-Review Needs-Feedback
Owner: ----
Can you also share the document you are trying to print from Drive?
Status: WontFix (was: Unconfirmed)
Closing for lack of response for almost two months. Please reopen if you have more info/responses to c#3 and c#5.
I imagine this is a duplicate of bug 649775, but we can't know for sure without more information.

Sign in to add a comment