Bug 975881 - epson scanner v500 - epkowa driver does not work any more on x64 system since 13.2
epson scanner v500 - epkowa driver does not work any more on x64 system since...
Status: RESOLVED DUPLICATE of bug 976813
Classification: openSUSE
Product: openSUSE Distribution
Classification: openSUSE
Component: Kernel
13.2
x86-64 openSUSE 13.2
: P5 - None : Major (vote)
: ---
Assigned To: E-mail List
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-04-17 20:37 UTC by Jean-Claude Dole
Modified: 2016-04-27 13:47 UTC (History)
1 user (show)

See Also:
Found By: Community User
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Scanner config and Error msg (45.83 KB, application/gzip)
2016-04-17 20:37 UTC, Jean-Claude Dole
Details
Scan test on 13.1 (45.27 KB, image/png)
2016-04-21 19:35 UTC, Jean-Claude Dole
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jean-Claude Dole 2016-04-17 20:37:26 UTC
Created attachment 673265 [details]
Scanner config and Error msg

Configuration with yast2 give a warning that the driver may not work on 64 bits system.
The scanner is recognized.
Commands are accepted.
Cannot make test successfully; the scanner scan but does not output anythings.

Using iscan, I got a more precise error : Scanner have no write access.
When searching a directory to save a scan, got a disk full warning.

This scanner work correctly on windows 10.
This scanner was working correctly 2 years ago on Opensuse 13.1.
Comment 1 Johannes Meixner 2016-04-18 09:37:51 UTC
The iscan software is proprietary third-party driver software.

There is nothing what we (openSUSE) can do in case of issues
with third-party software.

Accordingly the issue is invalid for us (openSUSE).

You can only contact those wherefrom you got the proprietary
software for any kind of help and support, see
"Third-Party Scanner Drivers" at
https://en.opensuse.org/SDB:Configuring_Scanners

FYI:

Regarding using 32-bit scanner driver software:
In general on 64-bit x86_64 systems you can also run
traditional x86 32-bit software.
To use a traditional 32-bit scanner driver software
you must run the whole scanning software as 32-bit software.
This means you have to use the 32-bit sane-backends RPM package.
To avoid conflicts you probably have to remove your currently
installed 64-bit sane-backends RPM package and instead install
only the 32-bit sane-backends RPM package.
When the scanning base software is 32-bit software
it should probably work to use a 32-bit scanner driver software.

Regarding "no write access":
See "USB scanner access permissions via udev" at
https://en.opensuse.org/SDB:Configuring_Scanners

Regarding "disk full warning":
In general no software works when your disk is full.
Scanning in higher resolution results tons
of Megabytes up to Gigabytes of scanning data
that must be stored on your disk, cf.
https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c26
Comment 2 Jean-Claude Dole 2016-04-18 14:51:50 UTC
Hello.
You don't view carrefully the attached files.
They have nothing to do with iscan.
They are relative to yast2.

Concerning the disk full warning there is 60Gb free so I think it is sufficient.

scanimage return this alert :
"# scanimage -vvv -T
scanimage: scanning image of size 1696x3743 pixels at 24 bits/pixel
scanimage: acquiring RGB frame, 8 bits/sample
scanimage: reading one scanline, 5088 bytes...  PASS
scanimage: reading one byte...          PASS
scanimage: stepped read, 2 bytes...     PASS
scanimage: stepped read, 4 bytes...     PASS
scanimage: stepped read, 8 bytes...     PASS
scanimage: stepped read, 16 bytes...    PASS
scanimage: stepped read, 32 bytes...    PASS
scanimage: stepped read, 64 bytes...    PASS
scanimage: stepped read, 128 bytes...   PASS
scanimage: stepped read, 256 bytes...   PASS
scanimage: stepped read, 512 bytes...   PASS
scanimage: stepped read, 1024 bytes...  PASS
scanimage: stepped read, 2048 bytes...  PASS
scanimage: stepped read, 4096 bytes...  PASS
scanimage: stepped read, 8192 bytes...  PASS
scanimage: stepped read, 8191 bytes...  PASS
scanimage: stepped read, 4095 bytes...  PASS
scanimage: stepped read, 2047 bytes...  PASS
scanimage: stepped read, 1023 bytes...  PASS
scanimage: stepped read, 511 bytes...   PASS
scanimage: stepped read, 255 bytes...   PASS
scanimage: stepped read, 127 bytes...   PASS
scanimage: stepped read, 63 bytes...    PASS
scanimage: stepped read, 31 bytes...    PASS
scanimage: stepped read, 15 bytes...    PASS
scanimage: stepped read, 7 bytes...     PASS
scanimage: stepped read, 3 bytes...     PASS
Closing device
libusb: warning [libusb_close] internal signalling read failed, closing anyway"
^Cscanimage: received signal 2
scanimage: trying to stop scanner                                                                                                                        
^Cscanimage: received signal 2                                                                                                                      
scanimage: aborting                                                                        
"
                                                              
and this :
"# scanimage -vvv --format tiff > /tmp/scan2.tiff                                                                                           
scanimage: scanning image of size 1696x3743 pixels at 24 bits/pixel                                                                                      
scanimage: acquiring RGB frame                                                                                                                           
scanimage: min/max graylevel value = 8/255
scanimage: read 19044384 bytes in total
Closing device
libusb: warning [libusb_close] internal signalling read failed, closing anyway
^Cscanimage: received signal 2
scanimage: trying to stop scanner
^Cscanimage: received signal 2
scanimage: aborting
"

And as said : "This scanner was working correctly 2 years ago on Opensuse 13.1."

I am trying your recommendation by using traditional x86 32-bit software, and will give news asap.
Comment 3 Jean-Claude Dole 2016-04-18 17:30:19 UTC
While trying x86 driver, I have to keep x86_64 version of kipi-plugins-acquireimage and libksane0 because changing to 32 bits need to change many other things.
I installed the 32 bits scanner driver.
I still have a warning that the driver may failed on 64 bits system.
It does not work.

# lsusb
Bus 002 Device 004: ID 04b8:0130 Seiko Epson Corp. GT-X770 [Perfection V500]

OK

# sane-find-scanner -v
This is sane-find-scanner from sane-backends 1.0.24

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

found USB scanner (vendor=0x04b8 [EPSON], product=0x0130 [EPSON Scanner]) at libusb:002:004
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.
done

OK

# scanimage -L
device `epkowa:interpreter:002:004' is a Epson (unknown model) flatbed scanner
device `epkowa:interpreter:002:004' is a Epson (unknown model) flatbed scanner
device `epkowa:interpreter:002:004' is a Epson (unknown model) flatbed scanner
device `epkowa:interpreter:002:004' is a Epson (unknown model) flatbed scanner
device `epkowa:interpreter:002:004' is a Epson (unknown model) flatbed scanner
device `epkowa:interpreter:002:004' is a Epson (unknown model) flatbed scanner
device `epkowa:interpreter:002:004' is a Epson (unknown model) flatbed scanner
device `epkowa:interpreter:002:004' is a Epson (unknown model) flatbed scanner
device `epkowa:interpreter:002:004' is a Epson (unknown model) flatbed scanner
device `epkowa:interpreter:002:004' is a Epson (unknown model) flatbed scanner
device `epkowa:interpreter:002:004' is a Epson (unknown model) flatbed scanner

OK

# scanimage -vvv -T
scanimage: open of device epkowa:interpreter:002:004 failed: Invalid argument
Calling sane_exit
scanimage: finished
Comment 4 Jean-Claude Dole 2016-04-21 19:35:03 UTC
Created attachment 674046 [details]
Scan test on 13.1
Comment 5 Jean-Claude Dole 2016-04-21 19:37:03 UTC
Same scanner, Same drivers and it's work on 13.1