Closed
Bug 276109
Opened 20 years ago
Closed 19 years ago
Firefox & Mozilla will not print correctly with Samsung ML-1750
Categories
(Core :: Printing: Output, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: shancock, Unassigned)
Details
The fonts are skewed when printing any pages from the browser and the page is mostly unreadable. Graphics print OK. This occurs on both windows and linux version of firefox and mozilla. The will print to my Epson C82 fine. No other applications have this problem. Changing fonts make no difference.
| Reporter | ||
Comment 1•20 years ago
|
||
Problem occurs on SuSE 9.1, Fedora Core 2 & 3, Windows 2000. This has been happening for the last 2-3 releases (I'm sorry I don't have specifics). Firefox and Mozilla are the most current versions. The Samsung ML-1750 is using the PPD file: Samsung ML-1750 Foomatic/pxlmono file. The problem occurs when using kprinter or lpd or the default mozilla call for printing (on linux). The printer is a local printer to a linux workstation (SuSE 9.1) and other windows workstations on the intranet can print to that printer. I have not tried printing to the ML-1750 on windows as a local printer.
Summary: Firefox & Mozilla will not print correctly with Samsung ML-1750 → Firefox & Mozilla will not print correctly with Samsung ML-1750
Comment 2•20 years ago
|
||
Over to Printing.
Assignee: firefox → core.printing
Component: General → Printing
Product: Firefox → Core
QA Contact: firefox.general
Version: unspecified → Trunk
Comment 3•20 years ago
|
||
Can you go to 'about:config' and see whether 'freetype.printing' is set to true or false? I don't remember the exact pref. name. Just type 'freetype' and only one of several entries will have 'print' in its name.
Comment 4•20 years ago
|
||
In addition, the result of 'about:buildconfig' would help.
Comment 5•20 years ago
|
||
Stephen, are you still experiencing this problem?
Comment 6•19 years ago
|
||
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/
Comment 7•19 years ago
|
||
No response from the reporter to several requests for information.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•