Okular v0.15.4 truncate the printing of the attached PDF, while Evince v3.6.0 do not. The printed output is always truncated after "[Vos réponses]" paragraph. The string "lundi 07 janvier 2013" is not printed by Okular, while it should and is actually printed out by Evince. This PDF has been automatically generated by the website of a French university: "Formulaire de pré-inscription au D.E.F.L.E." https://ficheiaweb.univ-tlse2.fr/WD120AWP/WD120AWP.exe/CONNECT/Candidature Reproducible: Always Steps to Reproduce: 1. Open the PDF with Okular 0.15.4 2. Print it out Actual Results: The output page is truncated after [Vos réponses] Expected Results: The date string should also be printed. Okular Version 0.15.4 (not listed in the "Version" scroll-down of bugzilla)
Created attachment 76279 [details] printing is truncated between "Vos réponses" and "lundi 07 janvier 2013"
I am not sure i understand the problem here. Are you saying that if you get the pdf you attached to this bug and print it (to paper or to pdf?) the "lundi 07 janvier 2013" line on the bottom of page 1 disappears?
Yes, on the printing to A4 paper of this PDF, the date "lundi ..." is not printed. However, I tested once again and it worked, so I understand the problem is only when I set the margins to 0mm: if I let them to default values (top=14.82, left&right=3.18, bottom=11.99mm) the printout is not truncated, if I set them to 0 (which I usually do because otherwise some millimeters of the top and/or bottom are truncated) for this PDF, it does truncate. I attach a new more complete PDF, on which the truncate location is always the same, as shown on this photos: - Broken if margins=0: http://imageshack.us/a/img16/2690/img20130107181230.jpg - OK if default margins: http://imageshack.us/a/img543/7703/img20130107181241.jpg
Created attachment 76283 [details] pdf_printing_truncated_with_olular-v2.pdf
From which PDF file does http://imageshack.us/a/img16/2690/img20130107181230.jpg come from?
It's from the second PDF attached: https://bugs.kde.org/attachment.cgi?id=76283
Interesting so you say that printing the same PDF file with different margins (changing the margins in the properties page of the Okular printing dialog) give you the broken and the working printouts?
Yes, exactly. For both margins of 0mm and 1mm (I didn't test other values; if there is any specific border-line value you want me to test, let me know) the printout of pdf_printing_truncated_with_olular-v2.pdf is broken exactly as shown on http://imageshack.us/a/img16/2690/img20130107181230.jpg
I'm not sure there's much we can do here, it seems your printer gets confused with small printer margings. I'm setting this bug back to unconfirmed from needsinfo since i got all the info i needed but i'm unsure this is our bug. Sorry i can't be of much more help and thanks for caring about Okular and reporting this bug, also glad that you can print the document with the default margins.
Which version of okular and cups are you using?
Okular Version 0.18.4 (from Debian Testing: 4:4.12.4-1) CUPS 1.7.2-1 I just tried again with the PDF attached, and the same problem happens: the last line ("lundi 07 janvier 2013 1/2") is not printed if I set all margins to 0. With Evince 3.12.1, with a custom paper size of A4 with all margins set to 0, there is no problem.
Cups 1.7.2 has a few regressions that unfortunately make stuff not work, i'll get this back to unconfirmed and once i get the cups people to fix the regressions we'll get back to this.
Isn't the fact that Evince does work well means that CUPS is not in fault here?
(In reply to comment #13) > Isn't the fact that Evince does work well means that CUPS is not in fault > here? No.
*** Bug 192189 has been marked as a duplicate of this bug. ***
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
At least I cannot reproduce the bug, so I guess you can close this issue. Thanks for your work.
Thanks for reporting back! I am closing this -- please reopen if the problem comes back.