Discussion:
Cannot connect to my Fujitsu ScanSnap S1300i:
(too old to reply)
Max Westen
2017-12-04 09:31:06 UTC
Permalink
Trying to get my installation going.
Running Arch-Linux 4.13.12-1-ARCH on an Apple MacBookPro3,1.

Installed Sane by using sudo pacman -S sane
Installed version is: 1.0.27

A scan for the device gives me the following:
[***@Luminox sane.d]$ sane-find-scanner -q
could not open USB device 0x05ac/0x8502 at 002:002: Access denied
(insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 002:001: Access denied
(insufficient permissions)
could not open USB device 0x05ac/0x021b at 007:003: Access denied
(insufficient permissions)
could not open USB device 0x05ac/0x8242 at 007:002: Access denied
(insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 007:001: Access denied
(insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 006:001: Access denied
(insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 005:001: Access denied
(insufficient permissions)
found USB scanner (vendor=0x04c5 [FUJITSU], product=0x128d [ScanSnap
S1300i]) at libusb:001:005
could not open USB device 0x1d6b/0x0002 at 001:001: Access denied
(insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 004:001: Access denied
(insufficient permissions)
could not open USB device 0x05ac/0x1000 at 003:002: Access denied
(insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 003:001: Access denied
(insufficient permissions)

I've installed the file 1300i_0D12.nal in /usr/share/sane/epjitsu as per
instructions of man sane-epjitsu and made sure the file
/etc/sane.d/epjitsu.conf has the correct line for the firmware and usb

I commented out all other devices except for net and apjitsu in
/etc/sane.d/dll.conf, to minimise waittime.

when issuing the command scanimage -L it gives me no device.

after doing an export SANE_DEBUG_EPJITSU=30 and thn giving a scanimage -L,
it gives me the following output:

[***@Luminox sane.d]$ scanimage -L
[sanei_debug] Setting debug level of epjitsu to 30.
[epjitsu] sane_init: start
[epjitsu] sane_init: epjitsu backend 1.0.31, from sane-backends 1.0.27
[epjitsu] sane_init: finish
[epjitsu] sane_get_devices: start
[epjitsu] sane_get_devices: reading config file epjitsu.conf
[epjitsu] sane_get_devices: firmware
'/usr/share/sane/epjitsu/1300i_0D12.nal'
[epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x128d'
[epjitsu] attach_one: start 'libusb:001:005'
[epjitsu] attach_one: init struct
[epjitsu] attach_one: connect fd
[epjitsu] connect_fd: start
[epjitsu] connect_fd: opening USB device
[epjitsu] connect_fd: could not open device: 3
[epjitsu] connect_fd: finish
[epjitsu] destroy: start
[epjitsu] teardown_buffers: start
[epjitsu] teardown_buffers: finish
[epjitsu] destroy: finish
[epjitsu] sane_get_devices: found 0 scanner(s)
[epjitsu] sane_get_devices: finish

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).
[epjitsu] sane_exit: start
[epjitsu] sane_exit: finish


I'm not sure what to do next......
Does anyone have a hint as where to search for a solution ?

Thanks in advance!


Max Westen

Technical blog (EN): http://DLMax.org
Genealogy site (EN/NL): https://FamWesten.nl / https://History.FamWesten.nl
Persoonlijk blog (NL): http://MaxWesten.nl
Max Westen
2017-12-04 10:47:01 UTC
Permalink
Follow up:

Tried the other USB-port.
detecting the scanner gives me a hit. Immediately rescanning and the device
is 'gone':

[***@Luminox test]$ scanadf -L
device `epjitsu:libusb:002:002' is a FUJITSU ScanSnap S1300i scanner
[***@Luminox test]$ scanadf -L
[***@Luminox test]$


After some trying, this behaviour keeps the same...

I've prepared a comammandline with the next USB instance, unplug the USB,
put it back in and then execute the command. Yay it works !

[***@Luminox test]$ scanadf -d "epjitsu:libusb:002:009" --source "ADF
Duplex" --mode Color --resolution 300dpi -o /tmp/20171204_113055/page_%04d
--page-height 376
scanadf: rounded value of page-height from 376 to 375.999
Scanned document /tmp/20171204_113055/page_0001
Scanned document /tmp/20171204_113055/page_0002
Scanned 2 pages
[***@Luminox test]$ scanadf -L
device `epjitsu:libusb:002:009' is a FUJITSU ScanSnap S1300i scanner
[***@Luminox test]$ scanadf -L
[***@Luminox test]$

but immediately running a scanadf -L afterwards, gets me the correct ID,
giving the command another time, makes it disappear....

I can't get my head around this, but this isn't really workable....


Any help is greatly appreciated!

Max
m. allan noah
2017-12-05 11:50:30 UTC
Permalink
Sounds like the typical Linux USB problem. Please see this statement
from the sane 1.0.27 release notes:

Note 3: The Linux USB3 workaround which was added in version 1.0.25 is
now disabled by default. If you have difficulty using a scanner which
previously worked, or intermittent scanner availability, try setting
the new environment variable SANE_USB_WORKAROUND=1 before starting
your frontend.

Please give this a try, and let us know if it helps.

allan
Post by Max Westen
Tried the other USB-port.
detecting the scanner gives me a hit. Immediately rescanning and the device
device `epjitsu:libusb:002:002' is a FUJITSU ScanSnap S1300i scanner
After some trying, this behaviour keeps the same...
I've prepared a comammandline with the next USB instance, unplug the USB,
put it back in and then execute the command. Yay it works !
Duplex" --mode Color --resolution 300dpi -o /tmp/20171204_113055/page_%04d
--page-height 376
scanadf: rounded value of page-height from 376 to 375.999
Scanned document /tmp/20171204_113055/page_0001
Scanned document /tmp/20171204_113055/page_0002
Scanned 2 pages
device `epjitsu:libusb:002:009' is a FUJITSU ScanSnap S1300i scanner
but immediately running a scanadf -L afterwards, gets me the correct ID,
giving the command another time, makes it disappear....
I can't get my head around this, but this isn't really workable....
Any help is greatly appreciated!
Max
--
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
--
"well, I stand up next to a mountain- and I chop it down with the edge
of my hand"
--
sane-devel mailing list: sane-***@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-***@lists.alioth.debian.org
Max Westen
2017-12-05 19:10:22 UTC
Permalink
Hi Allan,

I've tried setting the env setting SANE_USB_WORKAROUND=1 before connecting
my scanner.
Output is still the same. The first scanimage -L returns the device. The
second (or sometimes the third time) calling the same line and it's gone.

I've looked at the specs of this macbookpro; it only contains 2 USB 2.0
ports, so it shouldn't be a USB 3 issue....

https://everymac.com/systems/apple/macbook_pro/specs/macbook-pro-core-2-duo-2.2-15-santa-rosa-specs.html

I also tried installing Arch (same setup as on macbookpro) with sane on
another laptop lying around (with lower specs, so definately not usable as
workstation) and the same scanner and that works flawless.... :(

Is there anything I could try or anything I could do to try to get it
resolved ?

Thanks again!

Max
m. allan noah
2017-12-05 20:36:26 UTC
Permalink
Well, you could git bisect between sane-backends 1.0.25 and 1.0.27,
and find the commit where it breaks.

Can you show the command you used to set the env var?

allan
Post by Max Westen
Hi Allan,
I've tried setting the env setting SANE_USB_WORKAROUND=1 before connecting
my scanner.
Output is still the same. The first scanimage -L returns the device. The
second (or sometimes the third time) calling the same line and it's gone.
I've looked at the specs of this macbookpro; it only contains 2 USB 2.0
ports, so it shouldn't be a USB 3 issue....
https://everymac.com/systems/apple/macbook_pro/specs/macbook-pro-core-2-duo-2.2-15-santa-rosa-specs.html
I also tried installing Arch (same setup as on macbookpro) with sane on
another laptop lying around (with lower specs, so definately not usable as
workstation) and the same scanner and that works flawless.... :(
Is there anything I could try or anything I could do to try to get it
resolved ?
Thanks again!
Max
--
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
--
"well, I stand up next to a mountain- and I chop it down with the edge
of my hand"
--
sane-devel mailing list: sane-***@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-***@lists.alioth.debian.org
Max Westen
2017-12-06 11:35:09 UTC
Permalink
Mea culpa!

Found the culprit....
SANE DID work..... but I had scanbd installed too, so scanbd had the usb
connection with sane and kept the device locked.....
I disabled scanbd, as I remembered installing that and that it might
interfere with SANE... and so it did!

Sorry for having bothered you and thanks for the help!

Max
Louis Lagendijk
2017-12-06 17:28:19 UTC
Permalink
Post by Max Westen
Mea culpa!
Found the culprit....
SANE DID work..... but I had scanbd installed too, so scanbd had the
usb connection with sane and kept the device locked.....
I disabled scanbd, as I remembered installing that and that it might
interfere with SANE... and so it did!
Sorry for having bothered you and thanks for the help!
Max
Well, make sure scanbd and the sane backend have their own dll.conf
where scanbd uses the "normal" one (including the backend for your
scanner), and give the normal clients only see the net backend as you
normally would for saned.

Configure scanbd to use the a separate directory where your copy the
relevant config for your backend and a dll.conf that is configured for
your backend. Remove all backends from the normal dll.conf (normally in
/etc/saned.d) but the net backend

All frontends will then use net to connect to scanbd/saned that in its
turn connects to the scanner

BR, Louis
--
sane-devel mailing list: sane-***@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-***@lists.alioth.debian.org
Max Westen
2017-12-06 20:55:55 UTC
Permalink
Hi Louis,

Thanks, I do have only 'net' in the /etc/sane.d/dll.conf and only 'epjitsu'
in the /etc/scanbd/sane.d/dll.conf
Scanning using the button works (YAY!), but connecting via the net config
fails....
logging gives me this when issuing a scanimage -L:

Dec 06 21:41:38 Luminox systemd[1]: Started Scanner button polling Service.
Dec 06 21:41:38 Luminox sudo[1550]: pam_unix(sudo:session): session closed
for user root
Dec 06 21:41:38 Luminox scanbd[1553]: /usr/sbin/scanbd: dbus match
type='signal',interface='org.freedesktop.Hal.Manager'
Dec 06 21:41:39 Luminox scanbd[1553]: /usr/sbin/scanbd: Not Primary Owner
(-1)
Dec 06 21:41:39 Luminox scanbd[1553]: /usr/sbin/scanbd: Name Error
(Connection ":1.208" is not allowed to own the service
"de.kmux.scanbd.server" due to security policies in the configuration file)
Dec 06 21:43:02 Luminox dbus-daemon[290]: [system] Activating via systemd:
service name='org.freedesktop.Avahi'
unit='dbus-org.freedesktop.Avahi.service' requested by ':1.211' (uid=1000
pid=1567 comm="scanimage -L ")
Dec 06 21:43:02 Luminox dbus-daemon[290]: [system] Activation via systemd
failed for unit 'dbus-org.freedesktop.Avahi.service': Unit
dbus-org.freedesktop.Avahi.service not found.
Dec 06 21:43:02 Luminox systemd[1]: Started Scanner Service ([::1]:60064).
Dec 06 21:43:02 Luminox scanbm[1570]: /usr/sbin/scanbm: dbus match
type='signal',interface='org.freedesktop.Hal.Manager'
Dec 06 21:43:02 Luminox dbus-daemon[290]: [system] Activating via systemd:
service name='de.kmux.scanbd.server'
unit='dbus-de.kmux.scanbd.server.service' requested by ':1.212' (uid=2
pid=1570 comm="/usr/sbin/scanbm -c /etc/scanbd/scanbd.conf ")
Dec 06 21:43:27 Luminox dbus-daemon[290]: [system] Failed to activate
service 'de.kmux.scanbd.server': timed out (service_start_timeout=25000ms)
Dec 06 21:43:27 Luminox saned[1571]: saned (AF-indep+IPv6) from
sane-backends 1.0.27 starting up
Dec 06 21:43:27 Luminox saned[1571]: check_host: access by remote host: ::1
Dec 06 21:43:27 Luminox saned[1571]: init: access granted to saned-user@::1
Dec 06 21:43:30 Luminox saned[1571]: saned exiting
Dec 06 21:43:30 Luminox dbus-daemon[290]: [system] Activating via systemd:
service name='de.kmux.scanbd.server'
unit='dbus-de.kmux.scanbd.server.service' requested by ':1.212' (uid=2
pid=1570 comm="/usr/sbin/scanbm -c /etc/scanbd/scanbd.conf ")
Dec 06 21:43:55 Luminox dbus-daemon[290]: [system] Failed to activate
service 'de.kmux.scanbd.server': timed out (service_start_timeout=25000ms)
Loading...