[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Gimp Print Problem



On Wed, Jan 29, 2003 at 01:37:23PM -0500, Thomas H. George wrote:
> I ran the error_log as suggested.  The first 'false' result occurred on
> line 285.  I saved this and the following 10 lines but can't figure out
> how to use vi to insert them here.  vi wont let me switch to the file I
> saved without exiting this message.

Posting pertinent lines from error log to the list might help people on
the list figure out what problem may be.

You could always display the error_log in a different console or xterm
window than one where vi is running, select the text you want to copy,
switch back to window/console where vi is running, and press middle
button of mouse to paste the text into vi if you have gpm or X
running.

Or attach an excerpt from the error_log to you email. 

> 
> At any rate, the line immediately following the 'false' result reads
> 
> 	Error: /syntaxerrorin --%ztokenexec_continue--
> 
> and then, several lines later,
> 
> 	Last OS error: 2
> 	ESP Ghostscript 7.05.4: Unrecoverable error, exit code 1
> 
> If anyone can interprete this, I would appreciate advice as what to try
> to do to correct the problem.
> 
> 
> On Mon, Jan 27, 2003 at 10:44:36PM -0500, Jerome Acks Jr wrote:
> > On Mon, Jan 27, 2003 at 11:36:55AM -0500, Thomas H. George,,, wrote:
> > > Epson Stylus Color 860 on /dev/usblp0 installed with 
> > > CUPS+GIMP-print_v4.2.2-pre2.
> > > 
> > > Print Test Page prints a page with color hexagon but no test.
> > > 
> > > From a command line escputil -s -u -r /dev/usblp0 returns printer 
> > > status information.
> > > 
> > > From a command line lp printtest results in request id is lp-81 but 
> > > nothing is printed.
> > > 
> > > From a command line lpr printtest prints nothing and the next command 
> > > prompt is displayed.
> > > 
> > > How do I get back to Band Camp?
> > 
> > Maybe you can get more information on what the problem is by setting
> > the LogLevel parameter in /etc/cups/cupsd.conf to "debug" and restart
> > the cupsd process by running /etc/init.d/cupsys restart
> > 
> > The /var/log/cups/error_log file will contain a detailed log of
> > everything that is reported by the scheduler and print filters.
> > 
> 
> 

-- 
Jerome

Attachment: pgpkB3z6Dhu5b.pgp
Description: PGP signature


Reply to: