Epson Perfection 1670 (Snapscan) isn't working, some kind of crash after first initialisation

Bug #1308451 reported by Andreas Ritter
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sane-backends (Ubuntu)
Invalid
Undecided
Rolf Leggewie

Bug Description

I have an Epson Perfection 1670, which worked with the snapscan - Module very good with older ubuntu releases.

In 14.04 there is a bug, which causes the following behaviour:

1. Connect scanner, sane-find-scanner recognize it and xsane find it, too.
2. Click on scan or even only on preview the scanner seems to initialize (moves shortly), after that nothing happens and after about 30 seconds a error message pops up, can't find scanner. (similar behavior with scanimage on terminal)
3. scanner could not found with xsane or sane-find-scanner.
4. Disconnect / Reconnect scanner from power -> begin with 1 again.

Installed packages:
dpkg -l |grep sane
ii libksane-data 4:4.13.0-0ubuntu1 all scanner library (data files)
ii libksane0 4:4.13.0-0ubuntu1 amd64 scanner library (runtime)
ii libsane:amd64 1.0.23-3ubuntu3 amd64 API library for scanners
ii libsane-common 1.0.23-3ubuntu3 amd64 API library for scanners -- documentation and support files
ii libsane-hpaio 3.14.3-0ubuntu3 amd64 HP SANE backend for multi-function peripherals
ii libsane-perl 0.05-2build1 amd64 Perl bindings for the SANE (Scanner Access Now Easy) Project
ii sane 1.0.14-9 amd64 scanner graphical frontends
ii sane-utils 1.0.23-3ubuntu3 amd64 API library for scanners -- utilities
ii xsane 0.998-5ubuntu1 amd64 featureful graphical frontend for SANE (Scanner Access Now Easy)
ii xsane-common 0.998-5ubuntu1 all featureful graphical frontend for SANE (Scanner Access Now Easy)

Andreas Ritter (eddie8)
description: updated
Revision history for this message
Dr. Juergen Helmers (juergen-helmers) wrote :

Also does not work for me anymore ever since the update to 14.04. Have to reboot to Windows to use the device.

scanimage -L does list the device at first, it also is listed (always) doing an lsusb. Trying to use a scanning application (skanlite, xsane or vuescan) each app is not able to find the device and it does not show up any longer with scanimage -L but still under lsusb.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in sane-backends (Ubuntu):
status: New → Confirmed
Revision history for this message
Dr. Juergen Helmers (juergen-helmers) wrote :

I solved my problem by redownloading the firmware file which I had place in /etc/sane.d. The file that works for me :

fc6ef4674ffe8d2afa403f79cc8dbc0e esfw30.bin

Scanning works now.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

Jürgen, thank you for the follow-up. Is there something that needs to be done to make this work automatically or can this ticket be closed?

Changed in sane-backends (Ubuntu):
assignee: nobody → Rolf Leggewie (r0lf)
Revision history for this message
Rolf Leggewie (r0lf) wrote :

Andreas, does this work for you now or is anything left to be done?

Revision history for this message
Rolf Leggewie (r0lf) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Changed in sane-backends (Ubuntu):
status: Confirmed → Incomplete
Rolf Leggewie (r0lf)
Changed in sane-backends (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Andreas Ritter (eddie8) wrote :

Sorry for the late response. I don't have the scanner any more and I also switched to fedora, so I can't test any updates.
But in 2014, I know that I had the same firmware as Jürgen, so I don't think that was the problem there.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.