Yahoo Groups archive

Digital BW, The Print

Index last updated: 2026-04-28 22:56 UTC

Thread

QTR Linux install question

QTR Linux install question

2003-10-13 by David Wroblewski

For those of you who have installed QTR on Linux, does this problem
sound familiar:

I have compiled and installed the software, defined a QTR version of 
my 2200 as a printer, and installed the example curves. Running a print
job via "qtcups CurveDesign/Images/qtrip-big.jpg" 
produces a print dialog with all the right stuff, ie shows the curves 
and options as expected. When I click OK the print manager shows a 
document getting queued for the printer. So far, so good.

Then the job disappears off the printer queue but nothing happens with 
the printer. (As a sanity check, if I invoke qtcups as above but print 
though the standard, non-QTR, printer definition the image prints 
immediately without problems.)

When I look at the the results of Print-Gimp-ErrorLog.command, I see two 
suspicious things. On jobs where I select paper source = standard, I see 
warnings that say "Media Tray Empty!" and "Invalid Printer settings!". 
If I select paper source as "Auto", I see those messages plus 
"PID 1234 crashed on signal 11!"

Thanks for your patience. Resolution will get rolled into the Linux 
installation notes, of course. 

Thanks,
David

Re: QTR Linux install question

2003-10-14 by Roy Harrington

--- In DigitalBlackandWhiteThePrint@yahoogroups.com, "David Wroblewski" 
<dawroblewski@y...> wrote:
> For those of you who have installed QTR on Linux, does this problem
> sound familiar:
> 
> I have compiled and installed the software, defined a QTR version of 
> my 2200 as a printer, and installed the example curves. Running a print
> job via "qtcups CurveDesign/Images/qtrip-big.jpg" 
> produces a print dialog with all the right stuff, ie shows the curves 
> and options as expected. When I click OK the print manager shows a 
> document getting queued for the printer. So far, so good.
> 
> Then the job disappears off the printer queue but nothing happens with 
> the printer. (As a sanity check, if I invoke qtcups as above but print 
> though the standard, non-QTR, printer definition the image prints 
> immediately without problems.)
> 
> When I look at the the results of Print-Gimp-ErrorLog.command, I see two 
> suspicious things. On jobs where I select paper source = standard, I see 
> warnings that say "Media Tray Empty!" and "Invalid Printer settings!". 
> If I select paper source as "Auto", I see those messages plus 
> "PID 1234 crashed on signal 11!"
> 
> Thanks for your patience. Resolution will get rolled into the Linux 
> installation notes, of course. 
> 
> Thanks,
> David

Hi David,

The error message "crashed on signal 11" basically means the program
went off into never-never land.  The PID (process id number) should
reference which program crashed -- is there a message about starting
a process with that PID in the log?  i.e. what program is being run there?
Also are the other messages preceded by some indication of what
program is finding these errors?

You might also try some other file formats like a tif file.  Make sure
its a grayscale, 8bit file and that you select the QTR mode.  You can
also try printing without a curve -- it ought to print thru gimp-print
in the normal mode.

Roy

Re: QTR Linux install question

2003-10-14 by David Wroblewski

--- In DigitalBlackandWhiteThePrint@yahoogroups.com, "Roy 
Harrington" <roy@h...> wrote:
> --- In DigitalBlackandWhiteThePrint@yahoogroups.com, "David 
Wroblewski" 
> <dawroblewski@y...> wrote:

Roy, I've emailed you a bit of a cups error log file that illustrates
what's happening, with some notes and answers to your questions...

-David


>
> The error message "crashed on signal 11" basically means the 
program
> went off into never-never land.  The PID (process id number) should
> reference which program crashed -- is there a message about 
starting
> a process with that PID in the log?  i.e. what program is being 
run there?
> Also are the other messages preceded by some indication of what
> program is finding these errors?
> 
> You might also try some other file formats like a tif file.  Make 
sure
> its a grayscale, 8bit file and that you select the QTR mode.  You 
can
> also try printing without a curve -- it ought to print thru gimp-
print
Show quoted textHide quoted text
> in the normal mode.
> 
> Roy

Re: QTR Linux install question

2003-10-14 by Roy Harrington

David,

I got your log file and I'm answering here since maybe some of the Linux
folks might have some comments.

From the log file, the program which is dying is "imagetoraster".  This is
a CUPS filter that converts several image formats to the raster format
needed by both QTR and Gimp-print.   On the Mac this program is no
longer used, its basically been superceded by ghostscript which also
can deal with postscript data.  

So on the Mac, Ghostcript is required for gimp-print and therefore QTR.
I suspect its a matter of getting ghostscript installed to make this
all work.  

Roy

--- In DigitalBlackandWhiteThePrint@yahoogroups.com, "David Wroblewski" 
<dawroblewski@y...> wrote:
Show quoted textHide quoted text
> --- In DigitalBlackandWhiteThePrint@yahoogroups.com, "Roy 
> Harrington" <roy@h...> wrote:
> > --- In DigitalBlackandWhiteThePrint@yahoogroups.com, "David 
> Wroblewski" 
> > <dawroblewski@y...> wrote:
> 
> Roy, I've emailed you a bit of a cups error log file that illustrates
> what's happening, with some notes and answers to your questions...
> 
> -David
> 
> 
> >
> > The error message "crashed on signal 11" basically means the 
> program
> > went off into never-never land.  The PID (process id number) should
> > reference which program crashed -- is there a message about 
> starting
> > a process with that PID in the log?  i.e. what program is being 
> run there?
> > Also are the other messages preceded by some indication of what
> > program is finding these errors?
> > 
> > You might also try some other file formats like a tif file.  Make 
> sure
> > its a grayscale, 8bit file and that you select the QTR mode.  You 
> can
> > also try printing without a curve -- it ought to print thru gimp-
> print
> > in the normal mode.
> > 
> > Roy

Re: QTR Linux install question

2003-10-14 by David Wroblewski

Thanks Roy, that's very useful.

I certainly have ghostscript installed, it comes with Redhat 9.
rpm -q ghostscript returns "ghostscript-7-05.32.1", to be exact.

If I understand you, we'd like to see /usr/bin/ghostscript being
invoked (with some set of options, I'm sure) during CUPS
processing in place of imagetoraster. 

Hmmmm... How to change this.... Wild guess, I grepped for 
imagetoraster in /etc/cups and I see that there are many 
references to imagetoraster in /etc/cups/mime.convs for 
starters... what does the image/jpeg entry in that file 
look like on the Mac?

-david



> 
> David,
> 
> I got your log file and I'm answering here since maybe some of the 
Linux
> folks might have some comments.
> 
> From the log file, the program which is dying is "imagetoraster".  
This is
> a CUPS filter that converts several image formats to the raster 
format
> needed by both QTR and Gimp-print.   On the Mac this program is no
> longer used, its basically been superceded by ghostscript which 
also
> can deal with postscript data.  
> 
> So on the Mac, Ghostcript is required for gimp-print and therefore 
QTR.
> I suspect its a matter of getting ghostscript installed to make 
this
> all work.  
> 
> Roy
> 
> --- In DigitalBlackandWhiteThePrint@yahoogroups.com, "David 
Wroblewski" 
> <dawroblewski@y...> wrote:
> > --- In DigitalBlackandWhiteThePrint@yahoogroups.com, "Roy 
> > Harrington" <roy@h...> wrote:
> > > --- In DigitalBlackandWhiteThePrint@yahoogroups.com, "David 
> > Wroblewski" 
> > > <dawroblewski@y...> wrote:
> > 
> > Roy, I've emailed you a bit of a cups error log file that 
illustrates
> > what's happening, with some notes and answers to your 
questions...
> > 
> > -David
> > 
> > 
> > >
> > > The error message "crashed on signal 11" basically means the 
> > program
> > > went off into never-never land.  The PID (process id number) 
should
> > > reference which program crashed -- is there a message about 
> > starting
> > > a process with that PID in the log?  i.e. what program is 
being 
> > run there?
> > > Also are the other messages preceded by some indication of what
> > > program is finding these errors?
> > > 
> > > You might also try some other file formats like a tif file.  
Make 
> > sure
> > > its a grayscale, 8bit file and that you select the QTR mode.  
You 
> > can
> > > also try printing without a curve -- it ought to print thru 
gimp-
Show quoted textHide quoted text
> > print
> > > in the normal mode.
> > > 
> > > Roy

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.