Initiate scan from Fujitsu ix500 to Linux over USB
I want to start a scan by pressing the scanner's scan button and have the data delivered to a Linux box.
Unfortunately, I can't use the scanner's WLAN interface, so I'm stuck with USB.
Is there any chance to make this work?
Here's a few speculative ways to achieve this. Did you have success with any of these?
- Run a client on Linux that (partially) adheres to the protocol that's implemented in ScanSnap's Windows and macOS clients (unlikely)
- Install a USB-to-Ethernet adapter on the scanner and get the scanner to use it as an ethernet device. I could then scan to FTP.
- Install the official Windows client via Wine.
linux usb scanner
add a comment |
I want to start a scan by pressing the scanner's scan button and have the data delivered to a Linux box.
Unfortunately, I can't use the scanner's WLAN interface, so I'm stuck with USB.
Is there any chance to make this work?
Here's a few speculative ways to achieve this. Did you have success with any of these?
- Run a client on Linux that (partially) adheres to the protocol that's implemented in ScanSnap's Windows and macOS clients (unlikely)
- Install a USB-to-Ethernet adapter on the scanner and get the scanner to use it as an ethernet device. I could then scan to FTP.
- Install the official Windows client via Wine.
linux usb scanner
see also stackoverflow.com/questions/50166248/…
– Wolfgang Fahl
Dec 18 '18 at 11:40
add a comment |
I want to start a scan by pressing the scanner's scan button and have the data delivered to a Linux box.
Unfortunately, I can't use the scanner's WLAN interface, so I'm stuck with USB.
Is there any chance to make this work?
Here's a few speculative ways to achieve this. Did you have success with any of these?
- Run a client on Linux that (partially) adheres to the protocol that's implemented in ScanSnap's Windows and macOS clients (unlikely)
- Install a USB-to-Ethernet adapter on the scanner and get the scanner to use it as an ethernet device. I could then scan to FTP.
- Install the official Windows client via Wine.
linux usb scanner
I want to start a scan by pressing the scanner's scan button and have the data delivered to a Linux box.
Unfortunately, I can't use the scanner's WLAN interface, so I'm stuck with USB.
Is there any chance to make this work?
Here's a few speculative ways to achieve this. Did you have success with any of these?
- Run a client on Linux that (partially) adheres to the protocol that's implemented in ScanSnap's Windows and macOS clients (unlikely)
- Install a USB-to-Ethernet adapter on the scanner and get the scanner to use it as an ethernet device. I could then scan to FTP.
- Install the official Windows client via Wine.
linux usb scanner
linux usb scanner
asked Mar 17 '18 at 16:37
ensens
1527
1527
see also stackoverflow.com/questions/50166248/…
– Wolfgang Fahl
Dec 18 '18 at 11:40
add a comment |
see also stackoverflow.com/questions/50166248/…
– Wolfgang Fahl
Dec 18 '18 at 11:40
see also stackoverflow.com/questions/50166248/…
– Wolfgang Fahl
Dec 18 '18 at 11:40
see also stackoverflow.com/questions/50166248/…
– Wolfgang Fahl
Dec 18 '18 at 11:40
add a comment |
1 Answer
1
active
oldest
votes
scanimage supports the ix500 scanner over usb
example:
scanimage -L
device `fujitsu:ScanSnap iX500:59766' is a FUJITSU ScanSnap iX500 scanner
So what's missing it the trigger from the button. I found
https://www.camroncade.com/cloud-scanner-with-raspberry-pi-fujitsu-ix500-2/
mentioning a scannerbuttond package. There is a german description at:
https://wiki.ubuntuusers.de/scanbuttond/
and an english one at- http://virantha.com/2014/03/17/one-touch-scanning-with-fujitsu-scansnap-in-linux/
Both are a bit outdated but give some hints on the general idea.
Here is a description of a trial with an Ubuntu 18.04 LTS virtual machine.
After installing
sudo apt-get install scanbuttond
I connected the scanner by assigning it's USB device to the virtual machine.
scanimage -L
worked as described above.
sudo sane-find-scanner
# 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.
found USB scanner (vendor=0x04c5 [Fujitsu], product=0x132b [ScanSnap iX500]) at libusb:003:007
could not fetch string descriptor: Input/output error
could not fetch string descriptor: Input/output error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Input/output error
# 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.
looks promising.
sudo scanbd -d7 -f
starts the daemon in foreground with debugging set to a high level.
In my case i had to comment out some scanner drivers in dll.conf to get rid of results from a different scanner that was available on my network.
Due to bug https://bugs.launchpad.net/ubuntu/+source/scanbd/+bug/1747115
I also had to change the users / group settings.
diff --git a/scanbd/scanbd.conf b/scanbd/scanbd.conf
index 5d74933..1356236 100644
--- a/scanbd/scanbd.conf
+++ b/scanbd/scanbd.conf
@@ -39,8 +39,8 @@ global {
# ArchLinux (ArchLinux doesn't have saned user)
# user = daemon
# *BSD
- # user = root
- user = saned
+ user = root
+ #user = saned
I added the full path to my test script 5 times in scanbd.conf and 4 times in scanner.d/fujitsu.conf:
root@fur:/etc/scanbd# grep scan.sh scanbd.conf
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
root@fur:/etc/scanbd# cd scanner.d/
root@fur:/etc/scanbd/scanner.d# grep scan.sh fujitsu.conf
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
with the script scan.sh being:
#!/bin/bash
# WF 2018-12-18
echo "scanning"
echo "scan button pressed on ix500" >> /tmp/ix500.log
i then tested with
sudo scanbd -f
in one terminal and
tail -f /tmp/ix500.log
in another.
scanbd: dbus match type='signal',interface='org.freedesktop.Hal.Manager'
scanbd: SANE_CONFIG_DIR not set
scanbd: Not Primary Owner (-1)
scanbd: Name Error (Connection ":1.96" is not allowed to own the service "de.kmux.scanbd.server" due to security policies in the configuration file)
scanbd: trigger action for page-loaded for device fujitsu:ScanSnap iX500:59766 with script /home/wf/bin/scan.sh
scanning
shows on the daemon's foreground output
and
scan button pressed on ix500
from here it seems be all downhill - the environment variables being passed are described in the scanbd.conf file.
e.g. modifying scan.sh to:
#!/bin/bash
# WF 2018-12-18
echo "scanning"
cat << EOF >> /tmp/ix500.log
scan button pressed on ix500
function: $SCANBD_FUNCTION
mode: $SCANBD_FUNCTION_MODE
device: $SCANBD_DEVICE
action: $SCANBD_ACTION
EOF
will create
scan button pressed on ix500
function: 1
mode: Lineart
device: fujitsu:ScanSnap iX500:59766
action: scan
on the press of the scan button :-)
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1305301%2finitiate-scan-from-fujitsu-ix500-to-linux-over-usb%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
scanimage supports the ix500 scanner over usb
example:
scanimage -L
device `fujitsu:ScanSnap iX500:59766' is a FUJITSU ScanSnap iX500 scanner
So what's missing it the trigger from the button. I found
https://www.camroncade.com/cloud-scanner-with-raspberry-pi-fujitsu-ix500-2/
mentioning a scannerbuttond package. There is a german description at:
https://wiki.ubuntuusers.de/scanbuttond/
and an english one at- http://virantha.com/2014/03/17/one-touch-scanning-with-fujitsu-scansnap-in-linux/
Both are a bit outdated but give some hints on the general idea.
Here is a description of a trial with an Ubuntu 18.04 LTS virtual machine.
After installing
sudo apt-get install scanbuttond
I connected the scanner by assigning it's USB device to the virtual machine.
scanimage -L
worked as described above.
sudo sane-find-scanner
# 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.
found USB scanner (vendor=0x04c5 [Fujitsu], product=0x132b [ScanSnap iX500]) at libusb:003:007
could not fetch string descriptor: Input/output error
could not fetch string descriptor: Input/output error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Input/output error
# 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.
looks promising.
sudo scanbd -d7 -f
starts the daemon in foreground with debugging set to a high level.
In my case i had to comment out some scanner drivers in dll.conf to get rid of results from a different scanner that was available on my network.
Due to bug https://bugs.launchpad.net/ubuntu/+source/scanbd/+bug/1747115
I also had to change the users / group settings.
diff --git a/scanbd/scanbd.conf b/scanbd/scanbd.conf
index 5d74933..1356236 100644
--- a/scanbd/scanbd.conf
+++ b/scanbd/scanbd.conf
@@ -39,8 +39,8 @@ global {
# ArchLinux (ArchLinux doesn't have saned user)
# user = daemon
# *BSD
- # user = root
- user = saned
+ user = root
+ #user = saned
I added the full path to my test script 5 times in scanbd.conf and 4 times in scanner.d/fujitsu.conf:
root@fur:/etc/scanbd# grep scan.sh scanbd.conf
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
root@fur:/etc/scanbd# cd scanner.d/
root@fur:/etc/scanbd/scanner.d# grep scan.sh fujitsu.conf
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
with the script scan.sh being:
#!/bin/bash
# WF 2018-12-18
echo "scanning"
echo "scan button pressed on ix500" >> /tmp/ix500.log
i then tested with
sudo scanbd -f
in one terminal and
tail -f /tmp/ix500.log
in another.
scanbd: dbus match type='signal',interface='org.freedesktop.Hal.Manager'
scanbd: SANE_CONFIG_DIR not set
scanbd: Not Primary Owner (-1)
scanbd: Name Error (Connection ":1.96" is not allowed to own the service "de.kmux.scanbd.server" due to security policies in the configuration file)
scanbd: trigger action for page-loaded for device fujitsu:ScanSnap iX500:59766 with script /home/wf/bin/scan.sh
scanning
shows on the daemon's foreground output
and
scan button pressed on ix500
from here it seems be all downhill - the environment variables being passed are described in the scanbd.conf file.
e.g. modifying scan.sh to:
#!/bin/bash
# WF 2018-12-18
echo "scanning"
cat << EOF >> /tmp/ix500.log
scan button pressed on ix500
function: $SCANBD_FUNCTION
mode: $SCANBD_FUNCTION_MODE
device: $SCANBD_DEVICE
action: $SCANBD_ACTION
EOF
will create
scan button pressed on ix500
function: 1
mode: Lineart
device: fujitsu:ScanSnap iX500:59766
action: scan
on the press of the scan button :-)
add a comment |
scanimage supports the ix500 scanner over usb
example:
scanimage -L
device `fujitsu:ScanSnap iX500:59766' is a FUJITSU ScanSnap iX500 scanner
So what's missing it the trigger from the button. I found
https://www.camroncade.com/cloud-scanner-with-raspberry-pi-fujitsu-ix500-2/
mentioning a scannerbuttond package. There is a german description at:
https://wiki.ubuntuusers.de/scanbuttond/
and an english one at- http://virantha.com/2014/03/17/one-touch-scanning-with-fujitsu-scansnap-in-linux/
Both are a bit outdated but give some hints on the general idea.
Here is a description of a trial with an Ubuntu 18.04 LTS virtual machine.
After installing
sudo apt-get install scanbuttond
I connected the scanner by assigning it's USB device to the virtual machine.
scanimage -L
worked as described above.
sudo sane-find-scanner
# 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.
found USB scanner (vendor=0x04c5 [Fujitsu], product=0x132b [ScanSnap iX500]) at libusb:003:007
could not fetch string descriptor: Input/output error
could not fetch string descriptor: Input/output error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Input/output error
# 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.
looks promising.
sudo scanbd -d7 -f
starts the daemon in foreground with debugging set to a high level.
In my case i had to comment out some scanner drivers in dll.conf to get rid of results from a different scanner that was available on my network.
Due to bug https://bugs.launchpad.net/ubuntu/+source/scanbd/+bug/1747115
I also had to change the users / group settings.
diff --git a/scanbd/scanbd.conf b/scanbd/scanbd.conf
index 5d74933..1356236 100644
--- a/scanbd/scanbd.conf
+++ b/scanbd/scanbd.conf
@@ -39,8 +39,8 @@ global {
# ArchLinux (ArchLinux doesn't have saned user)
# user = daemon
# *BSD
- # user = root
- user = saned
+ user = root
+ #user = saned
I added the full path to my test script 5 times in scanbd.conf and 4 times in scanner.d/fujitsu.conf:
root@fur:/etc/scanbd# grep scan.sh scanbd.conf
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
root@fur:/etc/scanbd# cd scanner.d/
root@fur:/etc/scanbd/scanner.d# grep scan.sh fujitsu.conf
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
with the script scan.sh being:
#!/bin/bash
# WF 2018-12-18
echo "scanning"
echo "scan button pressed on ix500" >> /tmp/ix500.log
i then tested with
sudo scanbd -f
in one terminal and
tail -f /tmp/ix500.log
in another.
scanbd: dbus match type='signal',interface='org.freedesktop.Hal.Manager'
scanbd: SANE_CONFIG_DIR not set
scanbd: Not Primary Owner (-1)
scanbd: Name Error (Connection ":1.96" is not allowed to own the service "de.kmux.scanbd.server" due to security policies in the configuration file)
scanbd: trigger action for page-loaded for device fujitsu:ScanSnap iX500:59766 with script /home/wf/bin/scan.sh
scanning
shows on the daemon's foreground output
and
scan button pressed on ix500
from here it seems be all downhill - the environment variables being passed are described in the scanbd.conf file.
e.g. modifying scan.sh to:
#!/bin/bash
# WF 2018-12-18
echo "scanning"
cat << EOF >> /tmp/ix500.log
scan button pressed on ix500
function: $SCANBD_FUNCTION
mode: $SCANBD_FUNCTION_MODE
device: $SCANBD_DEVICE
action: $SCANBD_ACTION
EOF
will create
scan button pressed on ix500
function: 1
mode: Lineart
device: fujitsu:ScanSnap iX500:59766
action: scan
on the press of the scan button :-)
add a comment |
scanimage supports the ix500 scanner over usb
example:
scanimage -L
device `fujitsu:ScanSnap iX500:59766' is a FUJITSU ScanSnap iX500 scanner
So what's missing it the trigger from the button. I found
https://www.camroncade.com/cloud-scanner-with-raspberry-pi-fujitsu-ix500-2/
mentioning a scannerbuttond package. There is a german description at:
https://wiki.ubuntuusers.de/scanbuttond/
and an english one at- http://virantha.com/2014/03/17/one-touch-scanning-with-fujitsu-scansnap-in-linux/
Both are a bit outdated but give some hints on the general idea.
Here is a description of a trial with an Ubuntu 18.04 LTS virtual machine.
After installing
sudo apt-get install scanbuttond
I connected the scanner by assigning it's USB device to the virtual machine.
scanimage -L
worked as described above.
sudo sane-find-scanner
# 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.
found USB scanner (vendor=0x04c5 [Fujitsu], product=0x132b [ScanSnap iX500]) at libusb:003:007
could not fetch string descriptor: Input/output error
could not fetch string descriptor: Input/output error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Input/output error
# 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.
looks promising.
sudo scanbd -d7 -f
starts the daemon in foreground with debugging set to a high level.
In my case i had to comment out some scanner drivers in dll.conf to get rid of results from a different scanner that was available on my network.
Due to bug https://bugs.launchpad.net/ubuntu/+source/scanbd/+bug/1747115
I also had to change the users / group settings.
diff --git a/scanbd/scanbd.conf b/scanbd/scanbd.conf
index 5d74933..1356236 100644
--- a/scanbd/scanbd.conf
+++ b/scanbd/scanbd.conf
@@ -39,8 +39,8 @@ global {
# ArchLinux (ArchLinux doesn't have saned user)
# user = daemon
# *BSD
- # user = root
- user = saned
+ user = root
+ #user = saned
I added the full path to my test script 5 times in scanbd.conf and 4 times in scanner.d/fujitsu.conf:
root@fur:/etc/scanbd# grep scan.sh scanbd.conf
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
root@fur:/etc/scanbd# cd scanner.d/
root@fur:/etc/scanbd/scanner.d# grep scan.sh fujitsu.conf
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
with the script scan.sh being:
#!/bin/bash
# WF 2018-12-18
echo "scanning"
echo "scan button pressed on ix500" >> /tmp/ix500.log
i then tested with
sudo scanbd -f
in one terminal and
tail -f /tmp/ix500.log
in another.
scanbd: dbus match type='signal',interface='org.freedesktop.Hal.Manager'
scanbd: SANE_CONFIG_DIR not set
scanbd: Not Primary Owner (-1)
scanbd: Name Error (Connection ":1.96" is not allowed to own the service "de.kmux.scanbd.server" due to security policies in the configuration file)
scanbd: trigger action for page-loaded for device fujitsu:ScanSnap iX500:59766 with script /home/wf/bin/scan.sh
scanning
shows on the daemon's foreground output
and
scan button pressed on ix500
from here it seems be all downhill - the environment variables being passed are described in the scanbd.conf file.
e.g. modifying scan.sh to:
#!/bin/bash
# WF 2018-12-18
echo "scanning"
cat << EOF >> /tmp/ix500.log
scan button pressed on ix500
function: $SCANBD_FUNCTION
mode: $SCANBD_FUNCTION_MODE
device: $SCANBD_DEVICE
action: $SCANBD_ACTION
EOF
will create
scan button pressed on ix500
function: 1
mode: Lineart
device: fujitsu:ScanSnap iX500:59766
action: scan
on the press of the scan button :-)
scanimage supports the ix500 scanner over usb
example:
scanimage -L
device `fujitsu:ScanSnap iX500:59766' is a FUJITSU ScanSnap iX500 scanner
So what's missing it the trigger from the button. I found
https://www.camroncade.com/cloud-scanner-with-raspberry-pi-fujitsu-ix500-2/
mentioning a scannerbuttond package. There is a german description at:
https://wiki.ubuntuusers.de/scanbuttond/
and an english one at- http://virantha.com/2014/03/17/one-touch-scanning-with-fujitsu-scansnap-in-linux/
Both are a bit outdated but give some hints on the general idea.
Here is a description of a trial with an Ubuntu 18.04 LTS virtual machine.
After installing
sudo apt-get install scanbuttond
I connected the scanner by assigning it's USB device to the virtual machine.
scanimage -L
worked as described above.
sudo sane-find-scanner
# 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.
found USB scanner (vendor=0x04c5 [Fujitsu], product=0x132b [ScanSnap iX500]) at libusb:003:007
could not fetch string descriptor: Input/output error
could not fetch string descriptor: Input/output error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Input/output error
# 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.
looks promising.
sudo scanbd -d7 -f
starts the daemon in foreground with debugging set to a high level.
In my case i had to comment out some scanner drivers in dll.conf to get rid of results from a different scanner that was available on my network.
Due to bug https://bugs.launchpad.net/ubuntu/+source/scanbd/+bug/1747115
I also had to change the users / group settings.
diff --git a/scanbd/scanbd.conf b/scanbd/scanbd.conf
index 5d74933..1356236 100644
--- a/scanbd/scanbd.conf
+++ b/scanbd/scanbd.conf
@@ -39,8 +39,8 @@ global {
# ArchLinux (ArchLinux doesn't have saned user)
# user = daemon
# *BSD
- # user = root
- user = saned
+ user = root
+ #user = saned
I added the full path to my test script 5 times in scanbd.conf and 4 times in scanner.d/fujitsu.conf:
root@fur:/etc/scanbd# grep scan.sh scanbd.conf
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
root@fur:/etc/scanbd# cd scanner.d/
root@fur:/etc/scanbd/scanner.d# grep scan.sh fujitsu.conf
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
script = "/home/wf/bin/scan.sh"
with the script scan.sh being:
#!/bin/bash
# WF 2018-12-18
echo "scanning"
echo "scan button pressed on ix500" >> /tmp/ix500.log
i then tested with
sudo scanbd -f
in one terminal and
tail -f /tmp/ix500.log
in another.
scanbd: dbus match type='signal',interface='org.freedesktop.Hal.Manager'
scanbd: SANE_CONFIG_DIR not set
scanbd: Not Primary Owner (-1)
scanbd: Name Error (Connection ":1.96" is not allowed to own the service "de.kmux.scanbd.server" due to security policies in the configuration file)
scanbd: trigger action for page-loaded for device fujitsu:ScanSnap iX500:59766 with script /home/wf/bin/scan.sh
scanning
shows on the daemon's foreground output
and
scan button pressed on ix500
from here it seems be all downhill - the environment variables being passed are described in the scanbd.conf file.
e.g. modifying scan.sh to:
#!/bin/bash
# WF 2018-12-18
echo "scanning"
cat << EOF >> /tmp/ix500.log
scan button pressed on ix500
function: $SCANBD_FUNCTION
mode: $SCANBD_FUNCTION_MODE
device: $SCANBD_DEVICE
action: $SCANBD_ACTION
EOF
will create
scan button pressed on ix500
function: 1
mode: Lineart
device: fujitsu:ScanSnap iX500:59766
action: scan
on the press of the scan button :-)
edited Dec 18 '18 at 16:03
answered Dec 18 '18 at 10:54
Wolfgang FahlWolfgang Fahl
154110
154110
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1305301%2finitiate-scan-from-fujitsu-ix500-to-linux-over-usb%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
see also stackoverflow.com/questions/50166248/…
– Wolfgang Fahl
Dec 18 '18 at 11:40