Package: libsane
Version: 1.0.27-3.2
Severity: important
File: sane
Dear Maintainer,
I have been using an old scanner of type CanoScan N1240U/LiDE 30 without
problems
since Debian 7, connected to a port replicator or directly to a USB port, on a
variety of computers (both 32 and 64 bits).
Since Debian 10, scanning functions have ceased to work properly, but this
seems
to affect only the 64b environment.
1. Context A
Thinkpad L570, fresh installation of Debian 10.3 64b, GNOME, Xorg.
CanoScan LiDE 30.
Xsane 0.999.
SimpleScan 3.30.1.1.
2. Initialization difficulties
a) Neither SimpleScan nor XSane detect the scanner automatically, despite
the
fact that the command lsusb recognizes and lists it.
b) Solution : execute first sane-find-scanner, which returns appropriately
found USB scanner (vendor=0x04a9 [Canon], product=0x220e [CanoScan]) at
libusb:001:019
(or equivalent, depending on which port the scanner is attached to).
And then execute scanimage -L, which returns appropriately
Created directory: /var/lib/snmp/mib_indexes
device `plustek:libusb:001:019' is a Canon CanoScan N1240U/LiDE30
flatbed scanner
c) Whereupon both SimpleScan and Xsane detect the scanner. However, they
still do
not function correctly.
3. SimpleScan can only scan once.
a) Start SimpleScan and scan a document page. Everything works perfectly.
b) Either "delete" the page or select "start again", and then "scan";
SimpleScan
enters the scanning loop but
b.i) does not drive the scanner (there is no movement of the scanning
head);
b.ii) it just displays an entirely black preview.
From then on, the only way to scan another page is to exit SimpleScan,
and
re-launch the program. It is impossible to scan a succession of pages
within
a single SimpleScan session.
4. SimpleScan gets into an inconsistent state.
a) After a while, even that procedure fails. When requested to scan,
SimpleScan
enters the state "contacting scanner" -- which lasts for a minute or
so, then
outputs the error message "failed to scan/cannot start scan". In this
situation,
scanimage -L still lists the scanner.
b) After a few attempts, SimpleScan quickly returns an error "failed to
scan/no
scanners available". In that situation, repeated invocations of sane-
find-scanner
and scanimage -L produce no result : scanimage -L no longer detects the
(still
attached) scanner, despite lsusb and sane-find-scanner having
identified it.
The only way to restart SimpleScan is to unplug the scanner, reconnect
it, and
redo the whole initialization procedure before invoking SimpleScan.
5. Xsane does not even scan once.
a) Starting Xsane after an initializatin leads to a very lengthy phase (1
minute or
more) where Xsane remains "scanning for devices".
When scanning e.g. with "acquire preview" results in the following:
a.i) Xsane does not drive the scanner;
a.ii) it just displays an entirely black page.
b) There is no way to make Xsane work, even for just one scan. Repeating
scans
always leads to a black page. Loading the CanoScan LiDE 30 device
parameters
in the "preferences" menu of Xsane produces the same result.
c) Exiting and re-launching Xsane then results in a different behaviour:
upon
requesting a scan, Xsane immediately returns an error message
"Failed to start scanner: error during device I-O".
Checking immediately with scanimage -L shows that the scanner is no
longer
detected. Re-executing sane-find-scanner and then scanimage -L does not
help
as long as the scanner has not been unplugged and replugged.
Context B.
Dell I9100, fresh installation of Debian 10.3 32b, XFCE.
CanoScan LiDE 30.
Xsane 0.999.
6. Scanning works.
a) Invoking Xsane directly, without the initialization with sane-find-
scanner
and scanimage -L, the program recognizes the scanner within seconds and
is
ready to work.
b) Scanning works flawlessly. "Acquire preview" results in a proper
display of
the document being scanned.
Conclusion.
There seems to be a serious inconsisteny in the scanning environment of the 64b
Debian
implementation that results in a faulty and incoherent behaviour of various
scanning
front-ends. They cannot really scan, and after a while the device drivers /
backend is
left in a perturbated state where the connected scanner is detected by some
utilities
but not by others. The problems occur whether the scanner is connected directly
to a
USB port, or via a port replicator. The problems do not occur in a 32b Debian
system.
-- System Information:
Debian Release: 10.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libsane:amd64 depends on:
ii acl 2.2.53-4
ii adduser 3.118
ii libavahi-client3 0.7-4+b1
ii libavahi-common3 0.7-4+b1
ii libc6 2.28-10
ii libgphoto2-6 2.5.22-3
ii libgphoto2-port12 2.5.22-3
ii libieee1284-3 0.2.11-13
ii libjpeg62-turbo 1:1.5.2-2+b1
ii libsane-common 1.0.27-3.2
ii libsnmp30 5.7.3+dfsg-5
ii libssl1.1 1.1.1d-0+deb10u2
ii libtiff5 4.1.0+git191117-2~deb10u1
ii libusb-1.0-0 2:1.0.22-2
ii udev 241-7~deb10u3
Versions of packages libsane:amd64 recommends:
ii sane-utils 1.0.27-3.2
Versions of packages libsane:amd64 suggests:
ii avahi-daemon 0.7-4+b1
ii hplip 3.18.12+dfsg0-2
-- no debconf information
