Closed Bug 343494 Opened 18 years ago Closed 13 years ago

Default printer selection sends the print job to the previous network printer even if not it is not mapped

Categories

(Firefox :: General, defect)

2.0 Branch
x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: bxk, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4

After printing once to a network printer and then moving to a location in which the previous networked printer is not available FireFox will by default print to the previous networked printers location.

Reproducible: Always

Steps to Reproduce:
1. Map 2 network printers
2. Select network printer A and print from firefox
3. Close firefox
4. Remove printer A mapping
5. Open Firefox
6. Select file --> print
7. Without selecting the drop down box click ok.  It will say have selected the last print in the list. Network Printer B if you only have 2 printers, for us it's Microsoft Office Document Image Writer.
8. Pick up printout Network Printer A
Actual Results:  
The printout goes to the wrong networked printer.

Expected Results:  
The printed document go to the network printer specified in the drop down box.

On application start set the default printer from systems default printer. 

The printout will go to the prefs.js's print.print_printer entry by default even if it is not in the list of printers.
Version: unspecified → 1.5.0.x Branch
Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!
Whiteboard: CLOSEME 07/14
I see this bug on both Firefox 2.0.0.14 and Thunderbird 2.0.0.14 on one user at our facility (might be more, but this person consistently moves back and forth between two sites, and runs into this consistently).  In fact, this user has a problem with the last printed printer not changing the printer selection consistently - they can open the application, it is pointing to printer A, she can select printer B and print to it; then going to a new message or page, go to print, and it is pointing back to printer A, not printer B.

This is NOT an issue on all systems.  What configuration settings can I look at to do comparisons between systems that exhibit this problem, and those that don't to determine what is going on?  Is there a way to prevent Mozilla FF and TB from remembering last printer at all, and always select to the default windows printer?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: 1.5.0.x Branch → 2.0 Branch
It's because the UNC of the last printer that was printed to is saved in the prefs.js file.

I've added a small application to our logoff.bat which finds all the firefox profiles and then cleans their prefs.js file of any lines that contain "print.printer" to mitigate this issue.
Whiteboard: CLOSEME 07/14
This bug is part of a query for Firefox bugs that have Status set to NEW, but have version field set to 2.0 or older and have not changed in over 800 days.

http://tiny.cc/forgottennewbugs

If you still see this bug, or if it is still valid with Firefox 3.6.10 or a firefox 4 nightly build, please update the version field and steps to reproduce.
I haven't had any users complain about this issue in quite a while.  I'm comfortable saying WFM at this point, but I'd prefer to have the reporter confirm this, and set if they agree.
Firefox 4.0 seems to have resolved the issue. 

In 4.0 when you print to a printer that is not the system default printer, such as network printer A, close the firefox, open firefox and select print network printer A is still selected as expected. If network printer A is removed from the system, the firefox print dialog window selects the default system printer from the list as is the logical behavior. 

Thanks for fixing it.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Glad it's gone. WFM though.
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.