public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Scanning double sided documents and printing them the same.
Date: Thu, 10 Dec 2020 18:00:20 -0600	[thread overview]
Message-ID: <3b61be9d-64d2-33e3-10ab-ca1c89e13e17@gmail.com> (raw)
In-Reply-To: <rqu79l$jh2$3@ciao.gmane.io>

Grant Edwards wrote:
> On 2020-12-10, Michael <confabulate@kintzios.com> wrote:
>>> There's no need for the two-step process:
>>>
>>> $ convert scan1.png scan2.png scanned.pdf
>> There was some vulnerability in ghostscript[1] which disabled the above 
>> conversion - but I can't find the BGO number.  I thought it had been patched 
>> since then, but my system appears to not have been fixed:
>>
>> $ convert scan1.jpg scan2.jpg scan.pdf
>> convert: attempt to perform an operation not allowed by the security policy 
>> `PDF' @ error/constitute.c/IsCoderAuthorized/422.
>>
>> [1] https://www.kb.cert.org/vuls/id/332928/
> You're right. You have to adjust the ImageMagick config files to allow
> converting to pdf. AFAICT, it's safe as long as you trust the input
> you're converting. I figure photos I've taken are OK.
>
> --
> Grant
>


I tried this in XSane but couldn't figure out how to get it to scan two
pages with me clicking something when the second page is ready.  It
scanned first page, then scanned the second without giving me a chance
to flip it over.  So, XSane didn't work this time.  Maybe I'm doing
something wrong. 

So, convert was my next test.  I scanned in both sides, cd'd to the
directory where the files were and issued the command Grant provided. 
At first, I got the security error.  I dug around a bit and figured out
how to tell it to ignore that and tried again.  YEPPIE!!!  It worked.  I
opened it in a pdf viewer and it was two pages.  I don't need to print
this one but I can send it to a friend since it is her mail, sort of. 
If I needed to print it, it should print duplex just fine. 

It's command line but it works.  It's awesome.  Still open to
suggestions but for now, I got something working.  It's easier than
using LOo for sure. 

Dale

:-)  :-) 


  reply	other threads:[~2020-12-11  0:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-10  0:09 [gentoo-user] Scanning double sided documents and printing them the same Dale
2020-12-10  0:46 ` thelma
2020-12-10  1:29   ` thelma
2020-12-10  2:16     ` Dale
2020-12-10  8:27 ` Neil Bothwick
2020-12-10  9:20   ` Michael
2020-12-10  9:26     ` Neil Bothwick
2020-12-10 15:21     ` [gentoo-user] " Grant Edwards
2020-12-10 17:36       ` Michael
2020-12-10 22:25         ` Grant Edwards
2020-12-11  0:00           ` Dale [this message]
2020-12-11  0:04             ` Dale
2020-12-10  9:28 ` [gentoo-user] " J. Roeleveld
2020-12-10 10:49   ` Dr Rainer Woitok
2020-12-10 13:09     ` J. Roeleveld
2020-12-10 15:37 ` Rich Freeman
2020-12-10 17:58   ` J. Roeleveld

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=3b61be9d-64d2-33e3-10ab-ca1c89e13e17@gmail.com \
    --to=rdalek1967@gmail.com \
    --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