Interupting Simple Scan killed scanner

Bug #706727 reported by fossil
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Simple Scan
Expired
Undecided
Unassigned

Bug Description

Running Ubuntu 10.04.1 LTS, Kernel 2.6.32-27-generic. and SimpleScan 1.0.3

I've been using the aptly named Simple Scan for some months and it has worked beatifully.

Until....

Started a scan at 1200 X 1200 dpi
Stopped scan part way through and scanning stopped.
In preferences, change to a lower resolution.
Could not restart scan at lower resolution. Could not restart any scan all.
Looked inside scanner and scanning bar was stopped in the middle of the glass.
Tried unplugging USB and re-plugging USB to no effect.
Tried de-powering / re-powering scanner to no effect
Tried plugging scanner into a different machine to no effect.

Simplescan.log reads:
** (simple-scan:4861): DEBUG: Starting Simple Scan 1.0.3, PID=4861
** (simple-scan:4861): DEBUG: Restoring window to 908x1020 pixels
** (simple-scan:4861): DEBUG: sane_init () -> SANE_STATUS_GOOD
** (simple-scan:4861): DEBUG: SANE version 1.0.20
** (simple-scan:4861): DEBUG: Requesting redetection of scan devices
** (simple-scan:4861): DEBUG: Processing request
** (simple-scan:4861): DEBUG: sane_get_devices () -> SANE_STATUS_GOOD
** (simple-scan:4861): DEBUG: Device: name="snapscan:libusb:001:010" vendor="EPSON" model="EPSON Scanner" type="flatbed scanner"
** (simple-scan:4861): DEBUG: Requesting scan at 300 dpi from device 'snapscan:libusb:001:010'
** (simple-scan:4861): DEBUG: scanner_scan ("snapscan:libusb:001:010", 300, SCAN_SINGLE)
** (simple-scan:4861): DEBUG: Processing request
** (simple-scan:4861): DEBUG: sane_open ("snapscan:libusb:001:010") -> SANE_STATUS_INVAL

It seems like the scanner might have died.
Bummer.
Any questions or suggestions?

Thanks, Brett

Revision history for this message
Michael Nagel (nailor) wrote :

Hi Brett, that sounds pretty bad! I have some questions that might get me a better picture of the situation:

- do you have any news? could you revive the scanner?
- what exact model is it?
- did you ever before stop scanning?
- do you think it is possible that the whole thing was just coincidence?

Changed in simple-scan:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Simple Scan because there has been no activity for 60 days.]

Changed in simple-scan:
status: Incomplete → Expired
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.