Print Command Only Sets After Print Job.




14 years ago
13 years ago


(Reporter: drichard, Assigned: bugzilla)


Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

When using FF 1.0 on Linux, if you go into the printer manager and enter the
command for your printer (lpr -P <printer>) it only sticks from session to
session if you physically print.  If you enter the command, click OK and then
cancel out of the dialog the command stays for the current session but is lost
in future sessions.  We sent out directions for people to put in their commands,
and discovered that those users that didn't print within that session lost them

Reproducible: Always
Steps to Reproduce:
1. Open fresh Firefox session
2. Go into printer dialog area, and type in command to print.
3. Cancel out of physical print, restart FF and see command hasn't saved.

Expected Results:  
When you click [OK] to accept the entry of the printer command, it should save
it to your preferences.
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:
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.
Last Resolved: 14 years ago
Resolution: --- → EXPIRED
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs,
filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → preferences
You need to log in before you can comment on or make changes to this bug.