Firefox Quantum prints blank pages. Tested on 8 dif Windows 10 PCs in dif locations to different printers + pdf printing. Tried reset reinstall - no help.
I have tried every fix suggested in the forums. Nothing helps. FF Quantum just prints blank pages. Even an uninstall, delete everything in appdata etc. and a reinstall does not work. FF Quatum 57 and 57.0.1 running under multiple Windows 10 PCs at various update levels all have the same problem. I bulit up one PC from scratch - new OS install, new FF Quantum install, Nothing else. Same issue. Won't print to any printers, or print to pdf programs. Just blank pages. HP, Dell, Microsoft print to PDF, Nitro, etc.
所有回复 (4)
When I do a restore, FF will print out the text from the restore titled "Sorry. We’re having trouble getting your pages back." but as soon as I try to print a web page, any web page, without even closing and relaunching FF, it comes out blank. 32 bit version does the same thing as the 64 bit version.
Still no help from anyone at Mozilla. I'm managing about 100 Windows 10 PCs and my friend manages another 200 or so. Neither of us have been able to fix this issue. Our work around is to run FF 56, which prints just fine, but for security reasons we will have to migrate to Chrome if this issue is not fixed fairly soon.
Not able to replicate it over here, I'd first go an update your printer driver and try resetting FF by typeing "about:support" then "refresh firefox" on the top right. Than restart...
Make sure Firefox has the permissions required on your network, in windows it's profile permissions to print and has access to the network/not blocked by firewall or anti-virus. 300 secluded cases like that is pointing to something misconfiguered on your network or a shared older plugin/extention/addon they all share, Firefox 57 is not compadible anymore with the older XUL extentions if that's what your are reling on for something.
I did all that and it didn't help. Printing didn't even work in safe mode. And it didn't work when using print to PDF (Microsoft or Nitro versions).
I fixed the problem by double-clicking the browser.tabs.remote.autostart.2 preference to switch the value from true to false. After a restart, printing worked.
But I was also able to fix it in one PC by changing the dom.ipc.processCount preference from 4 to 1. What is interesting about this fix was that I had both the 32 and 64 bit versions of FF installed on that PC, The 32 bit was on FF 56 and printed while the 64 bit was on FF 57.0.2 and did not.
I opened the 64 bit version and changed dom.ipc.processCount preference from 4 to 1. I then closed and restarted the 64 bit version of FF 57.0.2. Printing worked - but amazingly, the dom.ipc.processCount preference had been reset back to 4. I somehow had printing working with no apparent changes to any FF parameters.
This does not work when you only have one version of FF installed on your PC.