Print jobs automatically cancel before they can run

[Gail LaForest]

Thank you, I did indeed join the list and will watch this thread from my email 
program as opposed to the browser, and I am happy to make things as easy as 
possible for all involved.

Peace,
Gail

On Tuesday 10 May 2005 02:21 pm, Kurt Pfeifle wrote:
> Gail,
>
> forwarding this to you as per your request. Please subscribe (you can not
> expect us to deal with each user separately -- you can always unsubscribe
> after your problem is solved).
>
> For my questions see below (end of mail).
>
> Cheers,
> Kurt
>
> On Tuesday 10 May 2005 20:42, Gail LaForest wrote:
> > > Greetings All,
> > >
> > > I have an interesting problem that has me stumped.  I did a recent
> > > install of Debian Linux kernel 2.6.8-2-386 (testing) with KDE 3.3.2. 
> > > Everything is running as it should with only one problem . . . . I
> > > cannot get my Epson Stylus Photo 1280 to print anything.
> > >
> > > Using apt-get I installed cupsys, cupsys-client, and
> > > cupsys-driver-gimpprint.  I've done this same installation a half dozen
> > > times with no problems at all until now.
> > >
> > > When I try to print anything from any program within KDE the print job
> > > cancels itself immediately (as I view it from within Konqueror using
> > > print:/printers/Stylus_Photo_1280?completed_jobs).  The state reads
> > > Canceled as soon as the print button command is given.
> > >
> > > Any help at all would be greatly appreciated.  I can find nothing
> > > online that points to this kind of problem, and I am more than happy to
> > > supply whatever file information is needed to help.
> > > Thanks,
> > > Gail
> > >
> > > PS  I did not subscribe to this list, please cc this email address in
> > > replies.
> >
> > I am working on this as best I can.  I went into the CUPS printer admin
> > through Konqueror (localhost.localdomain:631) and the message that came
> > up when I tried to print from there was Error: client-error-not-possible
> >
> > What does this mean?  KPrint and CUPS have always worked flawlessly until
> > now. I will gladly send a debug report or log file if someone can point
> > me in the right direction for doing that.
>
> Questions:
>
>  * Which version of CUPS are you using?
>  * Can you print from the commandline?
>  * Can you give us the output of the following commands (run as root)?
>    * lpstat -r
>    * lpstat -p
>    * lpstat -p -l
>    * lpstat -v
>    * lpinfo -v
>    * lpoptions -p <yourprintername> -l
>
> Cheers,
> Kurt