Package Details: epsonscan2 6.7.87.0-4

Git Clone URL: https://aur.archlinux.org/epsonscan2.git (read-only, click to copy)
Package Base: epsonscan2
Description: Epson scanner management utility
Upstream URL: https://download-center.epson.com/
Licenses: GPL-3.0-or-later, LicenseRef-EULA
Conflicts: epsonscan2-non-free-plugin
Submitter: tecnotercio
Maintainer: tecnotercio
Last Packager: tecnotercio
Votes: 23
Popularity: 2.03
First Submitted: 2020-11-20 05:34 (UTC)
Last Updated: 2026-05-11 08:09 (UTC)

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 Next › Last »

AchmadFathoni commented on 2023-06-15 02:17 (UTC) (edited on 2023-06-15 03:01 (UTC) by AchmadFathoni)

Few months ago everything working fine. But now epsoscan2 can't detect my L350 from USB.

I tried using imagescan. After tweaking utsushi.conf, I can finally scan my document.

I think I will use simple-scan because it doesn't need any configuration.

kleini commented on 2023-02-05 08:40 (UTC)

Version 6.7.0.0 crashes lately for me. I changed locally the PKGBUILD file to version 6.7.42.0, updated SHAs and the new version does not crash for me.

dboneham commented on 2022-10-18 17:57 (UTC)

It is not downloading one of the dependencies. See error message below

libharu-2.4.2-1-x86_64.pkg.tar.zst failed to download Total (1/3) 735.9 KiB 692 KiB/s 00:01 [############################################################] 100% error: failed retrieving file 'libharu-2.4.2-1-x86_64.pkg.tar.zst' from archlinux.uk.mirror.allworldit.com : The requested URL returned error: 404 error: failed retrieving file 'libharu-2.4.2-1-x86_64.pkg.tar.zst' from mirrors.melbourne.co.uk : The requested URL returned error: 404 error: failed retrieving file 'libharu-2.4.2-1-x86_64.pkg.tar.zst' from lon.mirror.rackspace.com : The requested URL returned error: 404 error: failed retrieving file 'libharu-2.4.2-1-x86_64.pkg.tar.zst' from mirror.bytemark.co.uk : The requested URL returned error: 404 error: failed retrieving file 'libharu-2.4.2-1-x86_64.pkg.tar.zst' from www.mirrorservice.org : The requested URL returned error: 404 error: failed retrieving file 'libharu-2.4.2-1-x86_64.pkg.tar.zst' from mirror.netweaver.uk : The requested URL returned error: 404 error: failed retrieving file 'libharu-2.4.2-1-x86_64.pkg.tar.zst' from mirror.netweaver.uk : The requested URL returned error: 404 error: failed retrieving file 'libharu-2.4.2-1-x86_64.pkg.tar.zst' from archlinux.uk.mirror.allworldit.com : The requested URL returned error: 404 error: failed retrieving file 'libharu-2.4.2-1-x86_64.pkg.tar.zst' from mirrors.melbourne.co.uk : The requested URL returned error: 404 error: failed retrieving file 'libharu-2.4.2-1-x86_64.pkg.tar.zst' from www.mirrorservice.org : The requested URL returned error: 404 error: failed retrieving file 'libharu-2.4.2-1-x86_64.pkg.tar.zst' from mirror.bytemark.co.uk : The requested URL returned error: 404 error: failed retrieving file 'libharu-2.4.2-1-x86_64.pkg.tar.zst' from lon.mirror.rackspace.com : The requested URL returned error: 404 error: failed retrieving file 'libharu-2.4.2-1-x86_64.pkg.tar.zst' from mirrors.manchester.m247.com : The requested URL returned error: 404 warning: failed to retrieve some files error: failed to commit transaction (failed to retrieve some files) Errors occurred, no packages were upgraded.

JotEs commented on 2022-08-29 13:21 (UTC)

@Balkonsky: I can confirm the findings in all points. I have also not found a solution.

sherif commented on 2022-08-24 11:38 (UTC)

Latest pkg + epsonsca2-non-free-plugin give communication error.. iscan , xsane works fine with the v600 scanner, however, to get the Transparent unit to work, I needed to use different device epkowa " the non-free device" however that doesn't show at all in epsonscan2, and I have no idea why

Nightwulf commented on 2022-06-26 22:26 (UTC)

Had the same communication error with my XP-3100. Installing this package helped: https://aur.archlinux.org/packages/epsonscan2-non-free-plugin

jpc commented on 2022-05-25 04:09 (UTC) (edited on 2022-05-25 04:41 (UTC) by jpc)

I get the same communication error, which is odd because this was working perfectly ~1.5 months ago on the same version. Agreed, this seems like a i/o bug somewhere in a dependency.