User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0

Steps to reproduce:

I opened a PDF file and clicked on the printing icon

Actual results:

The printing window appeared, but when I clicked on the button "Imprimer" (I am French), the window disappeared, the windox "Preparing printing" appeared briefly and disappeared, and the printer received nothing. It happens each time I try.

Expected results:

The printer should have printed the document I was viewing.

To clarify, are you viewing the PDF in Firefox or an external application such as Acrobat?

(In reply to Emma Humphries, Bugmaster ☕️🎸🧞‍♀️✨ (she/her) [:emceeaich] (UTC-8) needinfo? me from comment #1)

To clarify, are you viewing the PDF in Firefox or an external application such as Acrobat?

In Firefox. I have to save the doc and edit it with Acrobat to print it, then it works fine. In fact, whatever I want to print with Firefox, it just does not work, and I have to load the doc in another app such as LibreOffice, Acrobat or NotePad to print.

This sounds very similar to https://bugzilla.mozilla.org/show_bug.cgi?id=1630095

europ33, can you please test using mozregression to find exactly what changed which broke printing for you? https://mozilla.github.io/mozregression/ has information about how to download and run Mozregression. The tool will download different builds of Firefox for you to try, and after about 10 different builds it should be able to tell the exact change which caused printing to stop working for you. This would be of tremendous help to us.

Also, are you able to download a build of Firefox 76 Beta? Starting in Firefox 76 we will track printing errors through telemetry. Please download Firefox 76 and see if you are still having issues printing. If so, then can you go to about:telemetry, click on Scalars, and search for "printing"? Please let us know what errors are listed for you under the "printing.error" scalar.

I installed Firefox 76 Beta, and it works OK. Many thanks.

Resolving per comment #5; without error information, we can't do anything more here. Happily it's resolved for the original reporter. If the problem re-appears, hopefully with more details we can investigate further.