On Sun, 6 Jul 2003 22:14:42 -0400 Antonio RodrHX <[EMAIL PROTECTED]> wrote: > After turning the level to debug, here is what I get, after stopping > and starting again. I am attaching the relevant part. Thanks
< snip from attachment > D [06/Jul/2003:22:01:13 -0400] foomatic-gswrapper: gs '-dSAFER' '-dNOPAUSE' '-dBATCH' '-sDEVICE=stp' '-sOutputFile=/dev/fd/3' '/dev/fd/0' 3>&1 1>&2 D [06/Jul/2003:22:01:14 -0400] GNU Ghostscript 6.53 (2002-02-13) D [06/Jul/2003:22:01:14 -0400] Copyright (C) 2002 artofcode LLC, Benicia, CA. All rights reserved. D [06/Jul/2003:22:01:14 -0400] This software comes with NO WARRANTY: see the file COPYING for details. D [06/Jul/2003:22:01:15 -0400] Printer must be specified with -sModel D [06/Jul/2003:22:01:15 -0400] **** Unable to open the initial device, quitting. D [06/Jul/2003:22:01:15 -0400] Couldn't exec foomatic-gswrapper -q -dSAFER -dNOPAUSE -dBATCH -sDEVICE=stp -sOutputFile=- - at /usr/lib/cups/filter/cupsomatic line 965. < end snip > Well, it does look a problem with Ghostscript and/or foomatic, and not with cups proper. It appears to me (though I'm no expert) that CUPS (the spooler) hands off the job to Ghostscript successfully, but then GS can't process it correctly, probably because it's trying to open a non-existent device. I don't use the foomatic toolchain, so I'm afraid I can't be of much more assistance. Some questions that come to mind though... Did you possibly have a choice of drivers at some point during the Ghostscript or foomatic install? Are there any other drivers you could pick in the printer configuration that seem reasonable? Also, I know there's an HP driver somewhere - hpijs maybe? Is that applicable here? However it works out, it appears that you need to be using a different GS driver than you're trying right now. Sorry I can't be more helpful... hopefully someone with an HP is reading... --Todd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
