180602 - Printing page results in 16 leading blank pages, followed by a correct, but offset, page

Status: RESOLVED WORKSFORME

Description

[Karl Scriba]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021016
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021016

Printing page results in 16 blank pages being printed, followed by the correctly
laid out page.  However, even that page is offset to the bottom and the right.

Reproducible: Always

Steps to Reproduce:
1. Go to URL.
2. Select menu option: File -> Print.
3. Specify "PostScript/Default" as the printer.
4. Select "Print".

Actual Results:  
16 blank pages are printed, followed by the correctly laid out page, but even
that page is offset to the bottom and the right.

Expected Results:  
Print the requested page without leading blank pages and without offsets.

The printing system used is CUPS.
The Konqueror browser prints the page correctly and without incorrect offsets.
Options used with printing are to include the URL and the page title on the
printed page.
Printing the page to a PostScript file and then sending that PostScript file to
the printer results in the same problem.  However, viewing the PostScript file
directly does not show any leading pages.

Comment 1

[Mitch]

Reporter, you've just asserted that this is not a problem with mozilla ?

 "However, viewing the PostScript file directly does not show any leading pages"

This works fine for me (no leading pages) with LPRNG on Linux with cvs 20021117.

Comment 2

[Karl Scriba]

Other applications (e.g.: viewing and printing) may be "smart" enough to filter
out leading blank pages.  That would be fortunate, but an entirely separate issue.

Printing the PostScript file generated by Mozilla results in 16 leading blank pages.

Printing the PostScript file generated by Konqueror results in zero leading
blank pages.

I have tried this out with a number of different web pages, including the page I
am writing this on.  Same results.  Mozilla 16 - Konqueror 0.

Given that, I would contend that Mozilla (at least the latest released version,
1.2b) generated PostScript which is ... flawed.

Whether that is correct, I can't say.  Is there a way for me to upload a
PostScript file for analysis by somebody that understands PostScript?

Comment 3

[rods (gone)]

we don't work with CUPS as far as I know.

Comment 4

[Roland Mainz]

rods wrote:
> we don't work with CUPS as far as I know.

"CUPS" is just another spooler - I doubt this is the root of the problem...

Comment 5

[Kenneth Herron]

Karl, per your comment, you can upload files into bugzilla through the "create a
new attachment" link on this bug report's page. Uploading a postscript file that
demonstrates this problem would be helpful.

Comment 6

[Karl Scriba]

Created attachment 107796 [details]
Sample PostScript file that results in 16 blank leading pages

Printing any web page will result in 16 leading blank pages.
In the interest of minimize the size of the PostScript file I uploaded the
PostScript file for the web page http://cr.yp.to/djbdns.html, which is a text
only page.

This file was generated using the 1.2 release, but has the same problem as the
files generated/printed under the 1.2b release ... 16 blank, leading pages.

Comment 7

[Helmut Franzke]

There is a workaround and some information at:

http://sdb.suse.de/en/sdb/html/jsmeix_print-81-cups-formfeed.html

For me the mentioned change in cupsomatic works.

Comment 8

[Kenneth Herron]

Karl, could you take a look at the link from comment 7 and see if it helps you
with this issue?

Comment 9

[Karl Scriba]

Helmut, Kenneth, yes the fix referred to in comment #7 works.  No more "16
leading blank pages".

Comment 10

[Alexander Opitz]

Is the bug gone or need it fixed in mozilla?

Comment 11

[Karl Scriba]

The bug is gone.  The fix referred to in comment #7 resolved the matter.

Comment 12

[Kenneth Herron]

Resolving based on reporter's comment 11.