Box "Printer failed when starting the document."




17 years ago
14 years ago


(Reporter: mrosiak, Assigned: rods)


Windows 2000

Firefox Tracking Flags

(Not tracked)




17 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826

This is a random problem. E.g., had printed many times before, this morning. At
other times, got this message on first printing. Sometimes closing and reopening
browser heals it. Can take same URL to IE or Netscape 4.x and prints OK.

Reproducible: Sometimes

Steps to Reproduce:
1.So far, have not identified any particular pattern or cause.

Comment 1

16 years ago
I get this bug as well, except that sometimes it is "Printing failed when
completing the page" instead of "Printing failed when starting the page".

It will always leave a stub in the printer queue, permanently flagged as
"Spooling", with a few hundred bytes.  That stub will always be there until you
go in and manually delete it.  Fortunately this sub does not interfere with
future print jobs.

Printing from Internet Explorer works fine.

If it is very hard to fix this bug, I would love to see at least a more detailed
and better error message.  This will allow future bug reports to give better
information.  I recommend that the exact point of failure be listed in the error
message box, so that people who know the source can use the error message to go
back to the source and learn where the error occurred at and what caused it.
Summary: Box "Printer failed when starting the document." → Box "Printer failed when starting the document."

Comment 2

15 years ago
This works for me now, as of Firefox 0.8 (on Windows 2000)!  Printing now works
correctly.  I have not been able to reproduce the error at all anymore.  No
change to my printers or printer drivers were made....
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
You need to log in before you can comment on or make changes to this bug.