View Issue Details

IDProjectCategoryView StatusLast Update
0003484ScribusPrintingpublic2006-06-05 12:33
Reporterabrock Assigned Tojghali  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionno change required 
PlatformDesktopOSWindowsOS VersionXP Pro SP2
Product Version1.3.2 
Summary0003484: Printing Cause StackOverFlow Error on Printer
DescriptionWhen attempting to print document to Gestetner C7116, it always cause the printer to have an error. Instead of the document, I get page with the following printed message.

ERROR: stackoverflow
OFFENDING COMMAND: 7.9375

Following this is a bunch of numbers. No other app I use causes this printing problem on this printer. In fact, I can get Scribus to create a PDF file which I can then open with Acrobat and print to the printer.
Steps To ReproduceSame error and same printout each time I try to print document.
TagsNo tags attached.
Patch

Activities

jghali

2006-03-22 11:31

administrator   ~0009416

Last edited: 2006-03-22 12:09

May you make the two following tests for me:
- make a one page new document, place an image (jpg or tiff screen size only: 1024x768 for ex) and try to print that doc
- make a one page new document, place some text and try to print that doc
Do you have the stack overflow error in both cases? Thanks by advance.

jghali

2006-03-22 12:59

administrator   ~0009417

This printer seems to support PostScript. You may try to circumvent the problem by using a hidden ability Scribus has on Windows : printing on PostScript printer using pure GDI. To do so, when clicking the "ok" button in print dialog, keep the right shift key down. But beware : all colors are transmitted as RGB colors GDI having no support for CMYK colors as input.

abrock

2006-03-22 15:21

reporter   ~0009419

Ok, I did the two tests. The document with an image caused another printer error. This time the printer gave the following:

ERROR: limitcheck
OFFENDING COMMAND: filter

STACK:
/ReusableStreamDecode
-filestream-
-savelelvel-

The document with just text printed without any problems. I might note also that the document I tried printing when I first sent this bug notice is composed of a mixture of text, boxes, and lines.

As to the suggestion to circumvent the problem, I tried that with all the above documents and was able to print everything without any errors. So, how do I achieve printing documents without having to circumvent the problem?

jghali

2006-03-22 16:00

administrator   ~0009420

ok, so there is maybe a problem with the postscript code generated. Can you upload the image you used to produce that error?

2006-03-22 16:17

 

test_image.tif (2,369,868 bytes)

abrock

2006-03-22 16:18

reporter   ~0009421

Last edited: 2006-03-22 16:20

I have uploaded the image I used in the test you made mention of that causes an error when printing.

BTW, the Gestetner C7116 supports Postscript Level 3.

abrock

2006-03-22 22:20

reporter   ~0009424

Several other items of note that I have discovered today while working with the program and trying to get it to print.

First, I imported a ps file created from Adobe PageMaker. Anyway, I imported this file into a new Scribus document. I could print in with and without the right-shift circumvent trick. The entire document printed both times, but it will not print in color without using the right-shift circumvent trick.

Second, I re-created the above imported document by creating a new document in Scribus and laying it out to look like the one from PageMaker. The document is comprised of lines, shaded boxes, and text. It will print without having to use the right-shift circumvent trick; however, it does not print the color portions in color. If I use the right-shift circumvent trick, it prints only part of the page, but the color parts are in color. The printed part is the left 1/4 of the page all the way down. The rest of the page is blank.

jghali

2006-03-22 23:23

administrator   ~0009427

Using the provided image, I have tested our PostScript output with GhostScript 8.53, Distiller 7.0, Photoshop 7.0, a Xerox Phaser 7750GX. All of these software or printer supports PostScript Level 3 and all output it correctly and without the slightest error (and in color).

jghali

2006-03-22 23:30

administrator   ~0009428

Last edited: 2006-03-22 23:31

Given the results of my test, your problems may be caused by the use of an inadequate PPD. You should try to update it.

2006-03-23 13:43

 

abrock

2006-03-23 13:47

reporter   ~0009439

I've uploaded another file that perhaps you can try. It is one that I created from scratch in Scribus. I can get it to print with or without the circumvent trick, but it will not print in color unless I use the circumvent trick.

Perhaps it is the ppd, but Scribus is the only program that gives me these problems. InDesign, PageMaker, and all my other programs have no problem printing in color without errors to the printer. So I am at a loss as to how to solve the problem. Perhaps there is something in the way Scribus is sending the data to the printer that is giving it problems.

I am using GPL Ghostscript 8.50. I originally installed AFPL Ghostscript but Scribus kept giving me the message that Ghostscript was not installed, so I went with the GPL version and Scribus found it just fine.

jghali

2006-03-23 17:10

administrator   ~0009449

The least that can be said is that there is not much color in your document amongst printable objects. Looking at outputted files, the color data is what is expected whatever print path is used.

For your information there is a big difference between the normal printing method and the circumvent trick : the normal print method transmit color as spot colors or CMYK colors, the gdi print path as RGB colors, the RGB to CMYK conversion being done by the printer in this case.

Looking at your document, the color named FromEPS#132b1a is a spot color. When using the normal print path (postscript), this color is transmitted by default as a spot color with following CMYK equivalent: C9% M0% Y7% K83%. When using the gdi print path, the FromEPS#132b1a color is outputed with values specified in color dialog : R19 G43 B26. The RGB to CMYK conversion done by the printer can lead to a quite different color than the previous one.

Several possibilities here:
- your printer may have some difficulties dealing with spot colors (but doubtful), in this case you should use the "Convert spot colors to process colors" option
- the difference you see may result from the fact that the PostScript print path specify color spot equivalents as CMYK (and not RGB) and perform in case of spot colors the conversion without color management (even if it is enabled it seems).

Possible solution:
1 ) Enable color management in document preferences
2 ) Edit the FromEPS#132b1a color in colors dialog: uncheck to IsSpot box and convert your color to the CMYK model
I suspect that postscript print result will be closer to the one you expect

jghali

2006-03-23 17:23

administrator   ~0009450

Btw, i see you use 1.3.2. There is a 1.3.3cvs snapshot on sourceforge which has some important fixes compared to the original 1.3.2 release

plinnell

2006-03-25 19:54

viewer   ~0009475

please convert all those color to CMYK and retest.. I suspect your printer may not support RGB spots in your configuration.

Issue History

Date Modified Username Field Change
2006-03-22 06:16 abrock New Issue
2006-03-22 06:52 cbradney Status new => assigned
2006-03-22 06:52 cbradney Assigned To => jghali
2006-03-22 11:31 jghali Note Added: 0009416
2006-03-22 12:09 jghali Note Edited: 0009416
2006-03-22 12:59 jghali Note Added: 0009417
2006-03-22 15:21 abrock Note Added: 0009419
2006-03-22 16:00 jghali Note Added: 0009420
2006-03-22 16:17 abrock File Added: test_image.tif
2006-03-22 16:18 abrock Note Added: 0009421
2006-03-22 16:20 abrock Note Edited: 0009421
2006-03-22 22:20 abrock Note Added: 0009424
2006-03-22 23:23 jghali Note Added: 0009427
2006-03-22 23:30 jghali Note Added: 0009428
2006-03-22 23:31 jghali Note Edited: 0009428
2006-03-23 13:43 abrock File Added: FTF for Radio Stations 106-110 [CD Insert].sla
2006-03-23 13:47 abrock Note Added: 0009439
2006-03-23 17:10 jghali Note Added: 0009449
2006-03-23 17:23 jghali Note Added: 0009450
2006-03-25 19:54 plinnell Note Added: 0009475
2006-05-30 21:55 plinnell Status assigned => resolved
2006-05-30 21:55 plinnell Resolution open => no change required
2006-06-05 12:32 cbradney Status resolved => closed