First - 'standard' printing works ok, which excludes many error sources.
But - I cannot use any special capabilities of the printer, since the PPD files
(properly placed and named, by CUPS, in /etc/cups/ppd/) cannot be found!
lpoptions -l tells me "Destination Kyocera has no PPD file!" and KDE print
configuration options does not show any 'driver' tab.
CUPS at localhost:631 works ok - except for "Configure printer" which gives an
Error: server-internal-error

I am running Slackware 10 with kernel 2.6.7, using KDE (and thus X). I know
that non-X users used to have to recompile esp-ghostscript but the Slack 10
release blurb indicated that CUPS integration had now been achieved..

The CUPS.bugs newsgroup des not have any mention of this type of problem, nor
does googling give any hints.

================================================== ==
<remove my attribute to get my proper email address>

Occam wrote:

> First - 'standard' printing works ok, which excludes many error sources.
> But - I cannot use any special capabilities of the printer, since the PPD
> files (properly placed and named, by CUPS, in /etc/cups/ppd/) cannot be
> found! lpoptions -l tells me "Destination Kyocera has no PPD file!" and
> KDE print configuration options does not show any 'driver' tab.
> CUPS at localhost:631 works ok - except for "Configure printer" which
> gives an Error: server-internal-error

forget about kde and other fancy guis for now. focus on cups internal web
interface and logs. check /var/log/cups/error_log and see what's happening

On Sun, 08 Aug 2004 00:52:52 -0400, "Dominik L.. Borkowski" <dom@vbi.vt.edu>
wrote:

>Occam wrote:
>
>> First - 'standard' printing works ok, which excludes many error sources.
>> But - I cannot use any special capabilities of the printer, since the PPD
>> files (properly placed and named, by CUPS, in /etc/cups/ppd/) cannot be
>> found! lpoptions -l tells me "Destination Kyocera has no PPD file!" and
>> KDE print configuration options does not show any 'driver' tab.
>> CUPS at localhost:631 works ok - except for "Configure printer" which
>> gives an Error: server-internal-error
>
>forget about kde and other fancy guis for now. focus on cups internal web
>interface and logs. check /var/log/cups/error_log and see what's happening

That is why I went to the command line program 'lpoptions' and tried the CUPS
'direct' interface at localhost:631.

The error log shows normal startup and printing messages only.

I also changed the PPD file, which made printing not work properly - showing
that the printing process had found and used the right PPD file. No difference
to lpoptions -l though.
Further I tried it with another printer, and on a second computer with a third
printer: always standard printing ok, but no PPD files found.

================================================== ==
<remove my attribute to get my proper email address>

On Mon, 09 Aug 2004 07:52:52 +1000, Occam <occam@internode.razoron.net> wrote:

>On Sun, 08 Aug 2004 00:52:52 -0400, "Dominik L.. Borkowski" <dom@vbi.vt.edu>
>wrote:
>
>>Occam wrote:
>>
>>> First - 'standard' printing works ok, which excludes many error sources.
>>> But - I cannot use any special capabilities of the printer, since the PPD
>>> files (properly placed and named, by CUPS, in /etc/cups/ppd/) cannot be
>>> found! lpoptions -l tells me "Destination Kyocera has no PPD file!" and
>>> KDE print configuration options does not show any 'driver' tab.
>>> CUPS at localhost:631 works ok - except for "Configure printer" which
>>> gives an Error: server-internal-error
>>

Problem solved: I had uncommented the ServerName and ServerAdmin lines and put
the name of my domain there. Recommenting the lines solved the problem.
================================================== ==
<remove my attribute to get my proper email address>