[opensuse] Detected scanner, proper driver, won't scan
The scanner is Epson 640U, in recently installed oS v11.3. YaST > Scanners finds it. scanimage -L and scanimage -T don't. Attemps to scan produce "Failed to start scanner. Invalid argument", which is not very informative. A review of a number of Google hits doesn't add more. I am assuming (hoping) that I have left something undone, but have not found anything to point me to it. Ideas? -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday, February 26, 2011 04:15:47 am Stan Goodman wrote:
I am assuming (hoping) that I have left something undone, but have not found anything to point me to it. Ideas?
Use root when you run scanimage. If that works then it is device access permission problem. Create system group scanner, change device group permissions, add user to scanner group, and fix udev rules to make changes persistent over the computer restarts. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 26 February 2011 22:56:27 Rajko M. wrote:
On Saturday, February 26, 2011 04:15:47 am Stan Goodman wrote:
I am assuming (hoping) that I have left something undone, but have not found anything to point me to it. Ideas?
Use root when you run scanimage. If that works then it is device access permission problem. Create system group scanner, change device group permissions, add user to scanner group, and fix udev rules to make changes persistent over the computer restarts.
In trying to understand how to do some of the things you have suggested,
I found that the scanner at present belongs to group lp, and that I am
not a member of that group. So I made myself one. (I can come back to
the "scanner" group later if that seems the way to go.)
The device permissions seem to be in order. I find from Google that the
default is
Hello, On Feb 26 12:15 Stan Goodman wrote (excerpt):
The scanner is Epson 640U, in recently installed oS v11.3. YaST > Scanners finds it. scanimage -L and scanimage -T don't.
Attemps to scan produce "Failed to start scanner. Invalid argument",
You may have a look at http://en.opensuse.org/SDB:Configuring_Scanners Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
The original problem, which appeared weeks ago, was that the scanner (which I have installed before on this very hardware, the and under the same oS v11.3), would not scan. I wrote: ***** The scanner is Epson 640U, in recently installed openSuSE v11.3. YaST > Scanners finds it and identifies it correctly; I have chosen the epson2 driver. scanimage -L device `epson2:libusb:003:002' is a Epson Perfection640 flatbed scanner -----much snipped----- ***** Lots of time , and lots of help from others here and elsewhere have not helped in solving the problem; wasted time for me and others. Today, I stumbled on a bug report that tells me that this scanner won't run with this version of the epson2 driver (epson2.so.1.0.21). YaST, reading from the sane-backends package, assure me that this driver "should' run the 640U; this, together with the fact that I have used epson2 before, gave me the unfortunate confidence that the driver, having served well in the past, could not be at fault. The bug is #583166; I found it at <http://us.generation-nt.com/bug-583166-libsane-scanner-epson- perfection-640u-fails-epson2-backend-help-198503171.html>. YaST offers me only epson2.so.1.0.21 in the sane-backends package, although the file list for this package shows that epson.so.1.0.21 is present, and that file (which the wab page containing the bug report says will work with this scanner, is indeed present: lrwxrwxrwx 1 root root 24 2011-02-16 12:05 libsane-epson2.so.1 -> libsane-epson2.so.1.0.21 -rwxr-xr-x 1 root root 189736 2010-07-06 00:41 libsane-epson2.so.1.0.21 lrwxrwxrwx 1 root root 23 2011-02-16 12:05 libsane-epson.so.1 -> libsane-epson.so.1.0.21 -rwxr-xr-x 1 root root 127592 2010-07-06 00:41 libsane-epson.so.1.0.21 Why is YaST not showing it to me? I could simply make the epson2 link point to the epson file. But I would like to understand why YaST is keeping it secret, and to cause it to allow me to make the choice in the normal way. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2011-03-05 19:00, Stan Goodman wrote:
I could simply make the epson2 link point to the epson file. But I would like to understand why YaST is keeping it secret, and to cause it to allow me to make the choice in the normal way.
I think that you should report all this in a Bugzilla ;-) - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk1ymdwACgkQtTMYHG2NR9XF9wCggB+9nOEJy28H2m0x0b1JrgUz 18YAoJQTEHURyfY/0gnNTzZrliiaMwPf =6mUh -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 05 March 2011 22:15:24 Carlos E. R. wrote:
I could simply make the epson2 link point to the epson file. But I would like to understand why YaST is keeping it secret, and to cause it to allow me to make the choice in the normal way.
I think that you should report all this in a Bugzilla ;-)
Good idea. I'll look into that tomorrow. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello, On Mar 5 20:00 Stan Goodman wrote (excerpt):
Why is YaST not showing it to me?
YaST shows you what there is in the SANE *.desc description files, see http://en.opensuse.org/SDB:Configuring_Scanners YaST uses the SANE *.desc description files as authoritative source of information. YaST does not and cannot have any kind of magic "better" knowledge which drivers work in which way for which models than what is listed in the SANE *.desc description files. In the *.desc description files on my openSUSE 11.3 system there is "Epson Perfection 640U" listed for the drivers epson2 and epkowa but "Epson Perfection 640" (without the 'U') listed for the driver epson and YaST on my openSUSE 11.3 system shows it exactly this way. You should use the "Search String" in YaST to find such entries, read the help text in YaST. It is a know issue that same devices could be listed in different *.desc description files with different model names like "Epson Perfection 640U" versus "Epson Perfection 640". Both seem to be same devices because their USB IDs are same. But it is also known that not all devices wich have same USB IDs are actually the same hardware. Furthermore not for all USB scanners their USB IDs are listed in the SANE *.desc description files. In the end it is currently not possible to rely on the USB IDs to determine in an automated way which models are same devices. As long as same devices could be listed different in different SANE *.desc description files and as long as not all USB scanners have their USB IDs listed, the user must search manually and try to find out which drivers seem to belong to his model. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 08 March 2011 10:15:56 Johannes Meixner wrote:
Hello,
On Mar 5 20:00 Stan Goodman wrote (excerpt):
Why is YaST not showing it to me?
YaST shows you what there is in the SANE *.desc description files, see http://en.opensuse.org/SDB:Configuring_Scanners
I read that page long ago, and a hard copy of it is sitting on my desk throughout the current configuration exercise. I confess that I fell into the trap of trusting what YaST was showing me; I've leearned now yet another lesson. I must repeat, however, that I have installed this 640U scanner with every oS installation on every computer, and have never had this problem before. In addition to the lack of "magic" that you mention, something has changed since the last time I configured the scanner. My guess is that the epson2 scanner used to work and that its current release is faulty, as per the bug report that I found and reported here a few days ago. Anyway, thanks for confronting me with reality.
YaST uses the SANE *.desc description files as authoritative source of information.
YaST does not and cannot have any kind of magic "better" knowledge which drivers work in which way for which models than what is listed in the SANE *.desc description files.
-----snip----- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Carlos E. R.
-
Johannes Meixner
-
Rajko M.
-
Stan Goodman