Your message dated Sat, 08 May 2021 15:48:40 +0000 with message-id <[email protected]> and subject line Bug#954096: fixed in sane-backends 1.0.32-1 has caused the Debian Bug report #954096, regarding sane: Scanning utilities work only once, or not at all, leave scanning backend in inconsistent state. to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 954096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954096 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---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
--- End Message ---
--- Begin Message ---Source: sane-backends Source-Version: 1.0.32-1 Done: Jörg Frings-Fürst <[email protected]> We believe that the bug you reported is fixed in the latest version of sane-backends, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jörg Frings-Fürst <[email protected]> (supplier of updated sane-backends package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sat, 01 May 2021 12:09:06 +0200 Source: sane-backends Architecture: source Version: 1.0.32-1 Distribution: experimental Urgency: medium Maintainer: Jörg Frings-Fürst <[email protected]> Changed-By: Jörg Frings-Fürst <[email protected]> Closes: 887745 954096 971592 978902 984747 987805 987837 Changes: sane-backends (1.0.32-1) experimental; urgency=medium . * New Upstream release: - Refresh patches: + patches/0040-remove_git.patch + patches/0045-disable_lock_test_at_build_time.patch + patches/0060-cross.patch + patches/0140-avahi.patch + patches/0145-avahi.patch + patches/0150-i386-test.patch + patches/0155-hurd_PATH_MAX.patch + patches/0600-scanimage_manpage.patch + patches/0705-kfreebsd.patch + patches/0725-fix_link_60-libsane_rule.patch - Remove not longer needed patches: + patches/0100-source_spelling.patch + patches/0125-multiarch_dll_search_path.patch + patches/0055-Fix_build_error.patch + patches/0165-respect_local_only_parameter.patch + patches/0170-return_empty_list_when_local_devices_requested.patch - New Patches: + patches/0175-fix_tests.patch to fix build - tests. + patches/0605-fix_groff-warnings.patch to fix groff warnings. - Fix ftbfs with autoconf 2.70 (Closes: #978902). * debian/copyright: - Refresh to the new upstream release. * debian/libsane1.symbols: - Add 1 new symbol. - Remove MISSING from last release. * debian/libsane-common.lintian-overrides: - Remove double lines. * New debian/libsane1.lintian-overrides to override afe spelling. * TROUBLESHOOTING.Debian: - Add part if sane-backends and tlp runs on the same system (Closes: #954096, #887745). * Declare compliance with Debian Policy 4.5.1 (No changes needed). * Fix FTCBFS: Annotate python3-minimal dependency :any. (Closes: #984747). - Thanks to Helmut Grohne <[email protected]>. * debian/sane-utils.postrm: - Fix package doesn't purge cleanly (user/group not purged) (Closes: #987837). - Fix package doesn't purge cleanly (fix test with pathfind()) (Closes: #987805). * Fix filtering out libsane-dll (Closes: #971592): - Cherry-picked from 1.0.25-4.1+deb9u2 (Thanks to Sylvain Beucler <[email protected]>). Checksums-Sha1: 3e9b2f531b94533c2dc48b33adf2db6b470d3c62 2470 sane-backends_1.0.32-1.dsc 9a8cac79ec415e99d05204ebd6470918c60f2e13 5747181 sane-backends_1.0.32.orig.tar.gz de5da6cd8be67c442330aa26a2ebac51c2d4686c 79632 sane-backends_1.0.32-1.debian.tar.xz Checksums-Sha256: 424ede5530e2329995781b757c6af5e6f5cb9ceabe55a2246de28673bc8c2d4e 2470 sane-backends_1.0.32-1.dsc 58c645762fe42739ae03e42fc197fb8b59e4aaebae482881654420c54a3a7229 5747181 sane-backends_1.0.32.orig.tar.gz 4f646bf1167b4e4192c895f0eec25b53e9957bb2c17fd1e20942ef8d06ba6233 79632 sane-backends_1.0.32-1.debian.tar.xz Files: 5d567649b391d70066aeb653fbba2eb0 2470 graphics optional sane-backends_1.0.32-1.dsc b493e22dc89ea7853519a545176da209 5747181 graphics optional sane-backends_1.0.32.orig.tar.gz 9f1b45f33dee6ab9ae11142115cdd2c9 79632 graphics optional sane-backends_1.0.32-1.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmCWrvEACgkQiNJCh6LY mLFv7A/+MR5N0SbZPfcKj4BmczePAENEFf+91Qy41+F2sqp8gAKIM2BI93yDX7MW 4N8ON8BZ9xBFDfH5AMxPIkOcpYU89kb8ROlvq6iNyvld92MMdcGHoIf4aCFuw1Q6 klGF3gKhDpAhhDk7JW/7x+PHyupk82KeL/0fPXr/NmPMu5aqsWQU7A2Nvd4RBzDW wBUfwst2NWqQHLqXWwlVvjZCjdpGHJ8/Mpah+MbA1gPYXV+Bl7/OiEq/cDTO2k62 NW23TO5L/6VOEx1K5LDPdpYsL6lIXTtIBKaif8TxF31t+LnN47ArHcWwxUsQGaV+ DHcG+Nb53WzSdt3yU2mT1XZVAIY9hzcCpTajEc2KzdhYXOK8xVWHmYJ61WfHXSHA M8c5vV41tHbaHX4huKL9Yh1P7ve52KrtRVAM1DRwhmsc0P+Ae082uhgd+O2BE1Hn uIcSN0ctK7+sDoHcAmAwSG8I/dwiG2xcTXJj/9bXuHoOEw4CYC6CQBZk+NSs/Zi8 vUr67pL4N1hapLDx/w1MWFn6VeRnqev7G0OQKXC7Wcz+bs/X9tN3afDrBowRPR2h T7PpIi/hoB+sMg6gC3IGpmJXnR3WHnZzJhav25wuKjor2azupN6ZR1jVAj1CorNO D47aXOcI4VcV0u31haVqAsTkKiV/x4NAPyfWsGHEJq0iSZS8EGc= =cF3r -----END PGP SIGNATURE-----
--- End Message ---
