You are not logged in.

#1 2024-10-07 19:30:45

7ate9
Member
Registered: 2024-03-28
Posts: 2

Newest version of extra/imagescan has problems with Epson ES-200

Edit: Nevermind. I think it's a hardware problem, despite it very much looking like a software problem. The equivalent windows version of the software, with the same scanner, has the exact same issue. This doesn't explain why the Utsushi GUI on Linux seems broken for me, and might actually be an issue which I'll try to figure out, but the 'black bar' I described below appears on the scan of the Windows version as well.

Hello,

I had a problem with my scanner during my most recent system upgrade. I'm at least assuming it was the last version, as it has been awhile since I used my scanner. Thought I'd ask to see if anyone else had issues with their Epson scanners or if this is a problem on my system or scanner.

In short, the scan, despite the size of the page selected, always has a large black bar blocking off the right margin. I use the following command through a script when I am scanning:

`$ utsushi --image-format=JPEG --no-interface esci:usb:/sys/devices/pci0000:00/0000:00:15.0/usb2/2-3/2-3:1.0 --image-type Color --resolution=300 > 0.jpg`

I've tried playing around with the --scan-area option without any different results. Oddly, if I use --duplex, the reverse side appears to fully scan, just the front page seems wrong.

It seems the utsushi GUI is broken too; all of the relevant buttons are grayed out in the GUI and I can't seem to do anything, even though utsushi recognizes the scanner is connected.

If someone can help here, I can provide more details about the issue, but I'm mostly asking where exactly I might be able to file a bug report if I do determine this isn't isolated on my system. It seems Epson closed the source of the program, and I'm not exactly who is working on this program anymore (if anybody). The Archlinux package repo is on https://gitlab.archlinux.org/archlinux/ … /imagescan. I don't think it's appropriate to make an issue there, as that would just pertain to issues with the image build, not the actual program, no?

Anyway, not really sure what to do about this except maybe try to roll back my system and see if the issue persists. Might try and make a sandbox for it or something if that fixes it (which sounds like a lot of fuuun).

Last edited by 7ate9 (2024-10-07 21:21:17)

Offline

Board footer

Powered by FluxBB