Hi, ToddAndMargo writes:
> On 02/17/2018 06:13 AM, Richard Ryniker wrote: >> Does Olaf Meeuwissen's post at >> https://www.mail-archive.com/sane-devel@lists.alioth.debian.org/msg33846.html >> help? It describes imagescan as an Epson product. > > Hi Richard, > > My scanner is an Epson Perfection V300 > > I installed iscan-gt-f720-bundle-1.0.1.x64.rpm from That bundle should support your Perfection V300 just fine. > https://epson.com/Support/Scanners/Perfection-Series/Epson-Perfection-V19-Photo/s/SPT_B11B231201?review-filter=Linux Eh, that's for the V19. Oh, I see now, clicking the Linux Drivers for Epson Products gets you to http://download.ebz.epson.net/dsc/search/01/search/?OSC=LX (with which I'm familiar) where you can search for the V300. > I am able to scan with both xsane and simple-scan, which > both use the front end. Looks like you're slightly confused as to what's a frontend and what's a backend as far as SANE is concerned. Both xsane and simple-scan are SANE frontends. Both use the SANE epkowa backend that came as part of your bundle (via the SANE dll backend) to communicate with the scanner (via a non-free interpreter plugin used by the SANE epkowa backend in your particular case). > I am not able to scan from the back end using saned > with either "xsane net:localhost" of PDF Studio. Here you are using the xsane SANE frontend in combination with the SANE net backend to communicate with saned, running on localhost. That, in turn should be using the SANE epkowa backend (again via the SANE dll backend) to communicate with your scanner (again via that non-free interpreter plugin that the SANE epkowa backend relies upon in your particular case). > I am able to manually start saned and scan with > PDF Studio, which always uses saned. OK, so your saned configuration is good (apart from the fact that you have to start it manually but that's another issue). > From Olag's post, it seems that he is saying > that there is a different driver for the front end > and the back end. But, if I can manually start saned, > it would seems that I have both in place. Sorry if I gave you that impression but that's not what I was trying to say. Perhaps that my explanations above clarify a bit better how the various pieces are connected. If you can scan from your V300 using PDF Studio and PDF Studio always uses your saned on localhost, then, yes, you have all the required pieces in place. > From the error log, I do believe I am missing > libsane-imagescan.so.1 That SANE backend does not support the V300, AFAIK. The SANE epkowa backend does, with the help of a non-free interpreter (libesintXX.so IIRC). The imagescan backend is part of the imagescan RPM that you appear to have installed from an imagescan-bundle or at least had installed at one time. These are *not* the same as the iscan-bundles! BTW, the V19 is supported by *both* bundles. Check if you still have it installed, remove it if you don't need it and remove any references to it from any files below /etc/sane.d/ insofar still present. My guess is that the error message you initially posted is due to you removing the imagescan RPM and that that didn't clean up any references in the SANE configuration or, heaven forbid, you just removed selected files manually yourself. You can remove any imagescan.conf you find below /etc/sane.d/ and should remove any imagescan entry in dll.conf you find. That should make that dll backend error go away but probably still will not fix your "xsane net:localhost" issue. In case you want to keep imagescan installed, check that /usr/lib64/sane/libsane-imagescan.so.1 is not a broken symlink and points to /usr/lib64/utsushi/sane/libsame-imagescan.so.1.0.27. That is, the output of readlink -e /usr/lib64/sane/libsane-imagescan.so.1 should produce /usr/lib64/utsushi/sane/libsame-imagescan.so.1.0.27 > For the full error log, see > https://bugzilla.redhat.com/show_bug.cgi?id=1546433 > > Error log: https://bugzilla.redhat.com/attachment.cgi?id=1397367 > configuration: https://bugzilla.redhat.com/attachment.cgi?id=1397368 > > From the error log, it looks like saned tried to contact > the scanners three times and failed because it could not > find libsane-imagescan.so.1 It does look that way but I think that is mostly due to the log levels you specified. Add SANE_DEBUG_EPKOWA=HEX to see what the epkowa backend has to say when it looks for your V300 (or V19?). Hope this helps, -- Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Software https://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
