Closed Bug 324418 Opened 19 years ago Closed 13 years ago

printer generates LIMITCHECK error

Categories

(Core :: Printing: Output, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: normjen, Unassigned)

References

()

Details

(Whiteboard: [closeme 2011-03-15])

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

My Brother HL-5170DN printer is generating the following print error:
  ERROR NAME; limitcheck
  COMMAND; image
  OPERAND STACK; --savetype--

This is a repeatable error that only occurs in FireFox 1.5.  I have no problems printing in FireFox 1.07 or Apple's Safari.

Some web pages appear to print without any problem, like www.apple.com.  Others, like www.yahoo.com, generate the error.

I also get this problem if I use the Mac OS X print dialog box to create a PDF file, then try to print the PDF file.

I have contacted Brother and been through several rounds of resetting both the printer and my iBook.  I have also followed Bugzilla's recommendation by creating a new Mac OS X account (profile) and running off of that.

Hope this helps!

Reproducible: Always

Steps to Reproduce:
1.Launch FireFox 1.5 in Mac OS 10.3.9
2.Go to www.yahoo.com
3.Print to Brother HL-5170DN networked printer

Actual Results:  
Printer generates error page that reads:
  ERROR NAME; limitcheck
  COMMAND; image
  OPERAND STACK; --savetype--

Expected Results:  
I was hoping to get a print of the web page!

No problem repeating this process with FireFox 1.07 (what's changed between 1.07 and 1.5?) or Safari.
(In reply to comment #0)
> User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
> rv:1.8) Gecko/20051111 Firefox/1.5
> Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
> rv:1.8) Gecko/20051111 Firefox/1.5
> 
> My Brother HL-5170DN printer is generating the following print error:
>   ERROR NAME; limitcheck
>   COMMAND; image
>   OPERAND STACK; --savetype--
> 
> This is a repeatable error that only occurs in FireFox 1.5.  I have no problems
> printing in FireFox 1.07 or Apple's Safari.
> 
> Some web pages appear to print without any problem, like www.apple.com. 
> Others, like www.yahoo.com, generate the error.
> 
> I also get this problem if I use the Mac OS X print dialog box to create a PDF
> file, then try to print the PDF file.
> 
> I have contacted Brother and been through several rounds of resetting both the
> printer and my iBook.  I have also followed Bugzilla's recommendation by
> creating a new Mac OS X account (profile) and running off of that.
> 
> Hope this helps!
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> 1.Launch FireFox 1.5 in Mac OS 10.3.9
> 2.Go to www.yahoo.com
> 3.Print to Brother HL-5170DN networked printer
> 
> Actual Results:  
> Printer generates error page that reads:
>   ERROR NAME; limitcheck
>   COMMAND; image
>   OPERAND STACK; --savetype--
> 
> Expected Results:  
> I was hoping to get a print of the web page!
> 
> No problem repeating this process with FireFox 1.07 (what's changed between
> 1.07 and 1.5?) or Safari.
> 

I have EXACTLY this same problem; same printer. Not only does this happen in Firefox 1.5 but Camino 1.0 and SeaMonkey 1.0.
*** Bug 327460 has been marked as a duplicate of this bug. ***
Does this issue exists on trunk as well? Can you please try with a nightly Camino/Firefox/SeaMonkey build?
Component: General → Printing
Product: Firefox → Core
Version: unspecified → 1.8 Branch
Assignee: nobody → printing
QA Contact: general
(In reply to comment #3)
> Does this issue exists on trunk as well? Can you please try with a nightly
> Camino/Firefox/SeaMonkey build?
> 

Yes, just downloaded and used the Camino nightly build. Same problem.
(In reply to comment #4)
> (In reply to comment #3)
> > Does this issue exists on trunk as well? Can you please try with a nightly
> > Camino/Firefox/SeaMonkey build?
> > 
> Yes, just downloaded and used the Camino nightly build. Same problem.

OK, thanks. Hmm, so this happens on both branch and trunk...
Version: 1.8 Branch → Trunk
I have almost exactly the same printer, in the non-networked variety, HL-5150D.  (I bought it for its "recto-verso" printing capability.)  I don't experience this problem under 10.4, where I'm using the drivers that come with the OS.

limitcheck is a PostScript error.  Your printer may be running low on memory.  Try dropping the dpi to reduce complexity.

There are two Brother drivers available for this printer.  One of them sends PostScript to the printer, which rasterizes using its BR-Script interpreter.  The other handles rasterization on the computer.  This second driver is labeled "CUPS".  I recall that under 10.3, these drivers weren't bundled with the OS, but both were available from the manufacturer's web site.

I don't have trouble printing the yahoo page with either driver, but my printer's memory has been maxed out (168MB?), so it's got plenty of room to rasterize PostScript at 600dpi.
OK! Using the CUPS driver fixed this. I can now use Camino and print. At least in a one site test....Time will tell.

But....

The technologist in me wants to know why?

Why did this work in Firefox 1.07 but broke in Firefox 1.5 and Camino 1.0 and SeaMonkey 1.0?

What changed in these new apps?
We're probably outputting more complex PostScript than we had done in the past.  If you're a true hardcore technologist, print to a PS file in both 1.0.7 and 1.5.0.1 and see what's different.
Next:

In Windows 2000 this is even more of a problem. The error here says the error name is undefined and the command is -12345X@PJL.

Multiple error pages print until the job is cancelled. 

This was done with Firefox 1.501.

Solutions?
Assignee: printing → nobody
QA Contact: printing
do you see this issue still with version 3.6 or 4.0 beta?
Whiteboard: [closeme 2011-03-15]
No response to needed information. -> incomplete report
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.