public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ashley Dixon <ash@suugaku.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] printing pdfs
Date: Fri, 29 May 2020 06:10:13 +0100	[thread overview]
Message-ID: <20200529051013.b3nyn2jtepdkuyen@ad-gentoo-main> (raw)
In-Reply-To: <3f9a2e62-c430-5295-d2b9-1b7a30c1cfd2@verizon.net>

[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]

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

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. 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.

-- 

Ashley Dixon
suugaku.co.uk

2A9A 4117
DA96 D18A
8A7B B0D2
A30E BF25
F290 A8AA


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2020-05-29  5:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3f9a2e62-c430-5295-d2b9-1b7a30c1cfd2.ref@verizon.net>
2020-05-28 20:11 ` [gentoo-user] printing pdfs 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 [this message]
     [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     ` 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
2020-05-30 13:24       ` Ashley Dixon
2020-05-30 18:25       ` Neil Bothwick
2020-05-30 21:38         ` Peter Humphrey

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=20200529051013.b3nyn2jtepdkuyen@ad-gentoo-main \
    --to=ash@suugaku.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