Scanner stopped working

JosephS · 05-07-2018, 01:56 PM

I have been using simple-scan for a while and it has been working fine. The last few weeks it has stopped working and I can't figure out why this is. I have searched the NET but am not finding a solution. I don't know how to search out and find the solution. Does anyone have experience with this to help figure out what has happened?

Code:

joe@Bunsenlabs:~$ sudo lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 1058:0830 Western Digital Technologies, Inc. 
Bus 001 Device 003: ID 03f0:0324 Hewlett-Packard SK-2885 keyboard
Bus 001 Device 002: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
Bus 001 Device 007: ID 04b8:080d Seiko Epson Corp. Stylus CX4500/4600
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Epson is the scanner that I am using: cx4600

I have also tried gscan2pdf

These are not finding the scanner.

jlinkels · 05-07-2018, 02:13 PM

First, open an terminal and enter this command a normal user:

Code:

scanimage -L

If the scanner is not listed, retry with sudo, or as root.
It tells whether the scanner driver is aware of the presence of the scanner.

If the scanner is not listed in both attempts, do this, again in a terminal window:

Code:

tail -f /var/log/syslog

and unplug and replug the scanner.

Copy the lines which are recorder during the unplug/replug action and paste them here. Copy from a terminal is mark the text with the mouse, then SHF-CTRL-C to copy.

jlinkels

hazel · 05-07-2018, 02:17 PM

Some things to try from the command line:
1) sane-find-scanner. Does this find it? If not,
2) sudo sane-find-scanner.

If you can find it as root but not as yourself, it's a permissions problem.

This model is an all-in-1, so whether it's recognised as a printer or a scanner will depend on udev and may have changed recently. So check the usb numbers (04b8:080d) in /lib/udev/rules.d and /etc/udev/rules.d. Find out what group it's being assigned to at boot (lp or scanner) and make sure you are a member of that group.

3) Can you find and use it as a printer?

4) Does sudo scanimage -L find it?

AwesomeMachine · 05-07-2018, 05:49 PM

It could be that the scanner hardware failed. Scanners are the most prone to failure of any peripheral device.

JosephS · 05-08-2018, 11:01 PM

[QUOTE=jlinkels;5851760]First, open an terminal and enter this command a normal user:

Code:

scanimage -L

joe@Bunsenlabs:~$ scanimage -L
device `epson2:libusb:001:006' is a Epson CX4600 flatbed scanner

Code:

joe@Bunsenlabs:~$ sudo sane-find-scanner
[sudo] password for joe: 

  # 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.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
found USB scanner (vendor=0x04b8 [EPSON], product=0x080d [USB MFP]) at libusb:001:006
  # 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.

without sudo I got permission errors.

Code:

joe@Bunsenlabs:~$ ls /lib/udev/rules.d
40-usb_modeswitch.rules  60-pcmcia.rules                   70-power-switch.rules              77-mm-nokia-port-types.rules              80-mm-candidate.rules
42-usb-hid-pm.rules      60-persistent-alsa.rules          70-uaccess.rules                   77-mm-pcmcia-device-blacklist.rules       80-net-setup-link.rules
50-firmware.rules        60-persistent-input.rules         71-seat.rules                      77-mm-platform-serial-whitelist.rules     80-networking.rules
50-udev-default.rules    60-persistent-serial.rules        73-idrac.rules                     77-mm-qdl-device-blacklist.rules          80-udisks2.rules
55-dm.rules              60-persistent-storage-dm.rules    73-seat-late.rules                 77-mm-simtech-port-types.rules            85-hdparm.rules
60-cdrom_id.rules        60-persistent-storage.rules       75-net-description.rules           77-mm-telit-port-types.rules              85-hwclock.rules
60-crda.rules            60-persistent-storage-tape.rules  75-persistent-net-generator.rules  77-mm-usb-device-blacklist.rules          85-regulatory.rules
60-drm.rules             60-persistent-v4l.rules           75-probe_mtd.rules                 77-mm-usb-serial-adapters-greylist.rules  90-alsa-restore.rules
60-fuse.rules            61-accelerometer.rules            75-tty-description.rules           77-mm-x22x-port-types.rules               90-pulseaudio.rules
60-gnupg.rules           64-btrfs.rules                    77-mm-cinterion-port-types.rules   77-mm-zte-port-types.rules                95-udev-late.rules
60-keyboard.rules        64-xorg-xkb.rules                 77-mm-ericsson-mbm.rules           77-nm-olpc-mesh.rules                     95-upower-csr.rules
60-libgphoto2-6.rules    69-libmtp.rules                   77-mm-huawei-net-port-types.rules  78-sound-card.rules                       95-upower-hid.rules
60-libpisock9.rules      69-xorg-vmmouse.rules             77-mm-longcheer-port-types.rules   80-btrfs-lvm.rules                        95-upower-wup.rules
60-libsane.rules         70-btrfs.rules                    77-mm-mtk-port-types.rules         80-drivers.rules                          99-systemd.rules

Code:

joe@Bunsenlabs:~$ ls /etc/udev/rules.d
70-persistent-cd.rules  70-persistent-net.rules

I checked a number of the rules (ones with udev and usb) and didn't find 04b8:080d

I haven't used this as a printer for a while, only as a scanner. Will probably look for a black and white laser in the future.

hazel · 05-09-2018, 06:26 AM

Actually if scanimage -L works, there is no need to try sane-find-scanner. Scanimage -L is a more powerful test as it confirms that sane has a driver for the device. sane-find-scanner merely tells you that there is a usb device which claims to be a scanner. Udev rules are also irrelevant in this case: if there was a permissions problem, scanimage would not have found the scanner.

The next thing is to try to use the scanner with sane debugging switched on. Sane has very powerful debugging facilities. sane-find-scanner suggested that you read the manual page for your backend (driver), so that is the next step. You will probably find the name of the epson driver you are using in /etc/sane/dll.d. Read its man page and it will tell you how to switch debugging on. Sane itself has an excellent man page.

Quote:

Originally Posted by sane man page

If your scanner is still not found, try setting the various environment variables that are available to assist in debugging. The environment variables are documented in the relevant manual pages. For example, to get the maximum amount of debug information when testing a Mustek SCSI scanner, set environment variables SANE_DEBUG_DLL, SANE_DEBUG_MUSTEK, and SANE_DEBUG_SANEI_SCSI to 128 and then invoke scanimage -L . The debug messages for the dll backend tell if the mustek backend was found and loaded at all. The mustek messages explain what the mustek backend is doing while the SCSI debugging shows the low level handling. If you can't find out what's going on by checking the messages carefully, contact the sane-devel mailing list for help (see REPORTING BUGS below).

jlinkels · 05-09-2018, 07:26 AM

Quote:

Originally Posted by JosephS

without sudo I got permission errors.

Quote:

Originally Posted by Hazel

if there was a permissions problem, scanimage would not have found the scanner.

There is a permissions problem.

And you are right, permissions are arranged by udev. The most obvious question: are you member of the scanner group?

Since your scanner is recognized, it must exist somewhere in the /dev tree. Unfortunately my memory doesn't serve me well at the moment, I do not recall the correct device name and I don't have the time right now to recollect the knowledge. I hope someone else is faster posting the information than me.

jlinkels