Epson GT-S50 scanner not working after upgrade to 18.04 from 16.04
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
3
down vote
favorite
Since the upgrade, my Epson scanner GT-S50 (Epkowa driver).
It gets detected (dmesg
) when plugged in:
[ 3755.680091] usb 3-4.4.1: new high-speed USB device number 8 using ehci-pci
[ 3755.789893] usb 3-4.4.1: New USB device found, idVendor=04b8, idProduct=0137
[ 3755.789895] usb 3-4.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3755.789896] usb 3-4.4.1: Product: EPSON Scanner
[ 3755.789897] usb 3-4.4.1: Manufacturer: EPSON
But when starting either "Image Scan!" or "Simple scan", no scanner can be detected.
It still somehow gets detected by Sane, because when running sane-find-scanner, it "sees" it:
...
found USB scanner (vendor=0x04b8 [Language Error], product=0x0137 [Language Error]) at libusb:003:008
...
However, scanimage -L
fails to detect it!
No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages).
If I can't find a solution, I'll consider downgrading back to 16.04.
Extra information after some extra investigation: it seems that the upgrade to Ubuntu 18.04 broke something within the Sane setup. Calling iscan
or other sane related applications lead all to fail discovering my scanner due to the following error from syslog:
iscan: io/hpmud/pp.c 627: unable to read device-id ret=-1
Other calls to sane utilities fail for the same reason:
colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1
scanimage: io/hpmud/pp.c 627: unable to read device-id ret=-1
xsane: io/hpmud/pp.c 627: unable to read device-id ret=-1
EDIT 2: Ok, found & solved the origin of the io/hpmud/pp.c 627: unable to read device-id ret=-1
messages; it is caused by the hplip's (libsane's) hpio module. I've disabled it (= commented out in /etc/sane.d/dll.d/hplip
file) and the message is now gone.
Besides, I've tried to specify my scanner to sane by adding usb 0x04b8 0x0137
in the /etc/sane.d/epkowa.conf
file and added the following UDEV rules in /etc/udev/rules.d/
as file 55-libsane.rules
:
SUBSYSTEM=="usb", ENVDEVTYPE=="usb_device", MODE=="0666"
SUBSYSTEM=="usb_device", MODE=="0666"
ATTRSidVendor=="04b8", ATTRSidProduct=="0137", MODE="0666",
GROUP="scanner", ENVlibsane_matched="yes"
But, so far still no avail... scanner stubbornly undetected :'(
Side note: don't know if that matters, but when disconnecting the scanner, I see the following message appear in /var/log/syslog
:
May 16 09:37:40 hades kernel: [22174.197243] usb 3-4.4.1: USB disconnect, device number 7
May 16 09:37:40 hades upowerd[1809]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1c.5/0000:05:00.0/0000:06:00.2/usb3/3-4/3-4.4/3-4.4.1
May 16 09:37:40 hades colord-sane[7678]: failed to receive list of devices: Failed to connect to missing device /org/freedesktop/ColorManager/devices/sysfs_EPSON_EPSON_Scanner
16.04 usb 18.04 scanner epson
add a comment |Â
up vote
3
down vote
favorite
Since the upgrade, my Epson scanner GT-S50 (Epkowa driver).
It gets detected (dmesg
) when plugged in:
[ 3755.680091] usb 3-4.4.1: new high-speed USB device number 8 using ehci-pci
[ 3755.789893] usb 3-4.4.1: New USB device found, idVendor=04b8, idProduct=0137
[ 3755.789895] usb 3-4.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3755.789896] usb 3-4.4.1: Product: EPSON Scanner
[ 3755.789897] usb 3-4.4.1: Manufacturer: EPSON
But when starting either "Image Scan!" or "Simple scan", no scanner can be detected.
It still somehow gets detected by Sane, because when running sane-find-scanner, it "sees" it:
...
found USB scanner (vendor=0x04b8 [Language Error], product=0x0137 [Language Error]) at libusb:003:008
...
However, scanimage -L
fails to detect it!
No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages).
If I can't find a solution, I'll consider downgrading back to 16.04.
Extra information after some extra investigation: it seems that the upgrade to Ubuntu 18.04 broke something within the Sane setup. Calling iscan
or other sane related applications lead all to fail discovering my scanner due to the following error from syslog:
iscan: io/hpmud/pp.c 627: unable to read device-id ret=-1
Other calls to sane utilities fail for the same reason:
colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1
scanimage: io/hpmud/pp.c 627: unable to read device-id ret=-1
xsane: io/hpmud/pp.c 627: unable to read device-id ret=-1
EDIT 2: Ok, found & solved the origin of the io/hpmud/pp.c 627: unable to read device-id ret=-1
messages; it is caused by the hplip's (libsane's) hpio module. I've disabled it (= commented out in /etc/sane.d/dll.d/hplip
file) and the message is now gone.
Besides, I've tried to specify my scanner to sane by adding usb 0x04b8 0x0137
in the /etc/sane.d/epkowa.conf
file and added the following UDEV rules in /etc/udev/rules.d/
as file 55-libsane.rules
:
SUBSYSTEM=="usb", ENVDEVTYPE=="usb_device", MODE=="0666"
SUBSYSTEM=="usb_device", MODE=="0666"
ATTRSidVendor=="04b8", ATTRSidProduct=="0137", MODE="0666",
GROUP="scanner", ENVlibsane_matched="yes"
But, so far still no avail... scanner stubbornly undetected :'(
Side note: don't know if that matters, but when disconnecting the scanner, I see the following message appear in /var/log/syslog
:
May 16 09:37:40 hades kernel: [22174.197243] usb 3-4.4.1: USB disconnect, device number 7
May 16 09:37:40 hades upowerd[1809]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1c.5/0000:05:00.0/0000:06:00.2/usb3/3-4/3-4.4/3-4.4.1
May 16 09:37:40 hades colord-sane[7678]: failed to receive list of devices: Failed to connect to missing device /org/freedesktop/ColorManager/devices/sysfs_EPSON_EPSON_Scanner
16.04 usb 18.04 scanner epson
very well researched and documented; I hope you have reported this as a bug to ubuntu; they need this
â pdc
May 13 at 22:34
Hi pdc, thanks for the advice :-) There is actually already a bug filed in Ubuntu's sane-backend package: bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012. I've added my observations to it in a comment. Hoping they'll soon find a solution. Cheers, Manu
â Manu
May 16 at 8:34
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
Since the upgrade, my Epson scanner GT-S50 (Epkowa driver).
It gets detected (dmesg
) when plugged in:
[ 3755.680091] usb 3-4.4.1: new high-speed USB device number 8 using ehci-pci
[ 3755.789893] usb 3-4.4.1: New USB device found, idVendor=04b8, idProduct=0137
[ 3755.789895] usb 3-4.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3755.789896] usb 3-4.4.1: Product: EPSON Scanner
[ 3755.789897] usb 3-4.4.1: Manufacturer: EPSON
But when starting either "Image Scan!" or "Simple scan", no scanner can be detected.
It still somehow gets detected by Sane, because when running sane-find-scanner, it "sees" it:
...
found USB scanner (vendor=0x04b8 [Language Error], product=0x0137 [Language Error]) at libusb:003:008
...
However, scanimage -L
fails to detect it!
No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages).
If I can't find a solution, I'll consider downgrading back to 16.04.
Extra information after some extra investigation: it seems that the upgrade to Ubuntu 18.04 broke something within the Sane setup. Calling iscan
or other sane related applications lead all to fail discovering my scanner due to the following error from syslog:
iscan: io/hpmud/pp.c 627: unable to read device-id ret=-1
Other calls to sane utilities fail for the same reason:
colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1
scanimage: io/hpmud/pp.c 627: unable to read device-id ret=-1
xsane: io/hpmud/pp.c 627: unable to read device-id ret=-1
EDIT 2: Ok, found & solved the origin of the io/hpmud/pp.c 627: unable to read device-id ret=-1
messages; it is caused by the hplip's (libsane's) hpio module. I've disabled it (= commented out in /etc/sane.d/dll.d/hplip
file) and the message is now gone.
Besides, I've tried to specify my scanner to sane by adding usb 0x04b8 0x0137
in the /etc/sane.d/epkowa.conf
file and added the following UDEV rules in /etc/udev/rules.d/
as file 55-libsane.rules
:
SUBSYSTEM=="usb", ENVDEVTYPE=="usb_device", MODE=="0666"
SUBSYSTEM=="usb_device", MODE=="0666"
ATTRSidVendor=="04b8", ATTRSidProduct=="0137", MODE="0666",
GROUP="scanner", ENVlibsane_matched="yes"
But, so far still no avail... scanner stubbornly undetected :'(
Side note: don't know if that matters, but when disconnecting the scanner, I see the following message appear in /var/log/syslog
:
May 16 09:37:40 hades kernel: [22174.197243] usb 3-4.4.1: USB disconnect, device number 7
May 16 09:37:40 hades upowerd[1809]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1c.5/0000:05:00.0/0000:06:00.2/usb3/3-4/3-4.4/3-4.4.1
May 16 09:37:40 hades colord-sane[7678]: failed to receive list of devices: Failed to connect to missing device /org/freedesktop/ColorManager/devices/sysfs_EPSON_EPSON_Scanner
16.04 usb 18.04 scanner epson
Since the upgrade, my Epson scanner GT-S50 (Epkowa driver).
It gets detected (dmesg
) when plugged in:
[ 3755.680091] usb 3-4.4.1: new high-speed USB device number 8 using ehci-pci
[ 3755.789893] usb 3-4.4.1: New USB device found, idVendor=04b8, idProduct=0137
[ 3755.789895] usb 3-4.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3755.789896] usb 3-4.4.1: Product: EPSON Scanner
[ 3755.789897] usb 3-4.4.1: Manufacturer: EPSON
But when starting either "Image Scan!" or "Simple scan", no scanner can be detected.
It still somehow gets detected by Sane, because when running sane-find-scanner, it "sees" it:
...
found USB scanner (vendor=0x04b8 [Language Error], product=0x0137 [Language Error]) at libusb:003:008
...
However, scanimage -L
fails to detect it!
No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages).
If I can't find a solution, I'll consider downgrading back to 16.04.
Extra information after some extra investigation: it seems that the upgrade to Ubuntu 18.04 broke something within the Sane setup. Calling iscan
or other sane related applications lead all to fail discovering my scanner due to the following error from syslog:
iscan: io/hpmud/pp.c 627: unable to read device-id ret=-1
Other calls to sane utilities fail for the same reason:
colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1
scanimage: io/hpmud/pp.c 627: unable to read device-id ret=-1
xsane: io/hpmud/pp.c 627: unable to read device-id ret=-1
EDIT 2: Ok, found & solved the origin of the io/hpmud/pp.c 627: unable to read device-id ret=-1
messages; it is caused by the hplip's (libsane's) hpio module. I've disabled it (= commented out in /etc/sane.d/dll.d/hplip
file) and the message is now gone.
Besides, I've tried to specify my scanner to sane by adding usb 0x04b8 0x0137
in the /etc/sane.d/epkowa.conf
file and added the following UDEV rules in /etc/udev/rules.d/
as file 55-libsane.rules
:
SUBSYSTEM=="usb", ENVDEVTYPE=="usb_device", MODE=="0666"
SUBSYSTEM=="usb_device", MODE=="0666"
ATTRSidVendor=="04b8", ATTRSidProduct=="0137", MODE="0666",
GROUP="scanner", ENVlibsane_matched="yes"
But, so far still no avail... scanner stubbornly undetected :'(
Side note: don't know if that matters, but when disconnecting the scanner, I see the following message appear in /var/log/syslog
:
May 16 09:37:40 hades kernel: [22174.197243] usb 3-4.4.1: USB disconnect, device number 7
May 16 09:37:40 hades upowerd[1809]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1c.5/0000:05:00.0/0000:06:00.2/usb3/3-4/3-4.4/3-4.4.1
May 16 09:37:40 hades colord-sane[7678]: failed to receive list of devices: Failed to connect to missing device /org/freedesktop/ColorManager/devices/sysfs_EPSON_EPSON_Scanner
16.04 usb 18.04 scanner epson
edited Jul 6 at 15:45
![](https://i.stack.imgur.com/E0SEH.png?s=32&g=1)
![](https://i.stack.imgur.com/E0SEH.png?s=32&g=1)
David Foerster
26k1361106
26k1361106
asked May 10 at 14:46
![](https://i.stack.imgur.com/nBu09.jpg?s=32&g=1)
![](https://i.stack.imgur.com/nBu09.jpg?s=32&g=1)
Manu
1165
1165
very well researched and documented; I hope you have reported this as a bug to ubuntu; they need this
â pdc
May 13 at 22:34
Hi pdc, thanks for the advice :-) There is actually already a bug filed in Ubuntu's sane-backend package: bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012. I've added my observations to it in a comment. Hoping they'll soon find a solution. Cheers, Manu
â Manu
May 16 at 8:34
add a comment |Â
very well researched and documented; I hope you have reported this as a bug to ubuntu; they need this
â pdc
May 13 at 22:34
Hi pdc, thanks for the advice :-) There is actually already a bug filed in Ubuntu's sane-backend package: bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012. I've added my observations to it in a comment. Hoping they'll soon find a solution. Cheers, Manu
â Manu
May 16 at 8:34
very well researched and documented; I hope you have reported this as a bug to ubuntu; they need this
â pdc
May 13 at 22:34
very well researched and documented; I hope you have reported this as a bug to ubuntu; they need this
â pdc
May 13 at 22:34
Hi pdc, thanks for the advice :-) There is actually already a bug filed in Ubuntu's sane-backend package: bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012. I've added my observations to it in a comment. Hoping they'll soon find a solution. Cheers, Manu
â Manu
May 16 at 8:34
Hi pdc, thanks for the advice :-) There is actually already a bug filed in Ubuntu's sane-backend package: bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012. I've added my observations to it in a comment. Hoping they'll soon find a solution. Cheers, Manu
â Manu
May 16 at 8:34
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
I found a word an affective workaround in the comments of the Ubuntu's sane-backends bug #1728012. I documented it as a comment on the bug report.
The problem seems to reside in missing symlinks to the epkowa (SEIKO EPSON) libraries in the /usr/lib/x86_64-linux-gnu/sane
(or, more generically, /usr/lib/$(uname -m)-linux-gnu/sane
) folder.
I thus did the following:
sudo ln -sfr /usr/lib/sane/libsane-epkowa* /usr/lib/x86_64-linux-gnu/sane
Removed the
usb 0x04b8 0x0137
entry I had added to/etc/sane.d/epkowa.conf
Added a
55-epson-libsane.rules
file to/etc/udev/rules.d/
with the following text:SUBSYSTEM=="usb", ENVDEVTYPE=="usb_device", MODE=="0666"
SUBSYSTEM=="usb_device", MODE=="0666"
ATTRSmanufacturer=="EPSON", DRIVERS=="usb", SUBSYSTEMS=="usb", ATTRSidVendor=="04b8", ATTRSidProduct=="*", MODE="0666"
ATTRSidVendor=="04b8", ATTRSidProduct=="0137", MODE="0666", GROUP="scanner", ENVlibsane_matched="yes"Finally I unplugged / plugged my scanner and tried
scanimage -L
and got this encouraging answer:
device `epkowa:interpreter:003:011' is a Epson GT-S50 flatbed scanner
Then I started
iscan
(Image Scan!) and it immediately detected my scanner. I then could successfully scan a page. Yipee! :-)
well done; great research
â pdc
May 16 at 18:48
Thank you for this! I had a similar problem with Brother DCP-J315W. Adding symlinks to/usr/lib/x86_64-linux-gnu/sane
solved the problem.
â wojciech_rak
Jun 9 at 11:24
I followed your exact instructions with the exception of the vendor and product ID in the 55-epson-libsane.rules file. I had to change them to match my Epson V19 scanner. I was able to get the IDs by running the command sane-find-scanner.
â Daniel Eagle
Aug 4 at 22:27
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
I found a word an affective workaround in the comments of the Ubuntu's sane-backends bug #1728012. I documented it as a comment on the bug report.
The problem seems to reside in missing symlinks to the epkowa (SEIKO EPSON) libraries in the /usr/lib/x86_64-linux-gnu/sane
(or, more generically, /usr/lib/$(uname -m)-linux-gnu/sane
) folder.
I thus did the following:
sudo ln -sfr /usr/lib/sane/libsane-epkowa* /usr/lib/x86_64-linux-gnu/sane
Removed the
usb 0x04b8 0x0137
entry I had added to/etc/sane.d/epkowa.conf
Added a
55-epson-libsane.rules
file to/etc/udev/rules.d/
with the following text:SUBSYSTEM=="usb", ENVDEVTYPE=="usb_device", MODE=="0666"
SUBSYSTEM=="usb_device", MODE=="0666"
ATTRSmanufacturer=="EPSON", DRIVERS=="usb", SUBSYSTEMS=="usb", ATTRSidVendor=="04b8", ATTRSidProduct=="*", MODE="0666"
ATTRSidVendor=="04b8", ATTRSidProduct=="0137", MODE="0666", GROUP="scanner", ENVlibsane_matched="yes"Finally I unplugged / plugged my scanner and tried
scanimage -L
and got this encouraging answer:
device `epkowa:interpreter:003:011' is a Epson GT-S50 flatbed scanner
Then I started
iscan
(Image Scan!) and it immediately detected my scanner. I then could successfully scan a page. Yipee! :-)
well done; great research
â pdc
May 16 at 18:48
Thank you for this! I had a similar problem with Brother DCP-J315W. Adding symlinks to/usr/lib/x86_64-linux-gnu/sane
solved the problem.
â wojciech_rak
Jun 9 at 11:24
I followed your exact instructions with the exception of the vendor and product ID in the 55-epson-libsane.rules file. I had to change them to match my Epson V19 scanner. I was able to get the IDs by running the command sane-find-scanner.
â Daniel Eagle
Aug 4 at 22:27
add a comment |Â
up vote
2
down vote
accepted
I found a word an affective workaround in the comments of the Ubuntu's sane-backends bug #1728012. I documented it as a comment on the bug report.
The problem seems to reside in missing symlinks to the epkowa (SEIKO EPSON) libraries in the /usr/lib/x86_64-linux-gnu/sane
(or, more generically, /usr/lib/$(uname -m)-linux-gnu/sane
) folder.
I thus did the following:
sudo ln -sfr /usr/lib/sane/libsane-epkowa* /usr/lib/x86_64-linux-gnu/sane
Removed the
usb 0x04b8 0x0137
entry I had added to/etc/sane.d/epkowa.conf
Added a
55-epson-libsane.rules
file to/etc/udev/rules.d/
with the following text:SUBSYSTEM=="usb", ENVDEVTYPE=="usb_device", MODE=="0666"
SUBSYSTEM=="usb_device", MODE=="0666"
ATTRSmanufacturer=="EPSON", DRIVERS=="usb", SUBSYSTEMS=="usb", ATTRSidVendor=="04b8", ATTRSidProduct=="*", MODE="0666"
ATTRSidVendor=="04b8", ATTRSidProduct=="0137", MODE="0666", GROUP="scanner", ENVlibsane_matched="yes"Finally I unplugged / plugged my scanner and tried
scanimage -L
and got this encouraging answer:
device `epkowa:interpreter:003:011' is a Epson GT-S50 flatbed scanner
Then I started
iscan
(Image Scan!) and it immediately detected my scanner. I then could successfully scan a page. Yipee! :-)
well done; great research
â pdc
May 16 at 18:48
Thank you for this! I had a similar problem with Brother DCP-J315W. Adding symlinks to/usr/lib/x86_64-linux-gnu/sane
solved the problem.
â wojciech_rak
Jun 9 at 11:24
I followed your exact instructions with the exception of the vendor and product ID in the 55-epson-libsane.rules file. I had to change them to match my Epson V19 scanner. I was able to get the IDs by running the command sane-find-scanner.
â Daniel Eagle
Aug 4 at 22:27
add a comment |Â
up vote
2
down vote
accepted
up vote
2
down vote
accepted
I found a word an affective workaround in the comments of the Ubuntu's sane-backends bug #1728012. I documented it as a comment on the bug report.
The problem seems to reside in missing symlinks to the epkowa (SEIKO EPSON) libraries in the /usr/lib/x86_64-linux-gnu/sane
(or, more generically, /usr/lib/$(uname -m)-linux-gnu/sane
) folder.
I thus did the following:
sudo ln -sfr /usr/lib/sane/libsane-epkowa* /usr/lib/x86_64-linux-gnu/sane
Removed the
usb 0x04b8 0x0137
entry I had added to/etc/sane.d/epkowa.conf
Added a
55-epson-libsane.rules
file to/etc/udev/rules.d/
with the following text:SUBSYSTEM=="usb", ENVDEVTYPE=="usb_device", MODE=="0666"
SUBSYSTEM=="usb_device", MODE=="0666"
ATTRSmanufacturer=="EPSON", DRIVERS=="usb", SUBSYSTEMS=="usb", ATTRSidVendor=="04b8", ATTRSidProduct=="*", MODE="0666"
ATTRSidVendor=="04b8", ATTRSidProduct=="0137", MODE="0666", GROUP="scanner", ENVlibsane_matched="yes"Finally I unplugged / plugged my scanner and tried
scanimage -L
and got this encouraging answer:
device `epkowa:interpreter:003:011' is a Epson GT-S50 flatbed scanner
Then I started
iscan
(Image Scan!) and it immediately detected my scanner. I then could successfully scan a page. Yipee! :-)
I found a word an affective workaround in the comments of the Ubuntu's sane-backends bug #1728012. I documented it as a comment on the bug report.
The problem seems to reside in missing symlinks to the epkowa (SEIKO EPSON) libraries in the /usr/lib/x86_64-linux-gnu/sane
(or, more generically, /usr/lib/$(uname -m)-linux-gnu/sane
) folder.
I thus did the following:
sudo ln -sfr /usr/lib/sane/libsane-epkowa* /usr/lib/x86_64-linux-gnu/sane
Removed the
usb 0x04b8 0x0137
entry I had added to/etc/sane.d/epkowa.conf
Added a
55-epson-libsane.rules
file to/etc/udev/rules.d/
with the following text:SUBSYSTEM=="usb", ENVDEVTYPE=="usb_device", MODE=="0666"
SUBSYSTEM=="usb_device", MODE=="0666"
ATTRSmanufacturer=="EPSON", DRIVERS=="usb", SUBSYSTEMS=="usb", ATTRSidVendor=="04b8", ATTRSidProduct=="*", MODE="0666"
ATTRSidVendor=="04b8", ATTRSidProduct=="0137", MODE="0666", GROUP="scanner", ENVlibsane_matched="yes"Finally I unplugged / plugged my scanner and tried
scanimage -L
and got this encouraging answer:
device `epkowa:interpreter:003:011' is a Epson GT-S50 flatbed scanner
Then I started
iscan
(Image Scan!) and it immediately detected my scanner. I then could successfully scan a page. Yipee! :-)
edited Jul 6 at 15:43
![](https://i.stack.imgur.com/E0SEH.png?s=32&g=1)
![](https://i.stack.imgur.com/E0SEH.png?s=32&g=1)
David Foerster
26k1361106
26k1361106
answered May 16 at 10:05
![](https://i.stack.imgur.com/nBu09.jpg?s=32&g=1)
![](https://i.stack.imgur.com/nBu09.jpg?s=32&g=1)
Manu
1165
1165
well done; great research
â pdc
May 16 at 18:48
Thank you for this! I had a similar problem with Brother DCP-J315W. Adding symlinks to/usr/lib/x86_64-linux-gnu/sane
solved the problem.
â wojciech_rak
Jun 9 at 11:24
I followed your exact instructions with the exception of the vendor and product ID in the 55-epson-libsane.rules file. I had to change them to match my Epson V19 scanner. I was able to get the IDs by running the command sane-find-scanner.
â Daniel Eagle
Aug 4 at 22:27
add a comment |Â
well done; great research
â pdc
May 16 at 18:48
Thank you for this! I had a similar problem with Brother DCP-J315W. Adding symlinks to/usr/lib/x86_64-linux-gnu/sane
solved the problem.
â wojciech_rak
Jun 9 at 11:24
I followed your exact instructions with the exception of the vendor and product ID in the 55-epson-libsane.rules file. I had to change them to match my Epson V19 scanner. I was able to get the IDs by running the command sane-find-scanner.
â Daniel Eagle
Aug 4 at 22:27
well done; great research
â pdc
May 16 at 18:48
well done; great research
â pdc
May 16 at 18:48
Thank you for this! I had a similar problem with Brother DCP-J315W. Adding symlinks to
/usr/lib/x86_64-linux-gnu/sane
solved the problem.â wojciech_rak
Jun 9 at 11:24
Thank you for this! I had a similar problem with Brother DCP-J315W. Adding symlinks to
/usr/lib/x86_64-linux-gnu/sane
solved the problem.â wojciech_rak
Jun 9 at 11:24
I followed your exact instructions with the exception of the vendor and product ID in the 55-epson-libsane.rules file. I had to change them to match my Epson V19 scanner. I was able to get the IDs by running the command sane-find-scanner.
â Daniel Eagle
Aug 4 at 22:27
I followed your exact instructions with the exception of the vendor and product ID in the 55-epson-libsane.rules file. I had to change them to match my Epson V19 scanner. I was able to get the IDs by running the command sane-find-scanner.
â Daniel Eagle
Aug 4 at 22:27
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1034528%2fepson-gt-s50-scanner-not-working-after-upgrade-to-18-04-from-16-04%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
very well researched and documented; I hope you have reported this as a bug to ubuntu; they need this
â pdc
May 13 at 22:34
Hi pdc, thanks for the advice :-) There is actually already a bug filed in Ubuntu's sane-backend package: bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012. I've added my observations to it in a comment. Hoping they'll soon find a solution. Cheers, Manu
â Manu
May 16 at 8:34