Closed Bug 452243 Opened 17 years ago Closed 15 years ago

Printing not possible if no default printer selected

Categories

(Firefox :: General, defect)

x86
Windows Vista
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: jan.n.klug, Unassigned)

Details

(Whiteboard: [CLOSEME 2010-11-01])

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1a2pre) Gecko/20080826034105 Minefield/3.1a2pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1a2pre) Gecko/20080826034105 Minefield/3.1a2pre If printers are installed under Windows Vista, but no default printer is selected, Firefox comes up with a message, that no printer is installed. This happens e.g. after using remote desktop (printers are still installed, but no default printer is selected, even if it was before). Microsoft Office opens the printer dialog with an empty printer field. You can then select the desired printer from the drop down menu. Reproducible: Always Steps to Reproduce: 1. Somehow delete your default printer. 2. Open Firefox 3. Try to print a webpage Actual Results: "No printer installed" dialog appears Expected Results: printing ialog appears with no printer selected as in MS Office.
This is a mass search for bugs which are in the Firefox General component, are UNCO, have not been changed for 500 days and have an unspecified version. Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.
Whiteboard: [CLOSEME 2010-11-01]
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.