Closed Bug 1485344 Opened 6 years ago Closed 6 years ago

[PRemotePrintJobChild] print.print_to_file does not work since 59.0+ versions

Categories

(Core :: Printing: Setup, defect)

61 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1471854

People

(Reporter: hosni.adala, Unassigned)

Details

(Keywords: regression)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36

Steps to reproduce:

On selenium 3.13 I open a firefox profile then I add the following options:
 profile.set_preference("print_printer", "PDF")
 profile.set_preference("print.always_print_silent", True)
 profile.set_preference("print.print_to_file", True)
 profile.set_preference("print.print_to_filename", "/tmp/file.pdf")

I try to print a file to a PDF silently. Everything works with the previous version of firefox (under 60 versions).



Actual results:

When I run a test I got this error in geckodriver.log:
IPDL protocol error: [PRemotePrintJobChild] Received an invalid file descriptor

The same workflow works with firefox 58.0.2



Expected results:

We should be able to print to a file silently.
Summary: print.print_to_file does not work since 60+ versions → [PRemotePrintJobChild] print.print_to_file does not work since 60+ versions
Summary: [PRemotePrintJobChild] print.print_to_file does not work since 60+ versions → [PRemotePrintJobChild] print.print_to_file does not work since 59.0.2+ versions
The problem occur since 59.0 firefox release
Summary: [PRemotePrintJobChild] print.print_to_file does not work since 59.0.2+ versions → [PRemotePrintJobChild] print.print_to_file does not work since 59.0+ versions
Unfortunately, I don't have Selenium to be able to test this, but I will set a component as a starting point. Also, this sounds like a regression.
Component: Untriaged → Printing: Setup
Keywords: regression
Product: Firefox → Core
Hmm, bug 220956 makes it look like print.print_to_file hasn't worked since basically forever. However, probably nobody noticed that bug should be closed when it was fixed at some point.

Looks like this is a duplicate of bug 1477909 though.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.