Closed Bug 212829 Opened 21 years ago Closed 19 years ago

won't print (HP OfficeJet G95)

Categories

(Core :: Printing: Output, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: koen, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624

For any webpage, if you want to print it (File->Print...), the "Print" dialog
box pops up, but clicking OK here doesn't send anything to the printer if I
select my HP OfficeJet HP G95 printer. Selecting another printer seems to work
fine however. The HP G95 works fine from any other Windows application. It looks
as Mozilla tries to initialize the printer, but no documents are printed. If I
look in the print queue, usually nothing seems to appear there. Only once did I
get an item in the queue, with the rather weird status "Deleting - Spooled -
Printing". At that time, choosing File->Print... within Mozilla produced an
error: "Printer error - Not available".

Reproducible: Always

Steps to Reproduce:
1. Open any webpage
2. Select File->Print...
3. Click OK

Actual Results:  
the printer wakes up, but nothing is printed.

Expected Results:  
print the open web page.

Printer: HP OfficeJet G95
Driver: 2.43
There seem to be a few other reports from OfficeJet users.  Checking the HP
website, driver version 3.1 was released early on in the year.  Can you upgrade
and see if that helps?
Summary: won't print → won't print (HP OfficeJet G95)
I have always had this same exact problem with an HP OfficeJet G85. All
applications (Notepad, Word, Excel, Palm Desktop, etc) print fine with no
problem. Attempting to print from Mozilla results in:
  a) Printer initialization noises
  b) Print job spools
  c) Nothing prints
  d) HP printer engine (hpoeng.exe) eats up 99% of CPU

System becomes extremely sluggish and unresponsive, and I must manually kill the
HP software.

I'm running Windows 2000 with SP4, though the problem has persisted since SP3.
The printer is connected to a JetDirect via the LAN in our computer room, with a
LinkSys BEFSR41 4-port switch.

Of note is my wife is running Windows 98 OSR 2 and has no problems printing from
Netscape 6 and Netscape 7. This has made me suspect the issue is driver related.
However, you can not download new drivers from HP's website, you must order an
actual CD to get the new drivers. Has anyone else obtained the latest HP drivers?
perhaps Related: Bug 187282
*** Bug 198094 has been marked as a duplicate of this bug. ***
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: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.