Closed Bug 253917 Opened 21 years ago Closed 20 years ago

print job from Mozilla browser does not print and then blocks printer queue

Categories

(Core :: Printing: Output, defect)

x86
Windows 2000
defect
Not set
major

Tracking

()

RESOLVED EXPIRED

People

(Reporter: swissguy, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 When I try to print things straight from the Mozilla 1.5 Browser - things like driving directions from Mapquest.com or recipes or the like, the job goes to the printer queue, where the status goes from "spooling" to "printing"... However, the print job never starts actually printing. When this happens I have to uninstall the printer (an HP Officejet K60) and re-install it, as the faulty print job, sent from Mozilla, would otherwise block me from printing anything else. I was thinking this could this be a buffer problem - BUT when I printed these kinds of things from Windows IE 5.0, this was never a problem, and there I remember having been able to print 5Mb sized jobs without any problem. Any ideas, anyone? Thanx for any help y'all could give me... Reproducible: Always Steps to Reproduce: 1. Find a webpage with content to print 2. Click on the File - Print command 3. Clock on the OK button Actual Results: As before - the print queue is blocked. The print job is still there and any print job I launch after this ends up blocked from execution by the erroneous print job. Expected Results: Should have sent the print job to the printer and executed a hardcopy printout.
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/
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: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.