From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] bypassing CUPS - howto
Date: Fri, 30 Apr 2010 10:43:01 +0100 [thread overview]
Message-ID: <7FB50E15-9A8B-45EB-82A8-59F0DFE6DA6D@stellar.eclipse.co.uk> (raw)
In-Reply-To: <tkrat.a396f7b4570c075d@igpm.rwth-aachen.de>
On 29 Apr 2010, at 10:13, Helmut Jarausch wrote:
> On 29 Apr, Stroller wrote:
>>
>> On 28 Apr 2010, at 15:27, Helmut Jarausch wrote:
>>>> ...
>>>> Why do you need to bypass CUPS?
>>>
>>> Thanks, it's just for debugging.
>>>
>>> Printing some pdf files with acroread makes some printers
>>> hang here.
>>> To locate the problem source, I'd like to check if the printer
>>> works if it gets the postscript or pdf-file (there printer is
>>> assumed
>>> to accept postscript level 3).
>>
>> Have you tried using `lpr` at the command line?
>>
>> I *believe* something like `lpr /path/to/file.pdf` should work.
>>
>
> Thanks, but lpr is just a front-end for cups.
So you're sure the problem isn't Acroread, then?
This is not clear from your description.
Stroller.
next prev parent reply other threads:[~2010-04-30 9:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <eEdjs-3zv-25@gated-at.bofh.it>
2010-04-28 13:11 ` [gentoo-user] bypassing CUPS - howto David W Noon
2010-04-28 14:27 ` Helmut Jarausch
2010-04-29 8:37 ` Stroller
2010-04-29 9:13 ` Helmut Jarausch
2010-04-29 13:47 ` Dale
2010-05-09 3:10 ` Michael George
2010-05-09 16:30 ` Michael George
2010-04-30 9:43 ` Stroller [this message]
[not found] <eEg7E-7KC-17@gated-at.bofh.it>
[not found] ` <eEg7E-7KC-15@gated-at.bofh.it>
[not found] ` <eEh3I-Hw-7@gated-at.bofh.it>
[not found] ` <eExUR-e9-5@gated-at.bofh.it>
[not found] ` <eEyQV-1BT-11@gated-at.bofh.it>
[not found] ` <eECBb-7il-3@gated-at.bofh.it>
[not found] ` <eI602-3d7-9@gated-at.bofh.it>
2010-05-09 17:18 ` David W Noon
2010-04-28 10:07 Helmut Jarausch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7FB50E15-9A8B-45EB-82A8-59F0DFE6DA6D@stellar.eclipse.co.uk \
--to=stroller@stellar.eclipse.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox