Open Bug 1084327 Opened 11 years ago Updated 3 years ago

mozilla print blank PDF files

Categories

(Firefox :: PDF Viewer, defect, P3)

Product:
Firefox
Component:
PDF Viewer
Version:
27 Branch
Platform:
x86_64
Windows 7
Type:
defect

Tracking

()

People

(Reporter: vruiz, Unassigned)

References

(Regression)

Details

(Keywords: regression, Whiteboard: [pdfjs-integration][pdfjs-printing])

Attachments

(1 file)

mozilla.pdf
78.53 KB, application/pdf
Details
Attached file mozilla.pdf —
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.104 Safari/537.36 Steps to reproduce: When I open some PDF files with the integrated PDF viewer, I can view the file correctly. However, when I print the document it prints a blank page. I have the problem from mozilla 29 update. If I try to view the PDF with the acrobat reader addon, then the pdf prints correctly. If I print the pdf on IE or Chrome, the pdf also prints all content correctly. I know that there is some similar bug (https://bugzilla.mozilla.org/show_bug.cgi?id=1003707) but theoretically this bug is resolved and I have the issue on all versions from 29 to 33, printing on any printer (ricoh, hp...). The PDF are generated from a RICOH printer, we have update the printer firmware but the problem remains. Actual results: Prints a blank page Expected results: Print all the PDF content. I attach the PDF file for test purposes.
I tried to print the PDF with MS XPS Document Writer and PDF Creator, it works but the printed file has 2 pages instead of one, and the 2nd one is blank. I didn't test with a real printer.
Component: Untriaged → PDF Viewer
Yes, with virtual printers also works for me (and also it adds a blank page in my case, and if the document has two pages, pdf creator creates a pdf with the two pages and an extra blank page) but when I try in a real printer I only obtain a blank page. We have a lot of machines, W7 x64 or x32, windows server...the problems is on all the machines. It seems that the problem is the way that the printer generates the pdf, but mozilla is the only browser that has the problem... Thanks for your help!
Blank page printed at the end of some documents is tracked in bug 1020878. The attached document is printed as a white page for me too, I have a Samsung ML-2850 Series printer. With other pdf documents seems to work fine. I could reproduce the issue in Firefox 34b1, Aurora 35, Nightly 36, but also in Firefox 28 beta 8, so this doesn't seem related to bug 1003707.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: 29 Branch → Trunk
We have detected the problem when upgrading from version 19 to 29, so I didn't test on version 28... We use mozilla in an enterprise environment, so we can't update every version. We are thinking about use ESR version, but I suppose that it has the same issue with pdf files... I don't understand why mozilla doesn't give support to a centralized managed browser (I know the frontmotion option, but I think that mozilla must release an official version...)
Petruta, did you try to print https://bugzilla.mozilla.org/attachment.cgi?id=8506824 with a version prior to 27 (where bug 1020878 appeared), like FF26?
I can print the attached pdf to Canon BJ M40 bubble jet printer if I turn on "Print Background (colors & images)" in Page Setup.
Loic, it prints fine using Fx26. Alice, I can't find that option for my printer.
Keywords: regression
(In reply to Petruta Rasa [QA] [:petruta] from comment #7) > Loic, it prints fine using Fx26. > Alice, I can't find that option for my printer. Press Alt key > File > "Page Setup" > "Format & Options" tab
So it's regressed somewhere in FF27, the PDF should be printed normally without turning on the option "Print Background (colors & images)" in the print setup.
(In reply to Alice0775 White from comment #8) > Press Alt key > File > "Page Setup" > "Format & Options" tab Thanks! :) It still prints a white page with this option on (I also restarted the browser).
Alice, I suppose that you refer to the Mozilla Menu option in Page Setup. I had this check unmarked, but now I have marked this check and the printer continues to printing a blank page. Like Petrusa, I also restarted the browser. Maybe are you using the acrobat reader add-on (instead to view the PDF? If I use the acrobat reader addon the pdf prints perfectly...
(In reply to vruiz from comment #11) > Alice, I suppose that you refer to the Mozilla Menu option in Page Setup. I > had this check unmarked, but now I have marked this check and the printer > continues to printing a blank page. Like Petrusa, I also restarted the > browser. > > Maybe are you using the acrobat reader add-on (instead to view the PDF? If I > use the acrobat reader addon the pdf prints perfectly... No,Not acrobat reader. Printed from Build-in pdf.js https://hg.mozilla.org/mozilla-central/rev/ae1dfa192faf Mozilla/5.0 (Windows NT 6.1; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0 ID:20141017030201
So, I don't understand why only works for Alice... Any idea? The "print background..." option doesn't work for me, What can I do now? Is there any way to escalate the bug to find the problem's source?
1. You should find a regression window.
Keywords: regressionwindow-wanted
Petruta said it works fine in FF26, and Alice too, so we should be able to find a regression in FF27.
Priority: -- → P2
Whiteboard: [pdfjs-c-integration][pdfjs-d-printing]
Hi, I suppose that "find a regression window" means to find in what version the problem starts... I have tested all versions from 19 to 29. The problem starts in version 27 and it remains until the newest version, 33. I also tested ESR version (31), frontmotion msi's and normal mozilla installation downloaded from official site. The last test was change the mozilla language. Usually we use the catalan language, but I've test english and spanish versions and the problem remains. "Print Background..." options doesn't work. Next step? Thanks everyone for your help
Vruiz, thanks a lot for this start! It's great to see that we know that 27.0 is the first affected version. The next step you should do is to check the beta versions of 27.0, so that we can reduce the possible amount of changes drastically. I would propose you try it first with 27.0 Beta 1, and if that works bisecting the remaining beta releases. All of them you can find here: ftp://ftp.mozilla.org/pub/firefox/releases/ Especially the beta 1: ftp://ftp.mozilla.org/pub/firefox/releases/27.0b1/
Version: Trunk → 27 Branch
Hi, I've just tested, and the version 27b1 has the problem.
vruiz, did you test the version 26? http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/26.0/
Yes, I did it. In version 26 the pdf is printed perfectly. Regards
Well, as you're able to reproduce the issue, you can install the tool mozregression on a test machine (see http://mozilla.github.io/mozregression/ for details) and find a regression range. No need to bisec, just stop when you got the pushlog in the console (paste the console output here). FF27 nightlies started in mid-Sept. 2013, so --good=2013-09-01 is a good start.
(In reply to vruiz from comment #18) > I've just tested, and the version 27b1 has the problem. Alright. So the problem has been introduced in Aurora and Nightly builds for the 27.0 release. Would you mind continuing the search for the regression range? If yes here some additional information: Given the release calendar (https://wiki.mozilla.org/RapidRelease/Calendar) we have to check the range: merge date central aurora beta release date release 2013-10-28 Firefox 28 Firefox 27 Firefox 26 2013-10-29 Firefox 25 2013-09-16 Firefox 27 Firefox 26 Firefox 25 2013-09-17 Firefox 24 Range: 2013-09-16 - 2013-10-27 I would suggest that you directly start with Nightly builds and check the following two: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2013/09/2013-09-18-03-02-02-mozilla-central/ http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2013/10/2013-10-28-03-02-05-mozilla-central/ In those folder you find the win32.zip file, which you can extract for testing. Hopefully the first build should work fine and the latter should fail. Once we have that information we can continue to find the exact Nightly build.
Hi! Well, finally I've used the regression tool to find which Nightly version started the problem. I ran the command: mozregression --good=2013-09-16 --bad=2013-10-28 --bits=32 And started to test version to version: 07-10-2013 -> OK! 17-10-2013 -> OK! 22-10-2013 -> OK! 25-10-2013 -> OK! 26-10-2013 -> WRONG!!!! So I paste here the last part of the log: Got as far as we can go bisecting nightlies... Ensuring we have enough metadata to get a pushlog... Last good revision: 2f2a45f04e7c (2013-10-25) First bad revision: ef3f5669b53e (2013-10-26) Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=2f2a45f04e7c&tochan ge=ef3f5669b53e ... attempting to bisect inbound builds (starting from previous week, to make su re no inbound revision is missed) Getting http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2013/10/2013-10-1 8-03-02-06-mozilla-central/firefox-27.0a1.en-US.win32.txt Getting inbound builds between 4e7d1e2c93a6 and ef3f5669b53e Oh noes, no (more) inbound revisions :( do you want to bisect further by fetching the repository and building? (y or n) I have the tool running in a virtual machine so it is waiting for a next step. Have you got enough information? If I continue with the bisect process, what versions will be tested? Sorry, this is the first time that I use this tool and I have no idea if it is a good idea to continue with the bisec process. Thank you very much!!
No need to bisect, thanks.
My guess is that it regressed in bug 811002.
Blocks: 811002
Keywords: regressionwindow-wanted
But this bug appears as fixed...Can I do anything else? Thanks
(In reply to vruiz from comment #26) > But this bug appears as fixed...Can I do anything else? Thanks I was saying the regression has been probably introduced in bug 811002.
Flags: needinfo?(bas)
So...What's the next step? Sorry for my ignorance, but I don't know how the bugs are solved. The bug is in some type of queue waiting to be solved? It will be solved in proper versions? I suppose this post will remain open until the bug will be solved, won't it? Thanks for your help. I won't disturb anymore, I promise :P
(In reply to vruiz from comment #28) > So...What's the next step? Sorry for my ignorance, but I don't know how the > bugs are solved. > > The bug is in some type of queue waiting to be solved? > It will be solved in proper versions? > I suppose this post will remain open until the bug will be solved, won't it? > > Thanks for your help. I won't disturb anymore, I promise :P It's in the dev queue, but I guess Bas has some more important tasks about OMTC to fix before investigating this bug.
I'm hitting this bug in Firefox Nightly version 42.0a1 on Mac OS X 10.10.4 today. Even my colleague had the same issue with FirefoxDeveloper version. When I view it online I can see the content of the PDF fine, but when I print it I see blank page.
Using Firefox Nightly version 42.0a1 on Mac OS X 10.10.4. The whole document (I've tested 2 pages up to 150 pages) prints out blank pages. If I save as PDF and then print, the file does gets saved successfully.
I'm experiencing this when trying to print my Eurostar ticket PDF (Nightly 42.0a1, Mac). 'Saving to PDF' and 'Open in Preview' also result in blank pages. Printing the same PDF from my Stable (35.0.1) works fine.
Bug not apparent in v39.0
I can also reproduce this issue with the attached PDF.
Printing a pdf produced by a third party app using pdf.js we are getting a white page. FF version 40
Also with FF ESR 38.2.1
(In reply to zacky from comment #35) > Printing a pdf produced by a third party app using pdf.js we are getting a > white page. FF version 40 Could you attach such a PDF to the bug report, please.
Flags: needinfo?(zacky)
Used for testing the same pdf attached to this bug by vruiz on top of this page.
Flags: needinfo?(zacky)
This seems to work fine for me for production on windows, could you confirm?
Flags: needinfo?(bas)
On Win XP, I succeeded to print the PDF attached to the bug report with FF43 and printer HP Officejet Pro 8610.
Hello, I still have the problem Windows 8.1 pro 64 Firefox 50.1.0 On a specific file (professional healthcare dispatch, any - APM International), I get 1077 blank pages. Regards
Hello (bis) I've the save problem with the nightly build 53.0.a1 20170109030209 Regards
hello (ter) Sorry for the inconvenience. I found the solution there : https://support.mozilla.org/en-US/kb/fix-printing-problems-firefox? Several printer issues can be resolved by resetting Firefox's printer settings: In the address bar, type about:config and press Enter. The about:config "This might void your warranty!" warning page may appear. Click I accept the risk! to continue to the about:config page. In the Search field, type print_printer. Right-click on the print_printer setting and select Reset. Click the menu button New Fx Menu and then click Exit Close If this can help others. Regards
Moving to p3 because no activity for at least 1 year(s). See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Moving to p3 because no activity for at least 1 year(s). See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
No longer blocks: 811002
Regressed by: 811002
Has Regression Range: --- → yes
Whiteboard: [pdfjs-c-integration][pdfjs-d-printing] → [pdfjs-integration][pdfjs-printing]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: