Open Bug 1399131 Opened 8 years ago Updated 3 years ago

[Error] Firefox ESR 52.3.0 Prints a blank page with an error message

Categories

(Core :: Printing: Output, defect, P3)

52 Branch
defect

Tracking

()

UNCONFIRMED
Tracking Status
firefox57 --- wontfix
firefox58 --- wontfix
firefox59 --- ?

People

(Reporter: mvalenti, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 Build ID: 20170802111520 Steps to reproduce: Currently using Firefox ESR 52.3.0 in Windows 10. Tried to print from the browser. Also, use Firefox ESR 52.3.0 in Windows 7. Printing works with no errors. Installed Firefox ESR Version 49 and the latest FF(non ESR) on windows 10. Printing works with no errors. Actual results: Every time you print from FF ESR 52.3.0 you receive the printer error popup " An error occurred while printing" and a blank page print job is sent to the printer. I've reset the printer settings in about:config. Refreshed the browser. Started the browser in safemode with all add-ons disabled. Restarting the browser worked until the computer is rebooted. Now that option no longer works. FireFox ESR 52.3.0 is a fresh install on a brand new machine. The issue is windows 10 and this version of FF ESR.Can someone help me with this issue? Expected results: What should happen is when you select the print option it should print without an error message. It should print the content and not a blank page.
Component: Untriaged → Printing: Output
Product: Firefox → Core
Priority: -- → P3
Add more information. This Version of FireFox 52.3.0 ESR is use on all college campus computers. All users with Windows 10 and this version of FF is experiencing this issue unfortunately.
We have similar problem after the update to the latest version (56.0.1) OS: Windows 2008 Server R2 Brand new, non-admin user with RDP session (it's the same with any non-admin user) Print - blank page Print preview is ok, when clicked on Print: "An error occurred when printing." and there is a blank page again.
It might be helpful to see your printer settings. Can you open the page about:support , click "Copy text to clipboard", paste that into a text file, and then attach that file here? Also, can you check what page size is set in the print dialog?
Summary: Firefox ESR 52.3.0 Prints a blank page with an error message → [Error] Firefox ESR 52.3.0 Prints a blank page with an error message
This bug seems to persist until the latest Firefox 60.0.2: https://bugzilla.mozilla.org/show_bug.cgi?id=1468465 https://bugzilla.mozilla.org/show_bug.cgi?id=1451507 @Mia Valentini and EY: Are you using Intel Graphic drivers and is hardware acceleration enabled? If yes, disable it (about:preferences, restart required), try to print again and post the results here.
Flags: needinfo?(bobowencode)
Flags: needinfo?(bobowencode)
Update on this FF issue. To answer a previous question, Yes, our machines have Intel Graphic driver's and no hardware acceleration is not enabled. Since I updated to the Windows 10 build 1803 we are no longer having the printer error and blank page print out. I tried to duplicate the problem multiple times after the windows update and Lo and behold, the problem went away. FF versions 52.9.0esr(64 bit) and 60.1.0esr (64bit), both now print without an issue. There is an issue with FF esr and Windows 10 build 1607, 1709. The solution seems to be to update to Win10 build 1803. What I can do is add another comment and run the print test on a Win10 build 1709 and send you the About:Support info. See if this helps you figure out why FF ESR is having issues.

I have the same issue with Firefox 68.10.0esr (64-bit) on Windows 10 Build 1809, Intel HD Graphics 4000 with driver version 9.17.10.4229 (latest available for this graphics card).

I moved my profile folder from Windows to Linux recently, which fixed the described printing bug for me, but the problem on Windows persisted for me on FF68ESR on WIndows.

You can remove me from the needinfo list.

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.