Trusty, scanner, workaround for error: [epson2] e2_ext_read: cancel request received

Asked by Katie Urey on 2016-05-13

This concerns setting up an EPSON Perfection 1650 Scanner to work with Trusty.

The scanner is recognized but xsane bails out with this error:

[epson2] e2_ext_read: cancel request received

I think I have the configs set OK and that this is a known bug. However, I have not found useful work-arounds.

Please send links to useful work-arounds..

many thanks,

Katie U

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu sane-backends Edit question
Assignee:
No assignee Edit question
Solved by:
Katie Urey
Solved:
2016-05-15
Last query:
2016-05-15
Last reply:
2016-05-15

If you run:

sudo xsane

Does it work OK? Might be a permission issue on the scanner device...

Katie Urey (ksurey) said : #2

Yes, it works when I run sudo xsane.

Katie Urey (ksurey) said : #4

the hint took me to udev documentation.

I have changed a udev rule file in this directory

/lib/udev/rules.d

in this file
 40-libsane.rules

The stub of my scanner was listed. I removed the # comment from one line.
     grep -i -A1 'Epson Perfection 1650' /lib/udev/rules.d/40-*
          # /lib/udev/rules.d/40-libsane.rules:# Epson Perfection 1650 | Epson GT-8200U | Epson GT-8200UF
          /lib/udev/rules.d/40-libsane.rules:Epson Perfection 1650 | Epson Perfection 1650 PHOTO
          /lib/udev/rules.d/40-libsane.rules-ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0110", ENV{libsane_matched}="yes"

Then reloaded the udev rules.
             sudo udevadm control --reload-rules

the scanner then worked from my user account. It did complain when closing the program. This complaint went away when I forced a new ~/.sane directory to be created by renaming the old ~/.sane directory.

I had previously updated the /etc/sane.d/epson2.conf file ( the suggestion in 1565846)

So, I will mark this as resolved and send a Thank You!

gnc (gnc20) said : #5

Then reloaded the udev rules.
             sudo udevadm control --reload-rules

the scanner then worked from my user account. It did complain when https://audacity.onl/ https://findmyiphone.onl/ https://origin.onl/