Closed Bug 192542 Opened 22 years ago Closed 20 years ago

[ps] Physical printer hangs when accepting print job

Categories

(Core :: Printing: Output, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: dvschweiger, Assigned: rods)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030209 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030209 When I print a web page the printer hangs (hard hang, no way to make it work again using web page adminstration page. It needs to be turned off!!!!!!!!!!). Older Mozilla 1.2.1 works perfect with the same printer. GV has no problem to view both, but ps from new mozilla triggers excessive memory usage (200MB+). Reproducible: Always Steps to Reproduce: 1. Open web page in Mozilla (ANY!!). 2. Hit button "ok" in print request. 3. Printer gets the job and hangs quite immediately. Actual Results: Hard hang of printer, printer becomes unavailable to all users. Expected Results: Well, just a printed web page.
Flags: blocking1.3b?
Flags: blocking1.3?
Summary: Physical printer hangs when accepting print job → [ps] Physical printer hangs when accepting print job
Reporter: Using Mozilla's Xprint module should work perfectly with your printer - see http://www.mozilla.org/releases/mozilla1.0.2/#xprint :)
Not gonna hold beta for this.
Flags: blocking1.3b?
Reporter, what is the brand name and model number of your printer? What printer driver are you using? Are you using cups? Please try the following troubleshooting step: create a completely new profile. Then print the page at http://www.mozilla.org/ . Does that work?
*** This bug has been marked as a duplicate of 191684 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Flags: blocking1.3?
For what is it worth to comment here: 1.4rc2 on Linux, the problem still persist. The Postscript generated by the Postscript driver in Mozilla is not accepted unless it is filtered via Ghostscript to make it valid Postscript.
Clearly not a dup of a bug fixed in 1.3.... David, can you provide any info on which part of the PS breaks the printer?
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
David, what kind of printer (manufacturer and model) is this? Do you know what level of postscript it supports, or how much memory it contains? What ghostscript command line are you using to filter mozilla's output into something that can be printed?
HP Laser 4100N, HP Laser 9000HNS and Phaser 1235 print using PS module causes firmware hang with error 49.4c03 on the display, making a manual power cycle mandatory. Make sure you have the offending print job removed first. Otherwise the print job will be resend by the queue manager, leading into a endless loop Repeated attempts to print will make your system support staff busy, anoyed and **** ANGRY Workaround is to force CUPS to filter all Postscript print jobs to make it valid Postscrupt. Do not ask me how that works - I did not implement that myself
David (or anyone else), can you reproduce this with a current version of mozilla? There have been a lot of changes to the postscript generator since this bug was filed, and it's possible that the issue no longer exists. If someone can reproduce this, please attach a small print job that triggers the problem.
No response to the previous request. Resolving INVALID because I have no way to test on the specific printer. If anyone is experiencing a problem like this with a current version of mozilla, please open a new bug.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago20 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.