Closed
Bug 187708
Opened 23 years ago
Closed 20 years ago
Printing queues but will not print for HP PSC 750 and all Windows printing is then corrupted
Categories
(Core :: Printing: Output, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: bugzilla, Assigned: rods)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
This appears to be similar to bug 142045 (closed), which I was unable to
re-open. Apparently the bug is still there. This bug exists in Mozilla version
1.2.1 under Windows 2K SP3 with latest drivers for HP PSC 750 printer using Port
DOT 4_002 (USB).
Additional information: If the printer properties (Advanced tab) is set to
"Print directly to printer" rather than spool, the following popup box appears:
"Printing failed when completing the page". The item still appears in the print
queue (nothing prints), but for me (either way) nothing will print anymore from
any other applications after attempting a Mozilla print (print items will still
be added to queue though). Mozilla doesn't crash and can still surf the web.
The only way to get the printer to work again (for any application) is to remove
the printer drivers and then re-install the printer drivers again. Only Mozilla
has the power to corrupt the printer - pre-Mozilla printing works good.
Reproducible: Always
Steps to Reproduce:
1. Open any web page with Mozilla
2. File / Print
3.
Actual Results:
The printer no longer works until you un-install and re-install the printer
Expected Results:
Printed document, then removed document from print queue.
Comment 1•23 years ago
|
||
I have been having the identical problem with all versions since 1.0 rc3. I am
also win2000 sp3, but with hp officejet g55 (USB) I can get the ability to
print back by restarting windows. This does not occur on every page that I
print, about 60%. I have not found a common feature of the unprintable web
pages yet.
I have the identical same bug with Mozilla 1.4 on my Windows 2000 machine,
except that I have not found a single web page that 1.4 will print. I also get
the different behavior described by the submitter with spooling vs printing
directly to printer. Also, other print jobs queue up behind but cannot print.
I have discovered that you do not need to reboot to print again. You can clear
the print queue by cancelling the Mozilla generated item, and then killing the
hpoeng07.exe task in the process list. It will say that it is being cancelled,
but will not go away until you kill the task. This does allow other
applications to print.
I am Windows 2000 5.00.2195 SP2. I have old HP drivers and have not tried an
upgrade as everything else is working perfectly. I see that this is listed as
UNCONFIRMED. If I can be of any help in confirming this please let me know.
Well I too have the same exact problem (Mozilla 1.4, Windows 2000 sp4 here) with
an HP PSC-750 and latest available drivers (from HP's website).
I have changed my default print properties to spool documents and to print
spooled documents before non-spooled documents (ie. if a document is finished
spooling, it gets priority access to the printer compared to any document which
is not done spooling). Mozilla 1.4 begins to print, I hear my printer start up
and in the print jobs window I see the print job come up briefly, then it
disappears and nothing gets printed.
So while the "stuck print job" problem appears to no longer occur (for me) with
these settings in Windows, I can print nothing from Mozilla. Example, I was
just trying to print a map from maps.yahoo.com:
http://imgs.maps.yahoo.com/mapimage?MAPData=jZoJWvhyzy2dzJKLRdCQrovkoIWPAaLKD9IqB9Zc5K8xPrHQowkWkhUBvm92yHrlibFe0312pG4FmFxZttsuZFBfs8WFvPO3mOhIZyvtoNLr4AIHI2LKnGdqnkyeYNlbFck-
Mozilla starts the print job but as mentioned it vanishes from the print jobs
window and nothing comes off my printer. I then put the same URL into IE6 sp1
and it printed with no problems (I did not reboot nor did I kill/restart any
programs). It appears to be only Mozilla which cannot print, and it seems to be
Windows-specific or printer specific because I can print just fine from Mozilla
1.4 in OS/2 where I am printing to a PostScript device, not to this PSC-750 printer.
Don Eitner
Comment 4•21 years ago
|
||
Reporter - This issue may have been resolved in a more recent version of Mozilla
Could you please download a recent nightly build from
<http://www.mozilla.org/releases/nightly.html>, and then let us know if you
still see this problem?
Comment 5•20 years ago
|
||
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/
Comment 6•20 years ago
|
||
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.
Description
•