Closed
Bug 272669
Opened 21 years ago
Closed 14 years ago
can't print anymore on kyocera mita fs-1020d (postscript 3 capable) printer since mozilla 1.8a4
Categories
(Core :: Printing: Output, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: jochen, Unassigned)
Details
(Whiteboard: [closeme 2011-03-15])
Attachments
(1 file)
|
248.17 KB,
application/postscript
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a5) Gecko/20041201
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a5) Gecko/20041201
Since mozilla-1.8a4 (tested with a5 as well) I can't print from mozilla anymore
on my PostScript 3 capable printer. GhostScript still displays the file, and
after ps2ps I can even print it.
The file apparently gets transferred to the printer, which switches into busy
mode and stays there (waited 4 days, doesn't change)
my printer has 144mb of memory, so that shouldn't be a problem. i can't even
print most minimal pages... ideas?
Reproducible: Always
Steps to Reproduce:
1. print
2.
3.
Actual Results:
printer goes busy and remains busy
Expected Results:
printer prints
compiled mozilla myself, using gcc-3.4, no xprint or whatsoever, pretty standard
options (gtk2 toolkit)
Comment 1•21 years ago
|
||
Jochen, can you verify that printing to a file and then printing the file
produces the same problem? This would confirm that the problem is in the
generated file, rather than the way that mozilla is submitting it to the printer.
Could you produce a simple print job which has this problem and attach it to
this bug report?
Based on your description it sounds like the print job is executing endlessly
| Reporter | ||
Comment 2•21 years ago
|
||
Yes, it doesn't work no matter whether I print directly or using 'print to
file' and then print to file.
My print system is lprng with the ifhp filter, configured like this:
[ kyocera ]
status@
pjl@
pcl
ps
text
file_output_match = [
*postscript* ps
*pdf* ps \%s{pdf2ps_converter}
*pcl* pcl
*text* pcl
*gzip_compressed* filter \%s{gzip_decompress}
*assembler* raw
]
the kyocera printer language is identified as "assembler" by file, thus the
last entry. The printer understands pcl6 and ps level 3 as well.
note that printing about:blank works (want an about:blank.ps attached?)
Comment 3•21 years ago
|
||
Sigh. The sample prints fine on the fancy imagistics printer at my office, after
editing the job to change the paper size from A4 to good ol' american letter.
| Reporter | ||
Comment 4•21 years ago
|
||
I managed to work around this bug, by setting font.FreeType2.print to 'false'
A diff to a working version (FireFox 1.0) showed that the main differences in
the print out are the CID check code and fonts. A quick look at the mozilla
source code revealed that above option controls whether this postscript cid
stuff is inserted or not.
So probably it's a problem with the CID checking code or whatever else freetype2
inserts into my postscript files.
If you want me to debug this, tell me which files i should test-print :)
Comment 5•20 years ago
|
||
Jochen, could you test this again with a recent nightly build of mozilla or with
1.8b2 when it comes out? The freetype printing support was just updated; see bug
234182.
Comment 6•20 years ago
|
||
i have the exact same printer and the same hanging problem. sometimes web pages
do print, but then with all text removed. only some images and list bullets appear.
following the workaround in comment 4 and setting font.FreeType2.printing
(font.FreeType2.print doesn't exist) to 'false' works for me.
this is on ubuntu firefox 1.02 (which is supposedly version 1.04 backported).
- p
| Reporter | ||
Comment 7•19 years ago
|
||
with seamonkey 1.0 i seem to be able to print again (apart from a few other printing bugs...)
Updated•16 years ago
|
Assignee: printing → nobody
QA Contact: printing
Comment 8•14 years ago
|
||
do you see this issue still with version 3.6 or 4.0 beta?
Whiteboard: [closeme 2011-03-15]
Comment 9•14 years ago
|
||
No resonse to needed info. -> incomplete
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•