198094 - No printing at all for any web page in a HP OfficeJet v40 printer.

Status: RESOLVED DUPLICATE of bug 212829

(Core :: Printing: Output, defect)

Description

[Marco Avila]

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

Any web page that is tried to be printed by going to Print in the File menu is
not Printed in the HP OfficeJet v40 printer, the menu for printing appears, the
printer begins to make the noise it's going to begin to print but after that
nothing happens Moreover, when you click on the button on the task bar by
checking the Document name the Status appears as "prinitng".

Reproducible: Always

Steps to Reproduce:
1. Browse to any web pages (http://home.netscape.com)
2. Go to File -> Menu -> Print
3. Press ok for printing

Actual Results:  
The printer is not printing.

Expected Results:  
Printing the document

I use a IBM ThinkPad T20 with 384 MB RAM, Service Pack 3, Pentium III at 700
Mhz, the version of Mozilla is 1.2.1, Windows 2000, a Belkin Hub 2.0 USB PCMCIA
card that connects the printer.

Comment 1

[Hodor!]

Probably the same as bug # 212829, see my comments on that bug

Comment 2

[Steve Fetter]

I experience this bug also with an HP OfficeJet G55 and
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624

The print dialogue box comes up, followed by a box that says "printing" which
gives the percentage sent. The printer initializes as if it's going to print
(the print head moves into position), but the printer icon does not appear in
the system tray and nothing is printed. After a long pause, the print head moves
back into the standby position.

I had this problem with a previous version of Mozilla; installing an updated
printer driver did not fix the problem. 

All web pages print fine with IE on same computer/printer. All Windows
applications work fine. Printing to a file with Mozilla using Adobe Distiller
(and then printer from Acrobat Reader) works fine, too.

This is not the same as bug as those in reports 181213 or 195065--there is no
error message. Also, unlike the comment in 212829, there is no print process
chewing up CPU time and no need to reboot.

Comment 3

[Asa Dotzler [:asa]]

*** This bug has been marked as a duplicate of 212829 ***