printing fails with "Empty Print File!"

RESOLVED EXPIRED

Status

()

Core
Printing: Output
RESOLVED EXPIRED
13 years ago
12 years ago

People

(Reporter: Thomas Roth, Unassigned)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 MultiZilla/1.6.4.0b
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616 MultiZilla/1.6.4.0b

Printing of any page from different PCs running SuSE-Linux 8.2-9.1 using Mozilla
1.6-1.72 as well as 
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3
Thunderbird version 0.7.3 (20040803)
to a SuSE-Linux8.2 Cups 1.10 print server fails with the message "Empty print
file!" (This is the cups error message, the printers (HP and Lexmark Laser
printers) never see the file. The same error occurs when first printing to a
ps-file and the sending it to the print server.


Reproducible: Always
Steps to Reproduce:
1. Load any web page/ email (plain text / html) 
2. Print it to file / kprinter / printer queue
3. check printout

Actual Results:  
Cups displays "Empty print file!", printing aborted

Expected Results:  
My guess: Send valid postscript

Comment 1

13 years ago
Thomas, first of all, what is the name of the printer you're printing to.
Specifically, when you select File->Print, what appears in the "Printer Name" field?

Second, what is the exact print command you're using? Select File->Print and
click on the Properties button.
(Reporter)

Comment 2

13 years ago
(In reply to comment #1)
> Thomas, first of all, what is the name of the printer you're printing to.
> Specifically, when you select File->Print, what appears in the "Printer Name"
field?
> 
> Second, what is the exact print command you're using? Select File->Print and
> click on the Properties button.

The name of the printer is always 'PostScript/default' , printing directly as
well as printing to file.
In the Properties, I can use 'kprinter', 'lpr -P<name_of_queue>' or the mozilla
default,
'lpr ${MOZ_PRINTER_NAME:+'-P'}${MOZ_PRINTER_NAME}'
I have  to add that the ps-file produced by printing to file is perfectly
readable in ghostview & friends. 

Comment 3

13 years ago
This may be a duplicate of bug 222624. It could be that the "empty print file"
is from a failed attempt to filter mozilla's postscript somehow.

Thomas, could you test a recent trunk build of mozilla or firefox (or one of the
mozilla 1.8 alphas) and see if this is still a problem?
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.