From: james <garftd@verizon.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] printing pdfs
Date: Sat, 30 May 2020 09:06:16 -0400 [thread overview]
Message-ID: <110719f3-54c1-bd6c-b270-09d6cf16f1c2@verizon.net> (raw)
In-Reply-To: <AbFB0-4ZK-7@gated-at.bofh.it>
On 5/29/20 1:20 AM, Ashley Dixon wrote:
> On Thu, May 28, 2020 at 04:11:46PM -0400, james wrote:
>> Pdfs are becoming a challenge to print. I'm sure I'll be printing pdf files
>> for decades to come.
>>
>> So what application/strategy gets me past errors like this:
>>
>> "Cannot mix incompatible Qt library (version 0x50e01) with this library
>> (version 0x50e02)"
>
> How is your printer connected ? If it's using The Common Unix Print System
> (C.U.P.S.) as many do, try the lpr command (from `net-print/cups`). The server
> on which C.U.P.S.\ is running is specified with the `-H <address>` argument, and
> various options can be specified with `-o <key=value>`.
>
> To take the example from the man page of lpr:
>
> Print a double-sided legal document to a printer called "foo":
> $ lpr -P foo -o media=legal -o sides=two-sided-long-edge filename
>
> If your printer is remote, as mine is (on a server called `genserv`), you can do
> the following:
>
> $ lpr -H genserv -o sides=two-sided-long-edge paper.pdf
works great !
>
> This is not a suggestion that you abandon the issue of mismatched Qt library
> versions, but rather a simple workaround to use while the various Qt programs
> get up-to-date with the latest versions of the libraries.
Yea, the QT issues, happen every time the bleeding edge (of qt)
releases. Once I get the packages all upgraded, the bleeding edge qt
stuff works great (thanks to all the gentooers that work on qt!).....
> Providing C.U.P.S.\ is
> configured correctly with all the appropriate `ppd` files for your particular
> printer model, lpr should work out-of-the-box.
After thumping all teh cups codes, it works again, but some office files
from a pc that were originated in europe, cause the print to hickup. The
hp printer complained about version 1.... version 2 on the tiny hp
display. Rebooted several times and all my linux printing started
working again. I have the original hp firmware (10 years old). I do not
trust the updated hp firmwares, for several reason....
Thanks Ashley
next prev parent reply other threads:[~2020-05-30 13:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Abxaq-8iU-9@gated-at.bofh.it>
[not found] ` <Abxaq-8iU-7@gated-at.bofh.it>
[not found] ` <Abxk6-8m0-13@gated-at.bofh.it>
2020-05-28 23:04 ` [gentoo-user] printing pdfs james
2020-05-28 23:34 ` Jack
2020-05-29 22:30 ` james
2020-05-29 23:31 ` Jack
2020-05-30 7:58 ` Neil Bothwick
2020-05-30 12:54 ` james
2020-05-30 14:39 ` Francesco Turco
2020-05-29 0:05 ` Dale
2020-05-29 7:58 ` Francesco Turco
[not found] ` <AbFB0-4ZK-7@gated-at.bofh.it>
2020-05-30 13:06 ` james [this message]
2020-05-30 13:24 ` Ashley Dixon
2020-05-30 18:25 ` Neil Bothwick
2020-05-30 21:38 ` Peter Humphrey
[not found] <3f9a2e62-c430-5295-d2b9-1b7a30c1cfd2.ref@verizon.net>
2020-05-28 20:11 ` james
2020-05-28 20:21 ` Francesco Turco
2020-05-28 20:22 ` Arve Barsnes
2020-05-28 21:10 ` Dale
2020-05-28 22:25 ` Jens Reinemuth
2020-05-29 5:10 ` Ashley Dixon
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=110719f3-54c1-bd6c-b270-09d6cf16f1c2@verizon.net \
--to=garftd@verizon.net \
--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