Bug 703529

Summary:	Epson Stylus SX125 works with 1.0.22
Product:	[Fedora] Fedora	Reporter:	Gabriel Schulhof <gabrielschulhof>
Component:	sane-backends	Assignee:	Nils Philippsen <nphilipp>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	collura, nphilipp
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-28 12:54:02 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Gabriel Schulhof 2011-05-10 15:29:50 UTC

Description of problem:
The Epson Stylus SX125 (0x4b8/0x85c) works with the epson2 backend from sane-backends-1.0.22 ...

I had to modify /etc/sane.d/epson2.conf to append the vendor and product code to the "usb" line.

I tried to write to the sane-devel mailing list to ask them to add the device to the list of supported scanners, so subsequent users don't have to find out the hard way how to make the scanner work (like I did).

I also tried to ask them what tests to perform to qualify how well the scanner is supported, because their device listing has such a qualification.

Unfortunately, the mailing list doesn't seem to work for me, because the message that I sent was not sent back to me by mailman, like it usually happens. So, I don't know if anybody has received my message.

Could you please try to push support for this scanner upstream? It's probably as simple as adding the vendor/product code to a list so that it works out of the box, without any manual modifications to the conf file.

Version-Release number of selected component (if applicable): 1.0.22

How reproducible:
always

Steps to Reproduce:
1. Buy an Epson Stylus SX125
2. Install sane-backends-1.0.22
3. Scan a photo from gimp

Actual results:
It fails to find the scanner.

Expected results:
It scans the image.

Solution:
Change the line that reads "usb" in /etc/sane.d/epson2.conf to read "usb 0x4b8 0x85c"

Additional info:
It should not be necessary to make any modifications to conf files for this scanner to work. It should work out of the box.

Comment 1 Nils Philippsen 2011-09-16 11:21:03 UTC

I'll add the USB id for this scanner in the next release of sane-backends. Your mail to the ML has come through btw, but nothing happened besides M. Allan Noah thanking you for it :-). I'll try to push this upstream.

Comment 2 Nils Philippsen 2011-09-16 14:39:55 UTC

Fixed in sane-backends-1.0.22-4 for which I've submitted Fedora updates, you should be able to remove the usb id from epson2.conf with that version.

I've pushed the change into the upstream repository meanwhile, so the next version should know about it as well. I've marked it as ":status :untested", please give me feedback if you know about any shortcomings from using this device with the epson2 driver -- if there aren't any, I might as well change that to ":status :good" (for ":status :complete" we should know what features this device sports, and whether they all work).

Comment 3 Gabriel Schulhof 2013-03-03 22:26:05 UTC

I've since upgraded to Fedora 18, and, unfortunately, it has stopped working with or without the modification to epson2.conf.

sane-find-scanner will find it, but scanimage -L will say that there are no scanners.

My version of SANE is 1.0.23-7.

Comment 4 Nils Philippsen 2013-03-18 11:06:13 UTC

Do you have the actual scanner driver package (sane-backends-drivers-scanners) installed?

Comment 5 Gabriel Schulhof 2013-03-28 12:54:02 UTC

Thanks for your help! Installing that package made it work.

Comment 6 Gabriel Schulhof 2013-03-28 13:03:46 UTC

Thanks for your help! Installing that package made it work.