[gscan2pdf-help] Scantpaper - report re openSUSE Tumbleweed KDE Plasma

[daltrey <da...@da...>]

Hi all,

I got Scantpaper running in my openSUSE Tumbleweed/KDE Plasma install, 
so I thought I would share the results.

Because openSUSE rpm packaging/organization is a lot different from 
Ubuntu/Debian deb systems, it's somewhat difficult to find certain 
packages, such as goocanvas.

I had a lot of dependencies to track down and install, not the least of 
which was pytest and how to run pytest on Scantpaper. (Not that 
difficult, but new to me.) Many pytests hung up on OCRmyPDF until I 
finally got that resolved, then Tesseract and iso639, but finally 
Scantpaper is working. Early pytest runs would die at 29 errors, but the 
errors pointed me towards the missing packages and cleared up when I 
installed them.

This is fairly similar to the process I used in the early bad-old-days 
(for me) of running gscan2pdf in openSUSE/KDE. But luckily quite awhile 
ago enterprising persons incorporated gscan2pdf into openSUSE 
Tumbleweed, making life much easier. (I hope they will find out it is 
time to add Scantpaper.)

1. last pytest results -- 37 failed, 98 passed, 28 skipped, 1 xfailed, 
67 warnings.

2. goocanvas -- very problematic, ultimately it was some version of 
goocanvas 2.0 installed as 3.0?? (That was an AI assist ...) It's in the 
OSS repository, but I did not easily find it in a YAST search until I 
knew what I was looking for.

3. several dependencies were difficult to track down due to the 
difference between openSuse and Ubuntu (deb) packaging and naming 
conventions. Also, the openSuse online software lookup system was not 
working properly (or something), as the repositories referenced in the 
"install manually" option did not exist and the "automatic" option does 
not work in my browser, just opens a text page. I prefer to add the 
appropriate repository so the packages will update. I searched around 
for the referenced repository or something similar and couldn't find it.

However, the link to download the rpm package worked, so I was able to 
retrieve packages that were not in the OSS repository.

4. For OCRmyPDF I used a snap install, which required to log out and log 
back in to get snap added to the PATH -- I could add it manually without 
logging out, but Scantpaper didn't recognize the /snap/bin path until I 
logged out and back in?

5. I had to track down "community" builds of things like iso639 and 
ocrmypdf.py.

I didn't make very good notes, so this isn't a perfect walk-through.

On first run after the pytest listed at 1 above, everything worked 
right, sort of, but the scanner oddly kept rescanning the same page on 
the flatbed over and over and I had a little difficulty interrupting it 
so I could exit scantpaper by closing the window.

a separate issue: I have an anomaly with my Epson ET4800 printer/scanner 
that I also have in Gscan2pdf (I brought it up one time, but never 
followed through with Jeffrey, as I found a "workaround".)  Oddly, if 
scanner is set to "color" when the scan dialog opens, it nevertheless 
scans black and white. However, if I change the dialog to greytone or 
monochrome -- and then immediately change it back to color -- it scan in 
color just fine. Very odd.

For some reason when I used ADF I only got a scan of the first page, 
although the second page is feeding through the scanner. However, I have 
to test this on another scanner -- I don't know if it is a problem with 
scantpaper or a problem with the ET4800. (I have a couple of other MFC 
printers/scanners I can test, but they are in another room, so more 
difficult to test.)

Thanks for all you do Jeffrey! I have tested the various other available 
Linux scan programs, as well as some Windows ones, but nothing else is 
satisfactory.

In fact, on my Windows 11 computer, I nevertheless use Gscan2pdf, as it 
is running in the WSL2 gui and integrates nicely. (And, is less 
problematic than the commercial windows scan program I have.)

Barrington