Closed
Bug 263295
Opened 20 years ago
Closed 19 years ago
CUPS print queue defaults not read by Xprint
Categories
(Core Graveyard :: Printing: Xprint, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: andrew.talbot, Assigned: masaki.katakai)
Details
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-GB; rv:1.7) Gecko/20040618 Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-GB; rv:1.7) Gecko/20040618 We have our printers running under CUPS. When you go to the "Print" pop up window (print button or File -> Print) and click the properties button for the selected printer, the printer defaults set by CUPS are read as the defaults for Xprint to use. For example, we have one print queue set to "duplex" by default under CUPS but the properties of this printer under Xprint default to "simplex". You can then select "duplex" from the drop down list of options for the printer in Xprint. Reproducible: Always Steps to Reproduce: 1. Set your CUPS print queue default to "duplex" 2. In Moz, File -> Print 3. Investigate the default printer properties by pressing the "properties" button Actual Results: The queue default of "duplex" is not recognised and "simplex" is displayed. Expected Results: The queue defaults should be shown in the properties pop-up.
Comment 2•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 3•19 years ago
|
||
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
Closed: 19 years ago
Resolution: --- → EXPIRED
Updated•16 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•