Closed Bug 143241 Opened 24 years ago Closed 24 years ago

Unable to print to network printers

Categories

(Core :: Printing: Output, defect, P1)

x86
Windows 2000
defect

Tracking

()

VERIFIED FIXED
mozilla1.0

People

(Reporter: brad, Assigned: rods)

References

Details

(Whiteboard: [adt1])

Attachments

(1 file, 1 obsolete file)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0+) Gecko/20020508 BuildID: 2002050807 Printing to a network printer always works for me using the 2002050705 build but always fails using the 2002050807 build. Printing to a PostScript printer configured to go to a file works. I don't have a local printer to test. I've tried removing my existing profile and starting from scratch to no avail. Reproducible: Always Steps to Reproduce: 1. Open the browser. 1. Try to print to a network printer. Actual Results: When I attempt to print any page from Mozilla to a network printer, I get one of the following two errors: "Printing failed for some reason." "There was an unexpected problem when printing." Expected Results: It should have printed.
You're lucky! I tried to print today and it rebooted my machine. Consistently. A simple text only page or a simple HTML page.
wfm using build 2002050904 on Win2k (trunk). I didn't test 20020508 though. Can you try again with today's build ?
WFM using both 5/8 branch build and trunk build (200250807) on Win 98.
Unfortunately, it still fails for me using 2002050904. I tried it using both my standard profile and the profile it creates by default if you don't have one. I've also tried eight different network printers here (different manufacturers, different servers, etc.), but the problem's the same for each. Other information that may or may not be relevant: We're using Microsoft Active Directory here.
please see if you are affected by this bug 130083 Also can this bug be a DUP ? http://bugzilla.mozilla.org/show_bug.cgi?id=142923
Regarding bug 130083: No, this bug doesn't affect me. My printers are network printers, and I don't have control over whether or not information gets spooled. Also, I'm running Windows 2000, not 98/ME. Regarding bug 142923: This bug looks completely different. Unlike the people affected by bug 142923, I see all my printers listed in the Print dialog box's dropdown list box; however, I can't print to any network printer. There were several changes to the printing capabilities submitted between the two builds I originally mentioned -- perhaps the trouble is in one of those? I've also tried the latest changes from CVS, but it still doesn't work.
what type of printer, how is it shared (ACLs?), what os is sharing it, what rights do you have to it, ...
Network printers I've tried (all of which fail): HP DeskJet 1120C HP LaserJet 4M Plus HP LaserJet 4Si/4SiMX PS Xerox DC 420/432/440 PS3 (three different ones) Apple Color LW 12/660 PS (configured to go to FILE:) The first four listed are on one server running Windows 2000; the last is on a coworker's machine running Windows 2000. All are shared using standard Windows sharing. I have "Print" permission, but not "Manage Printers" or "Manage Documents" permissions. I have not had problems printing from other applications. Mozilla's "Print Preview" looks fine.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Priority: -- → P1
Target Milestone: --- → mozilla1.0
I found the problem with help frmo Brad (thanks Brad). It is a simple string compare, but it completely messes up the detection of whether it is printing to a file or not. And this can cause the reverse effect of it asking for a file name when it shouldn't and vise-versus. (very very bad bug).
Keywords: nsbeta1
Whiteboard: [adt1]
Attached patch patch (obsolete) — — Splinter Review
Part of what was masking the problem was a missed checkin of a file. So this fix plus checking in the change to mozilla/layout/html/base/src/jar.mn as part of bug 115136. So the fix is this line: + if (_tcscmp(lpInfo[i].pPrinterName, aPrinterName) == 0) { I also removed the failure check after the calls to EnumerateNativePrinters because even if one fails, it doesn't mean the others will. So it should keep trying. The rest of the code is extra error checking that is all ifdef'ed out
Attached patch better patch — — Splinter Review
Same as before with the addition of: I renamed one of two methods that had the same name (to reduce confusion) and got rid of it's uneeded return code.
Attachment #83569 - Attachment is obsolete: true
Attachment #83572 - Flags: superreview+
This is regression fix for 115136
Depends on: 115136
Comment on attachment 83572 [details] [diff] [review] better patch r=dcone
Attachment #83572 - Flags: review+
fixed
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Keywords: adt1.0.0
Resolution: --- → FIXED
nsbeta1+
Keywords: nsbeta1 → nsbeta1+
Brad, please verify this bug in latest build...and mark verified-fixed if it works for you now...thanks...
Blocks: 143047
Keywords: approval
Whiteboard: [adt1] → [adt1] [Needs ADT + and a=]
Verifying as fixed on build 2002051504.
Status: RESOLVED → VERIFIED
adding adt1.0.0+ for checkin. Please get drivers approval before checking in. If you don't need the debug code on the branch, please don't check it in.
Keywords: adt1.0.0 → adt1.0.0+
Whiteboard: [adt1] [Needs ADT + and a=] → [adt1] [Needs a=]
Comment on attachment 83572 [details] [diff] [review] better patch a=chofmann,blizzard,shaver, blizzard,rjesup please check in to 1.0 branch asap to get this in rc3.
Whiteboard: [adt1] [Needs a=] → [adt1]
changing to adt1.0.1+ for checkin to the 1.0 branch for the Mozilla1.0.1 milestone. Please get drivers approval before checking in.
Keywords: adt1.0.0+ → adt1.0.1+
please land on the 1.0.1 branch. once there, remove the "mozilla1.0.1+" keyword, and add the "fixed1.0.1" keyword.
Keywords: mozilla1.0.1+
Attachment #83572 - Flags: approval+
fixed on branch
verified.
Keywords: verified1.0.1
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: