Re: CUPS

Nick Edwards <[email protected]>
Newsgroups gmane.linux.slackware
Message-ID <CAMD-=VJ5k0aLpY864EVm9F3SkCHRxRmtUafAqAFajrQgt3VdKA@mail.gmail.com>
On 7/27/14, Walter Alejandro Iglesias <[email protected]> wrote:

>> Only noticed this because just replaced our ubuntu print server with
>> slackware (all other serves are slackware anyway so why not)  but for
>> the life of me it wont print .conf files,
>> sits there forever saying Idle - "Sending data to printer."  but it
>> clearly is not
>> hell the thing wont even print the test page "no profiles specified in
>> PPD"
>> even copied the types and convs files from  .../share/cups to
>> /etc/cups, no difference.
>>
>
> I am pretty sure that whatever your problem is it has nothing to do with
> your prejudice about antiquated or modern software.
>
> It sounds to me that you chose the wrong driver or the driver you need
> is not present in Slackware by default (Ubuntu, with its *friendly*
> approach take care of that details for you).
>

Nope, the driver (from guttenprint) is correct, if I print a document
from openoffice, it works perfect, I can even print an email from
webmail in chrome,  but try anything else, like from text editors, or
other softwares, nope, even a lp /etc/somefile.txt  lpr -l
/etc/ntp.conf on the print server itself = no go, and again test pages
dont from the print server, so I'm happy the driver is right, since it
is a perfect match to my printer.

The *only* thing I see different, and I will test out when I get in,
is in ubuntu's version they add in
Filter application/vnd.cups-raw 0 -
Filter application/vnd.cups-postscript 0 pstocanonij
Filter application/vnd.cups-command 0 commandtops

in the  printer.conf file printer section,  this is *not* added in
slackwares version, no mater what I tried.


also
 Willy, unable to build 1.7 on that machine, I think its a 64/32
conflict with slack 14.0, since i can build your package on my 32 bit
pc fine.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.